This is because for an online DBCC CHECKDB, an internal database snapshot is used to present a consistent set of data to check. The information in the message starting with "internal database snapshot." only appears if DBCC CHECKDB was run online, in which the database is not in SINGLE_USER mode. This message is also written to the Windows Application Event Log as an information level message with EventID=8957 (even if errors are reported this message is an information level message). This message shows how many database consistency errors were found and how many were repaired (if a repair option was used with the command). When the DBCC CHECKDB (or other similar commands like CHECKTABLE) is executed, a message like the following is written to the SQL Server error log: Date/Time spid53 DBCC CHECKDB (mydb) executed by MYDOMAIN\theuser found 15 errors and repaired errors.Įlapsed time: 0 hours 0 minutes 0 seconds. Original product version: SQL Server Original KB number: 2015748 Symptoms This article explains how to troubleshoot errors reported by the DBCC CHECKDB command.
0 Comments
Leave a Reply. |