Eric
Posts: 17314
Joined: 10/10/2003 From: Seattle, WA Status: offline
|
Uggh, here is another note for the future. Sometimes SQL Server will orphan a few running queries. They are mostly harmless, and once a month when I apply Windows Updates they get cleaned out. (I have found you cannot stop or kill these without recycling the SQL Processes.) Anyway, after my 5 minute update above, the system sat grinding on the same index for the next 5 minutes before I noticed that it was blocked. Sigh. So I stopped the job, restarted SQL Server, and now I am rerunning the job from the start. So we lost 10 minutes (the job rebuilds all indices from scratch and cannot really tell which ones have been done already.) So note to self for the future: recycle SQL Server before I kick off the index rebuild. Take 2. OK, 5 minutes in. We have rebuilt 82 of 740 indices or 11.1%. (And if you are wondering why it made different progress, it is due to the fact that it processes the indices in order of fragmentation. So this second run is working on different indices. And some indices are tiny and rebuild in seconds, while others are huge and take minutes.)
_____________________________
Cheers! -Eric LeVine http://twitter.com/cellartracker http://facebook.com/cellartracker
|