November 22, 2010 at 4:54 am
Hi all
Recently my re-index job failed with an error of Lock request time out period exceeded. I am assuming what happened was that the re-index job was unable to get a lock on the table during the rebuild and so timed out.
Is there any way I can properly troubleshoot it other than running the rebuild again and profiling the locks on the table during that period, to see what was causing the lock? Doing the profile has no guarantee that I will find the problem as this has been successful in the past
Thanks for any suggestions.
December 18, 2010 at 12:04 pm
If you use Enterprise Edition of SQL Server you can try "online" option for rebuilding indexes.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy