DBCC %ls (%ls%ls%ls) executed by %ls found %d errors and repaired %d errors.

Product: SQL Server
Event ID: 8957
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: DBCC %ls (%ls%ls%ls) executed by %ls found %d errors and repaired %d errors.
This message indicates that DBCC CHECKDB, DBCC CHECKALLOC, DBCC CHECKTABLE, or DBCC FILEGROUP has been executed on the SQL Server instance.

This message is never returned to the calling application; it is only written to the SQL Server error log and to the application event viewer. It is written to those logs even if the WITH NO_INFOMSGS option is used, as that option only controls what is returned to the calling application.

User Action
If the message indicates that errors were found:


Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows NT system and application logs and the SQL Server error log to see if the error occurred as the result of hardware failure. Fix any hardware-related problems.

If you have persistent data inconsistency problems, try to swap out different hardware components to isolate the problem. Check that your system does not have write caching enabled on the disk controller. If you suspect this to be the case, contact your hardware vendor.

Finally, you might find it beneficial to switch to a completely new hardware system, including reformatting the disk drives and reinstalling the operating system.


If the problem is not hardware related and a known clean backup is available, restore the database from the backup.


If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.

CAUTION: If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.

If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.


Leave a Reply