1

I have a single database running on SQL Server 2016 Standard edition in our primary datacenter. I would like to keep a live copy as close to realtime (1-2 minutes) in our disaster recovery datacenter so when the primary goes down we can redirect the traffic to DR. When the primary is back, changes in DR need to sync back to the primary.

From what I've researched peer-peer isn't available in the Standard edition. I found (and lost) a doc that discussed how to do this in Standard edition. It was limited to one database with one primary and one backup, yet I can't figure out what I searched to find it.

Any suggestions on best practice to accomplish this sync?

Improve this question

1 Answer 1

Reset to default
2

Replication is not a DR technology in SQL Server, so you should never consider that for DR purposes. In SQL 2016 Standard Edition, you should look at Basic Availability Groups.

Setting up a Basic AG for this database will provide you with DR capabilities and will allow for failover without breaking the flow of data between your replicas.

Improve this answer
2
  • Thanks... I've read about availability groups and I am a bit confused. When failed over is the DR database fully functional and will it sync back to the primary when the primary becomes available again?
    – Gary Hanna
    Aug 27, 2019 at 11:57
  • Yes, once a failover occurs, the DR node becomes the new Primary and will synchronise log records back to the original primary once it is available again.
    – HandyD
    Aug 27, 2019 at 23:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.