subject: Using MDF recovery utility to fix Error 8927 in MS SQL Server 2000 database [print this page] Are you facing problems when you work on the MS SQL Server 2000 database? If yes, then do check out to see if the error messages are suggesting problems in the page definitions of the database. If this is indeed the case, then you should find out the reason of page corruption and try to address the problem. If you are unable to fix the issue, then I would suggest you to use third-party SQL database recovery software to perform SQL recovery.
Let us analyze a situation in which you are facing the following error message while working on an MS SQL Server 2000 database:
"Object ID O_ID, index ID I_ID: The ghosted record count (HG_COUNT) in the header does not match the number of ghosted records (G_COUNT) found on page P_ID."
Cause:
The root cause of this problem is corruption in the page definitions. Because of this, the record count in the header is not similar to the numer of ghosted records on the P_ID page.
Resolution:
This problem can be solved by recovering MDF file. For this, you can try out the following three methods preferably in the given order:
Fixing corruption issues caused due to hardware failure: On numerous occasions, such issues occur due to faults in the hardware parts. To resolve these issues, you should perform the following measures:
Addressing the issues that appear after running hardware diagnostics.
Analyzing the error logs and checking if any error has occurred due to hardware failure. Try to fix it.
Swapping the hardware parts to isolate the exact reason that caused this error.
Formatting the hard disks and reinstalling the operating system.
Restoring database using backup: If the hardware parts are perfectly in place, then you restore the database with the backup provided it is updated and clean.
Employing DBCC CHECKDB: If the backup solution does not work, then you should run the DBCC CHECKDB utility with the suggested repair clause.
If the aforementioned SQL recovery methods do not provide a relief, then the use of a third-party MDF file recovery software remains the last hope in this case. These master database file recovery tools are extremely safe in their working and do not modify the existing databases in any which way.
The best MS SQL Server recovery software in such cases is Stellar Phoenix SQL Data Recovery, which recovers SQL databases created in MS SQL Server 7.0, 2000, 2005, and 2008. With the ability to recover MDF objects including NDF files, stored procedures, tables, triggers, collations, etc, this .MDF recovery tool is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.
Using MDF recovery utility to fix Error 8927 in MS SQL Server 2000 database
