November 10, 2014 at 10:10 am
We are seeing high number of hadr_sync_wait types on our server after setting up AOAG during peak times. We have setup sync type as synchronous commit and failover automatic. Can we change these settings to async and manual failover whenever we need and change them back to sync commit during off peak timings. Any drawbacks because of these changes ?
November 10, 2014 at 10:24 am
muthyala_51 (11/10/2014)
We are seeing high number of hadr_sync_wait types on our server after setting up AOAG during peak times. We have setup sync type as synchronous commit and failover automatic. Can we change these settings to async and manual failover whenever we need and change them back to sync commit during off peak timings.
you can change the settings to whatever you want, but is this really the answer?
muthyala_51 (11/10/2014)
Any drawbacks because of these changes ?
No automatic failover!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 10, 2014 at 11:00 am
And, in the event of failover, async means no guarantee of intact data.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
November 13, 2014 at 2:57 am
you can change the settings to whatever you want, but is this really the answer?
When we rebuild indexes on one of the server, it's blocking other processes. We tried to changed synchronous commit to async it works fine. In order to avoid blocking on production servers, I came up with this solution till we figure out a permanant one.
November 24, 2014 at 9:48 am
The index rebuilds causing the server to choke. Is there any way we can avoid this ?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply