delayed checkdb message in errorlog

  • I have a SQL2005 Maintenance Plan that does a checkdb operation on all databases. At the completion of the command for each database the log shows the following message:

    DBCC CHECKDB (msdb) WITH no_infomsgs executed by xxx found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 1 seconds.

    A couple of weeks later when I reboot the server and SQL starts up, one of the first messages in the new errorlog is:

    CHECKDB for database 'msdb' finished without errors on 2006-12-17 01:01:46.767 (local time). This is an informational message only; no user action is required.

    As you can see the messages are slightly different but are reporting essentially the same info. This happens for user databases as well as system databases. The date/time for the first message is the same as what is shown in the text for the last one although the last one doesn't get written to the errorlog until after the reboot. Any ideas what is happening?

    Bill

  • SQL Server 2005 saves in the database information about the last time a DBCC CHECKDB was run without errors on the database (that means found no corruption at all). Anytime the database is started, the information about the "last known good" clean DBCC is reported in the ERRORLOG...

    http://www.sqlskills.com/blogs/paul/2008/03/13/CHECKDBFromEveryAngleWhenDidDBCCCHECKDBLastRunSuccessfully.aspx

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply