November 19, 2007 at 6:33 am
Has anyone experienced an optimization job that does not error but appears to suddenly run much longer than normal. The job normally completes in 2 to 3 hours and in that time runs optimization on about 36 databases - it is currently still running 2 days later! It is processing, CPU and IO are clocking up and the db has changed so it will complete eventually. There are no errors or warnings in any of the logs, it appears to have hung for a day or so and then carried on. Does anyone know what could cause this and how to prevent it?
Cheers
The Aethyr Dragon
Cape Town
RSA
November 19, 2007 at 8:30 am
When running an Optimization Job or basically DBCC REINDEX it's always possible that a user process blocks the job. If a clustered index is being rebuilt, an exclusive table lock is needed. If some users are active in the database, they might prevent the job from placing such an exclusive lock.
Markus
[font="Verdana"]Markus Bohse[/font]
November 20, 2007 at 1:34 am
Thanks - that's the only thing I can think of as well.
Cheers
The Aethyr Dragon
Cape Town
RSA
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply