subject: How to resolve Error 8964 to repair damaged database in MS SQL Server 2000 [print this page] How to resolve Error 8964 to repair damaged database in MS SQL Server 2000
Are you getting few error messages related to the text nodes while working on your SQL database? If yes, then there is a strong possibility that the SQL database may have gone corrupt. The reasons for corruption could range from virus infections to abrupt or unplanned system shutdown and from hardware malfunctioning to database header corruption. In such cases, you would not be able to access the database or carry out various tasks. In such cases, you should use appropriate corrective methods for database recovery. If none of the methods succeed, then I would suggest you to use a third-party SQL Database Recovery software to resolve the issue.
Consider a scenario in which you are getting the following error message while working on an MS SQL Server 2000 database:
"Table error: Object ID O_ID. The text, ntext, or image node at page P_ID, slot S_ID, text ID TEXT_ID is not referenced."
Cause:
The root cause of this problem is that the text node was not referenced in any complex column in any heap or clustered index.
Resolution:
To resolve this problem, you should perform the following methods preferably in the given sequence:
Resolve hardware-related issues: You should check if the problem is not caused due to hardware malfunctioning. This can be done by using the following measures:
Checking the error logs and application event logs to see whether the problem is caused due to hardware malfunctioning.
Fixing any errors that appear once you run hardware diagnostics.
Swapping hardware components to isolate the actual cause of corruption.
Checking if write caching is enabled on the hard disks. If yes, then contact your hardware vendor to get it replaced.
Finally, if nothing works then you should reinstall the operating system after formatting the hard disks.
Restore from updated backup: You should check the status of the database backup. If it is clean and updated, then you should restore the database with the backup.
Run DBCC CHECKB: You should run the DBCC CHECKDB command with the suggested repair clause to repair the damaged SQL database.
If you still are getting the same error, then you should use a third-party database recoverysoftware for SQL databases to repair the damaged database. These read-only SQL repair tools are extremely safe to use that do not damage the existing data.
Stellar Phoenix SQL Data Recovery is the most recommended SQL database recovery software that repairs damaged or inaccessible SQL databases from all sorts of logical corruption. Recovering various database components such as tables, NDF files, collations, stored procedures, triggers, defaults, etc, this database recovery software is capable of displaying the preview of the repairable SQL components. In addition, this SQL Server Recovery software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.
