Azure SQL Database Geo Replication With Large Table

Question

We are getting ready to move our non-Azure db to Azure Sql Database and are wanting to use Geo-Replication as a failover.

Our audit table has 130+ Million rows of data and so just wondering how long the seeding process will take?

Also do we have to wait for the seeding process to complete before we can open up our production App? If the seeding process has not completed and we start creating transactions in our primary db, what will happen to those transactions on the secondary DB?

Answer 1

The time it takes is really dependent on a lot of factors, so it's going to hard to give you a solid answer. However, I can tell you that you can immediately make the database available before it completes the geo-replication setup. It's made so that you have access to the primary database the whole time.