1

In our always on set up we have One Primary and One Secondary as Synchronous Commit and the DR as asynchronous commit. If i want to change the DR to Synchronous Commit will there be any performance issues ?

3

If i want to change the DR to Synchronous Commit will there be any performance issues ?

Well, it will take longer to commit transactions, as the primary will wait for the log records to be saved on both sync replicas during each commit. Whether that causes a "performance issue" depends on the transaction throughput, network bandwidth, distance to the DR location, and the tolerance of the application and users for slower commits.

  • In our shop the mangement is deciding to use the DR as the primary for a couple of weeks so that they can do maintenance on the other ones. Due to network lag I guess this wont be a good idea – user9394033 Aug 28 '18 at 14:05
  • You can always switch the DR replica to synchronous, let it catch up, fail over to DR and set the old primary as async. That's just a failover, not a sync commit DR setup. – David Browne - Microsoft Aug 28 '18 at 14:06
  • Thanks for the clairification so in a nutshell the recommended availability mode of a DR should be asyn – user9394033 Aug 28 '18 at 14:09
  • Yes DR should normally be async, except while performing a planned failover to DR. – David Browne - Microsoft Aug 28 '18 at 14:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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