January 8, 2014 at 8:59 am
I noticed in my error log that CHECKDB has been adding to the error log that DBCC CHECKDB finished without error for a specific database constantly since the last CHECKDB run. The frequency of the logs varies, sometime there is 20 seconds between logs and sometime there is 4-5 minutes.
The issue looks like it started after the database recovered from a power failure 10 days ago. Below is the log prom the start up after power failure and a couple a relogs of "complete without error". There are thousands of these lines in the error log since. Starting up database 'dbname'.
2013-12-30 10:17:53.01 spid66 1064 transactions rolled forward in database 'dbname' (14). This is an informational message only. No user action is required.
2013-12-30 10:17:53.16 spid66 0 transactions rolled back in database 'dbname' (14). This is an informational message only. No user action is required.
2013-12-30 10:17:53.16 spid66 Recovery is writing a checkpoint in database 'dbname' (14). This is an informational message only. No user action is required.
2013-12-30 10:17:53.45 spid66 Recovery completed for database dbname (database ID 14) in 2 second(s) (analysis 41 ms, redo 1611 ms, undo 154 ms.) This is an informational message only. No user action is required.
2013-12-30 10:17:53.60 spid66 CHECKDB for database 'dbname' finished without errors on 2013-12-29 07:12:01.880 (local time). This is an informational message only; no user action is required.
2013-12-30 10:17:57.12 spid66 Starting up database 'dbname'.
2013-12-30 10:17:57.25 spid66 CHECKDB for database 'dbname' finished without errors on 2013-12-29 07:12:01.880 (local time). This is an informational message only; no user action is required.
2013-12-30 10:18:18.56 spid66 Starting up database 'dbname'.
2013-12-30 10:18:18.65 spid66 CHECKDB for database 'dbname' finished without errors on 2013-12-29 07:12:01.880 (local time). This is an informational message only; no user action is required.
2013-12-30 10:18:18.82 spid66 Starting up database 'dbname'.
2013-12-30 10:18:18.88 spid66 CHECKDB for database 'dbname' finished without errors on 2013-12-29 07:12:01.880 (local time). This is an informational message only; no user action is required.
DBCC CHECKDB has run since and the only thing that changes is the completed time. Has anyone seen this or have any suggestions outside of restarting the instance (last resort) on how to stop it from logging.
January 8, 2014 at 9:09 am
So you're saying that DBCC CHECKDB has been run on database 'dbname*' since 29 Dec 2013? Was it successful?
* Is this just one database in your log, or are you just obscuring the real names of several?
January 8, 2014 at 9:13 am
Robert klimes (1/8/2014)
Has anyone seen this or have any suggestions outside of restarting the instance (last resort) on how to stop it from logging.
I have seen this. Please check whether AutoClose option is ON of the database. If yes change it to OFF.
January 8, 2014 at 9:15 am
I was just coming back to ask that: see here
http://www.sqldbadiaries.com/2011/01/06/checkdb-running-every-minute-check-database-properties/
January 8, 2014 at 9:26 am
Beatrix Kiddo (1/8/2014)
So you're saying that DBCC CHECKDB has been run on database 'dbname*' since 29 Dec 2013? Was it successful?* Is this just one database in your log, or are you just obscuring the real names of several?
the dbcc had completed successfully and, yes, I am obscurring the database name.
Suresh B. (1/8/2014)
I have seen this. Please check whether AutoClose option is ON of the database. If yes change it to OFF.
autoclose was on. Since turning it off, the issue has stopped. thanks.:-)
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply