Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Good day,
One of our source databases used in Replicate are migrating from MS SQL server 2012 to 2019. This involves setting up the new server, back up the 2012 database and restore it on the new server.
How do we manage Replication in this case without reloading the full source database?
We thought, stop replicate, change the server details in the endpoint, and after MS replication has been set up, restart the Replicate task from a specific time.
Any best practices available?
Thanx!
Abrie
Hi @Abrie_M,
When moving SQL database when one server to another server
1) Stop the application first.
2) Monitor the replicate task and make sure that all the changes have been read.
3) Stop the replicate task.
4) After your database migration update the new database server info in the SQL endpoint and do the test connection.
5) You need to start the replication task from the current timestamp before you start your application. <-- This is a very important step if you don't want to miss changes.
6) Now start your application and monitor the changes.
Thanks,
Swathi
Hi @Abrie_M,
When moving SQL database when one server to another server
1) Stop the application first.
2) Monitor the replicate task and make sure that all the changes have been read.
3) Stop the replicate task.
4) After your database migration update the new database server info in the SQL endpoint and do the test connection.
5) You need to start the replication task from the current timestamp before you start your application. <-- This is a very important step if you don't want to miss changes.
6) Now start your application and monitor the changes.
Thanks,
Swathi
Thanx for the feedback, Swathi. Much appreciated!