September 16, 2022 at 10:20 pm
Hi,
Was just curious if AOAG suspend data movement should have a positive impact on performance when applied to the primary node .
We have a Warehouse ETL process that is intensive , running on a 3 node AOAG and wondered if by suspending data movement on primary the ETL job would run faster on the primary.
I carried out some initial testing of this and there appeared to be not much in it in terms of execution timings, however when i took the db out of the AOAG completely the job completed approx 40 mins quicker.
Can't seem to find much documentation around the performance implications of suspending data movement ,apart from keeping an eye on log file growth.
So thought i would post this to hopefully get some views of other dba experiences
Thanks
James
September 17, 2022 at 8:36 pm
What mode do you have the AG set in SYNC or ASYNC?
If SYNC I would expect there to be some delay as your fighting with HADR_SYNC_COMMIT waits, however if it was ASYNC I wouldn’t expect to much difference between suspending movement or not.
September 22, 2022 at 10:48 am
This was removed by the editor as SPAM
September 26, 2022 at 11:43 am
This was removed by the editor as SPAM
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply