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?
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.
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.