You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
32 lines
641 B
32 lines
641 B
|
3 weeks ago
|
# Proposal: 数据库优化与迁移
|
||
|
|
|
||
|
|
## Why
|
||
|
|
现有数据库存在以下问题:
|
||
|
|
1. 表结构设计不合理
|
||
|
|
2. 缺乏索引优化
|
||
|
|
3. 字段冗余
|
||
|
|
4. 缺乏数据迁移方案
|
||
|
|
5. 查询性能低下
|
||
|
|
|
||
|
|
## What
|
||
|
|
优化数据库设计并实施迁移:
|
||
|
|
1. 重新设计表结构
|
||
|
|
2. 添加索引优化
|
||
|
|
3. 规范化字段
|
||
|
|
4. 完整数据迁移方案
|
||
|
|
5. 迁移回滚方案
|
||
|
|
|
||
|
|
## Success Criteria
|
||
|
|
1. 表结构符合第三范式
|
||
|
|
2. 查询性能提升 50%
|
||
|
|
3. 数据迁移 100% 完整
|
||
|
|
4. 迁移可回滚
|
||
|
|
5. 无数据丢失
|
||
|
|
|
||
|
|
## Non-Goals
|
||
|
|
- 不改变业务逻辑
|
||
|
|
- 不引入新的数据库类型
|
||
|
|
|
||
|
|
## Dependencies
|
||
|
|
- 依赖 refactor-backend-api 的后端适配
|