July 23, 2013 at 1:23 am
We have databases setup in availability group, recently we had to do an rebuild few indexes as they were fragmented. The index size was 12GB+. Rebuilding index started to consume more log space, I increased the disk space about nearly 50GB and still it was not completed. I understand the log will grow during rebuild of indexes, these changes are hardened on the secondary replica database.I saw blocking issues with HADR_COMMIT_SYNC wait type. Are there any guidelines of rebuilding indexes in the availability group? Please share..
Using Online option to rebuild the index
July 23, 2013 at 2:23 am
Good question I'm moving to Always on soon. I would like to know the answer to this too. Something I have been thinking about too.
July 23, 2013 at 10:17 am
Fast tlog disks on both machines, and a very low latency fat network connection are key to good mirroring throughput. You should do a file IO stall and wait stats analysis while the reindex is running, as well as checking how far behind the sync is (if async) and also run sp_whoisactive to see what it might show for current activity and execution details.
Consider getting a professional on board to give your systems and setup a quick review. In my experience there are always lots of low-hanging fruits to be found ...
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply