数据库迁移策略 [英] DB Migration strategy

问题描述

嗨专家，

请针对以下情况提出迁移策略的高级计划建议。 

Kindly advice with high level plan for migration strategy for the below situation. 

情况

1。一个非常活跃的货币OLTP数据库，包含600多个表。

1. A very highly active monetary OLTP DB containing over 600 tables.

2。我需要将400多个表迁移到不同的数据库中。

2. I need to migrate over 400 tables into different DB's.

3。因此，假设我已将大约65个表分组，这些表属于某个LOB，可以移动到自己的专用数据库。

3. So let say I have grouped around 65 tables which belong to a certain LOB and can be moved to its own dedicated DB.

4。从65个表中30个不会收到太多活动的交易选择更多的插入。

4. From the 65 tables 30 are don't receive much active transactions selects more of inserts.

5。 20个表是高度事务，也复制到其他服务器。

5. 20 tables are highly transaction and also replicated to other servers.

6。我已经确定了这些表的依赖对象。

6. I have identified the dependent objects for those tables.

挑战

1。在同一个SQL Server实例中将其移动到不同的数据库，而不会丢失数据或对业务产生影响。 

1. Move it to different DB with in same SQL Server instance without Data loss or impact to business. 

我想在同一个数据库实例中设置事务复制并从中移动读取活动工作负载所有交易同步后新数据库。 

Am thinking to setup transaction replication within the same database instance and move the read activities workload from the new DB once all the transactions are in sync. 

稍后停用文章&转移写入也在新数据库上。 

Later disable the article & transfer writes also on the new DB. 

关注复制的延迟问题&从资源利用的角度来看，初始快照也可能是一项昂贵的操作。

Concern about the latency issues with replication & also the initial snapshot may be an expensive operation from resource utilisation point of view.

请您建议其他合适的方法..

Could you please suggest other suitable approaches..

谢谢 

Priya

推荐答案

。

这篇关于数据库迁移策略的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！