Problems of having DR as Synchronous Commit

Clash Royale CLAN TAG#URR8PPP

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;

up vote
1
down vote

favorite

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 ?

sql-server-2012 availability-groups data-synchronization disaster-recovery sql-data-sync

share|improve this question

asked Aug 28 at 13:53

user9394033

1518

add a comment | 

up vote
1
down vote

favorite

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 ?

sql-server-2012 availability-groups data-synchronization disaster-recovery sql-data-sync

share|improve this question

asked Aug 28 at 13:53

user9394033

1518

add a comment | 

up vote
1
down vote

favorite

up vote
1
down vote

favorite

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 ?

sql-server-2012 availability-groups data-synchronization disaster-recovery sql-data-sync

share|improve this question

asked Aug 28 at 13:53

user9394033

1518

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 ?

sql-server-2012 availability-groups data-synchronization disaster-recovery sql-data-sync

share|improve this question

asked Aug 28 at 13:53

user9394033

1518

share|improve this question

share|improve this question

asked Aug 28 at 13:53

user9394033

1518

asked Aug 28 at 13:53

user9394033

1518

asked Aug 28 at 13:53

user9394033

1518

1518

add a comment | 

add a comment | 

1 Answer
1

active

oldest

votes

up vote
3
down vote



accepted

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.

share|improve this answer

answered Aug 28 at 14:02

David Browne - Microsoft

8,185622

• 
  
  
  

  
  

  
  
  
  
  
  

  
  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 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 at 14:06
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Thanks for the clairification so in a nutshell the recommended availability mode of a DR should be asyn
  – user9394033
  Aug 28 at 14:09
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Yes DR should normally be async, except while performing a planned failover to DR.
  – David Browne - Microsoft
  Aug 28 at 14:09
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "182"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f216073%2fproblems-of-having-dr-as-synchronous-commit%23new-answer', 'question_page');

);

Post as a guest

Name Email

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

active

oldest

votes

active

oldest

votes

up vote
3
down vote



accepted

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.

share|improve this answer

answered Aug 28 at 14:02

David Browne - Microsoft

8,185622

• 
  
  
  

  
  

  
  
  
  
  
  

  
  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 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 at 14:06
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Thanks for the clairification so in a nutshell the recommended availability mode of a DR should be asyn
  – user9394033
  Aug 28 at 14:09
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Yes DR should normally be async, except while performing a planned failover to DR.
  – David Browne - Microsoft
  Aug 28 at 14:09
  

  
  
  
  

add a comment | 

up vote
3
down vote



accepted

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.

share|improve this answer

answered Aug 28 at 14:02

David Browne - Microsoft

8,185622

• 
  
  
  

  
  

  
  
  
  
  
  

  
  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 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 at 14:06
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Thanks for the clairification so in a nutshell the recommended availability mode of a DR should be asyn
  – user9394033
  Aug 28 at 14:09
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Yes DR should normally be async, except while performing a planned failover to DR.
  – David Browne - Microsoft
  Aug 28 at 14:09
  

  
  
  
  

add a comment | 

up vote
3
down vote



accepted

up vote
3
down vote



accepted

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.

share|improve this answer

answered Aug 28 at 14:02

David Browne - Microsoft

8,185622

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.

share|improve this answer

answered Aug 28 at 14:02

David Browne - Microsoft

8,185622

share|improve this answer

share|improve this answer

answered Aug 28 at 14:02

David Browne - Microsoft

8,185622

answered Aug 28 at 14:02

David Browne - Microsoft

8,185622

answered Aug 28 at 14:02

David Browne - Microsoft

8,185622

8,185622

• 
  
  
  

  
  

  
  
  
  
  
  

  
  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 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 at 14:06
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Thanks for the clairification so in a nutshell the recommended availability mode of a DR should be asyn
  – user9394033
  Aug 28 at 14:09
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Yes DR should normally be async, except while performing a planned failover to DR.
  – David Browne - Microsoft
  Aug 28 at 14:09
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  

  
  
  
  
  
  

  
  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 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 at 14:06
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Thanks for the clairification so in a nutshell the recommended availability mode of a DR should be asyn
  – user9394033
  Aug 28 at 14:09
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Yes DR should normally be async, except while performing a planned failover to DR.
  – David Browne - Microsoft
  Aug 28 at 14:09
  

  
  
  
  

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 at 14:05

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 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 at 14:06

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 at 14:06

Thanks for the clairification so in a nutshell the recommended availability mode of a DR should be asyn
– user9394033
Aug 28 at 14:09

Thanks for the clairification so in a nutshell the recommended availability mode of a DR should be asyn
– user9394033
Aug 28 at 14:09

Yes DR should normally be async, except while performing a planned failover to DR.
– David Browne - Microsoft
Aug 28 at 14:09

Yes DR should normally be async, except while performing a planned failover to DR.
– David Browne - Microsoft
Aug 28 at 14:09

add a comment | 

 

draft saved

draft discarded

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f216073%2fproblems-of-having-dr-as-synchronous-commit%23new-answer', 'question_page');

);

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Name Email

Name

Email

Name Email

Name

Email