|
I took a new job and inherited several Sql 2005 instances that have DBCC checkdb configured to run on startup of the instance. On the restart of a prod instance the other day, it took an hour before I got "Recovery Complete." It isn't to be a SQL agent job nor a schedule task. Where else could Sql Server be configured to do this?
(comments are locked)
|
|
It isn't sp_procoption, no user stored procs in master and "scan for startup procs" has a run values of zero. All the shutdowns were clean, command issued through SSMS. Any other possiblities? This one has got me stumped.
(comments are locked)
|
|
The only time I have seen it do this on startup on my server is when the database did not have a chance to close properly on shutdown. IE Power failure, hardware issue, etc. The only other time it runs on my server is during a scheduled job or when I run it manually. +1 Oh yeah, I completely spaced that. If you power off the server or in some other way stop the service, not allowing a shut down, it will do a consistency check on startup
Oct 01 '10 at 11:27 AM
Grant Fritchey ♦♦
Hey Grant, thanks for the push over 2000. I am glad it was you who sent me over. Now I can edit.
Oct 01 '10 at 11:29 AM
Tim
Congrats on the 2k. You've absolutlely boosted the quality around here.
Oct 01 '10 at 11:35 AM
Grant Fritchey ♦♦
congrats TRAD on the 2k!
Oct 01 '10 at 12:30 PM
DaniSQL
(comments are locked)
|
|
There's a startup procedure that could be doing this. Check out sp_procoption in the BOL to see more information about it. Good to know.
Oct 01 '10 at 11:09 AM
Tim
(comments are locked)
|
