June 12, 2014 at 10:33 pm
Hi
Why "DBCC CHECKDB WITH physical_only executed" run across my instance for every database although i did not run in manually ? Is it by default a new feature that will run in sql 2012?
June 13, 2014 at 1:51 am
1) Can you please tell us what information you used to conclude that checkdb was run?
2) Was it run just once or on some schedule?
3) Did you check for SQL Agent job that could do this?
4) Did you ask around to those that have access to see if someone else did it?
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
June 13, 2014 at 2:27 am
adzuanamir (6/12/2014)
Why "DBCC CHECKDB WITH physical_only executed" run across my instance for every database although i did not run in manually ? Is it by default a new feature that will run in sql 2012?
It isn't running automatically. Take a closer look at the times on those messages (hint, the time it ran will not be the same as the time of the log entry)
http://sqlmag.com/blog/why-sql-server-running-dbcc-checkdb-against-my-databases-server-startup
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
June 13, 2014 at 2:54 am
Hi monster, based on the link that you provide:
1. I did not restart or shutdown the database instance
2. The dbcc checkdb will keep popping out the sql server log message everyday.
3. Based on the log it take approximately 8 minutes 9 second to execute checkdb for database CGOPRDKCHS
Below are the sql server log:
06/09/2014 08:11:42,spid55,Unknown,DBCC CHECKDB (EMS) WITH physical_only executed by KLAS\BKUPEXEC found 0 errors and repaired 0 errors. Elapsed time: 0 hours 2 minutes 45 seconds. Internal database snapshot has split point LSN = 00004079:000014c9:0001 and first LSN = 00004079:000014c7:0001.
06/09/2014 08:08:55,spid55,Unknown,DBCC CHECKDB (CGOPRDKCHS) WITH physical_only executed by KLAS\BKUPEXEC found 0 errors and repaired 0 errors. Elapsed time: 0 hours 8 minutes 9 seconds. Internal database snapshot has split point LSN = 0000701b:0000032c:0001 and first LSN = 0000701b:0000032a:0001.[/color]
I dont know how to run "dbcc page ()" to get the "dbi_dbccLastKnownGood" because i dont know what value to put inside the ().
June 13, 2014 at 3:48 am
Ok, that really is something running CheckDB. From the username, looks like it might be coming from BackupExec. BackupExec may be doing a checkDB before each full backup, that could be the cause of this.
SQL does not run CheckDB automatically, ever. It's been run by someone or something, you need to identify what.
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
July 1, 2014 at 11:25 pm
Thanks bro...i will crosscheck with my infra team regarding the backup exec...I have a strong feeling this are the 3rd party backup solution that triggering dbcc checkdb
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply