August 5, 2011 at 8:02 am
In my SQL log I have several checkdb that run in the middle of the day:
Date8/4/2011 10:43:05 AM
LogSQL Server (Current - 8/5/2011 9:25:00 AM)
Sourcespid76s
Message
CHECKDB for database 'bigdb' finished without errors on 2011-07-28 00:02:57.417 (local time). This is an informational message only; no user action is required.
This is a new server, I don't have any jobs that runs a checkdb. yet.
I guess the only thing I can do is try to remember to look on Activity Monitor on Monday around same time to see who or what is connected to the databases.
August 5, 2011 at 8:22 am
There's a message like that right after a restart (which is a not a real checkdb()). In my server it's like this :
Date7/13/2011 2:13:45 PM
JournalSQL Server (Archive n°1 - 7/13/2011 2:24:00 PM)
Sourcespid17s
Message
CHECKDB for database 'PROD-FORDIA' finished without errors on 2011-07-13 04:33:54.227 (local time). This is an informational message only; no user action is required.
After an actual checkdb I get this slightly different message :
Date7/13/2011 1:20:43 AM
JournalSQL Server (Archive n°2 - 7/13/2011 2:15:00 PM)
Sourcespid59
Message
DBCC CHECKDB (PROD-FORDIA_test_restore) WITH no_infomsgs, tableresults executed by NT AUTHORITY\SYSTEM found 0 errors and repaired 0 errors. Elapsed time: 0 hours 11 minutes 36 seconds.
August 5, 2011 at 9:21 am
Sailor (8/5/2011)
Date8/4/2011 10:43:05 AM
LogSQL Server (Current - 8/5/2011 9:25:00 AM)
Sourcespid76s
Message
CHECKDB for database 'bigdb' finished without errors on 2011-07-28 00:02:57.417 (local time). This is an informational message only; no user action is required.
It's not running. Look at the dates.
SQL, starting up at 2011/08/05 09:25 notes in the log that CheckDB last completed at 2011-07-28 00:02.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 5, 2011 at 9:27 am
btw, if you're getting that in the middle of the day it means that the database closed and SQL opened it again. That's only printed when SQL brings a DB online. That should only be after a start of SQL or after a restore, attach or set online. If it's happening unexpectedly it may be that you have autoclose on, which is bad for a busy database.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 5, 2011 at 9:33 am
GilaMonster (8/5/2011)
btw, if you're getting that in the middle of the day it means that the database closed and SQL opened it again. That's only printed when SQL brings a DB online. That should only be after a start of SQL or after a restore, attach or set online. If it's happening unexpectedly it may be that you have autoclose on, which is bad for a busy database.
Hmm, when have you found auto_close to be usefull?
August 5, 2011 at 9:35 am
Ninja's_RGR'us (8/5/2011)
GilaMonster (8/5/2011)
btw, if you're getting that in the middle of the day it means that the database closed and SQL opened it again. That's only printed when SQL brings a DB online. That should only be after a start of SQL or after a restore, attach or set online. If it's happening unexpectedly it may be that you have autoclose on, which is bad for a busy database.Hmm, when have you found auto_close to be usefull?
Seldom used database on a busy server. If it's seldom used I don't want it's data and plans hogging memory that the rest of the server needs.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 5, 2011 at 9:38 am
How do you define seldom and what's the "usual" delay to bring it back online (ms or s)?
August 5, 2011 at 9:41 am
Ninja's_RGR'us (8/5/2011)
How do you define seldom and what's the "usual" delay to bring it back online (ms or s)?
The same way I define 'often', 'most', etc. Relative to what else is happening.
Usual delay = it depends.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 5, 2011 at 9:52 am
GilaMonster (8/5/2011)
Ninja's_RGR'us (8/5/2011)
How do you define seldom and what's the "usual" delay to bring it back online (ms or s)?The same way I define 'often', 'most', etc. Relative to what else is happening.
Usual delay = it depends.
Sometimes a ballpark figure or a real life exemple is a good number too ;-).
August 5, 2011 at 11:12 am
Thanks for the explanation.
That sort of explains a restart as we are not supposed to be "involved" on that server at the moment (go figure), but I was curious and noticed the entries in log.
August 5, 2011 at 11:32 am
Anytime a database starts SQL logs when the last checkDB completed without error. It's an aid for if you find corruption, you can check and see at what point the database was known to be clean.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply