Aligning Technology with Business

CIO/CTO Update

Subscribe to CIO/CTO Update: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get CIO/CTO Update: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


CIO/CTO Update Authors: Andy Thurai, Thanh Tran, Lori MacVittie, Adrian Bridgwater, Reza Koohrang

Related Topics: Microsoft Developer, CIO/CTO Update

Blog Feed Post

DBCC CHECKDB Process Fails With “Error 8967” in SQL Server

Microsoft SQL Server is a widely used relational database management system, which stores all the data in MDF (Master Database File). It provides an inbuilt utility to check the physical and logical integrity of the objects in specified database through a series of operations. However, in some situations, this tool fails to check the integrity and consistency of the SQL Server database and the database remains inaccessible. In such situation, you may face critical data loss situations and need SQL Database Recovery.

As an example of this problem, consider the underwritten scenario:

You restore Microsoft SQL Server 2005 or Microsoft SQL Server 2008 database from backup.
You encounter errors while restoring the database and the restore process fails.
You restore database from same backup using CONTINUE_AFTER_ERROR option.

In such cases, when you use DBCC CHECKDB command-line utility on computer, which has MDF file, you get the below error:

“Msg 8967, Level 16, State 216, Server , Line 2
An internal error occurred in DBCC which prevented further processing. Please contact Customer Support.
DBCC results for ''.
Msg 8921, Level 16, State 1, Server , Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.”

Furthermore, you may see the below error in error log of SQL Server:

“2007-05-26 07:13:49.21 spid58 DBCC encountered a page with an LSN greater than the current end of log LSN () for its internal database snapshot. Could not read page (file id:page id), database '), LSN = (), type = 32, isInSparseFile = 1. Please re-run this DBCC command.”

Cause

You face this problem if DBCC CHECKDB command can't perform required checks for confirming database consistency due to severe corruption.

Solution

In such critical situations, you need to restore database from the latest backup. But, if the backup is either not available or not updated, SQL Server Recovery becomes need of hour.

You can recover your damaged SQL Server database using powerful MS SQL Recovery software. The applications are powerful enough to systematically scan whole database and extract all inaccessible objects from it. They offer easy SQL Recovery with simple and interactive user interface.

SQL Recovery software successfully repairs and restores damaged SQL Server database using powerful techniques. It is designed for Microsoft SQL Server 2008, 2005, and 2000. The software restores all of the MDF file objects, including tables, reports, forms, macros, stored procedures, and triggers.

Read the original blog entry...

More Stories By Gram Smith

Gram Smith is an Internet entrepreneur and Database Repair Expert. Gram generally write articles on how to recover and repair precious data related to Access Repair Database, MS SQL Recovery Database, and MySql Repair.