August 23, 2014 at 4:02 pm
Hi Guys,
Here is the scenario that I am facing and not exactly sure how to go about it. Please let me know your thoughts.
I have a database with 1.5 TB in size. Rebuild Index Job fails after running for 10 hours and after completing 80%(last week, it failed due to deadlock). The same database is on a Replication Configuration on Publisher role. During the Rebuil Index run, I noticed Replication Log Reader is constantly blocked by Rebuild Index Job. Rebuild Index doesn't seems to make any progress, it's stuck at 33%.
Is there anything we can do to to Replication to complete Rebuild Index job successfully?
Regards,
SQLisAwe5oMe.
August 23, 2014 at 4:27 pm
Quick question, what edition of SQL Server are you on?
😎
August 23, 2014 at 7:10 pm
It's 2008r2, enterprise edition on Windows 2008.
Regards,
SQLisAwe5oMe.
August 24, 2014 at 12:44 am
SQLisAwE5OmE (8/23/2014)
It's 2008r2, enterprise edition on Windows 2008.
Are you using the ONLINE option? If you are, the additional resources required might be part of the problem. If not, in might also be worth giving it a shot.
😎
August 25, 2014 at 12:27 am
This was removed by the editor as SPAM
August 25, 2014 at 6:12 am
Quick question, how beefy is the index/indexes being rebuilt? Would it be an option to build an identical index with the ONLINE option and then drop the existing one afterwards?
😎
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply