June 27, 2019 at 4:27 pm
All:
Has anyone experienced issues with SharePoint 2010 in a SQL 2012 Availability Group?
In the past year we have added several databases to AGs. On two in particular we have had challenges with log file growth, especially with synchronous replication but even with asynchronous replication.
I am inclined to not expect SharePoint to be a problem. The databases that don't play well in AG have large daily dataloads. My thinking is that since the primary database log file cannot be reused until the transactions are committed on the secondaries, when individual transactions are very large, they can stack up, growing the log file out of control. On the other hand, changes made my users in SharePoint are small, written to the secondaries and committed quickly, keeping the log files under control.
The two problematic databases previous created problems when using mirroring, probably for the same reasons. We run Sharepoint with Asynch mirrors for years without issues.
So is it safe to put SharePoint in an AG?
June 28, 2019 at 5:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply