Hello guys,
We have a two MSSQL instances SQL 2008 R2 Enterprise with established peer to peer transactional replication between them.
The solution is built as a scale-out for better performance. One of the servers is a read server and the second one is a write server. Backend app server uses the write server to load data and another frontend application & SharePoint server use the read
server.
There are tables that are enabled for replication and others that are not which results in different database size on each peer.
We are planning to migrate the solution to two SQL 2008 R2 database consolidation instances built on a HA cluster active/active.
Our plan is to proceed in the following way:
1. Make sure there are no replicated transactions in progress and databases are in sync
2. Script replication with all publications/subscriptions on both instances and make the necessary changes in advance to reflect the new instance names. Transfer logins.
3. Disable all replication jobs on both peers
4. Detach databases from both reader & writer instances and attach them to the two new SQL 2008 R2 instances. Fix any login/user mappings
5. Execute the replication creation scripts that will create the distribution database, jobs, publications & subscriptions
6. Re-sync databases
I did not find many articles describing how an entire replication solution is supposed to be migrated. I would like to to check with you if the plan is correct or there is a better way to do this as well as any additional factors that must be taken into account.
Thank you in advance.