subject: How to troubleshoot Error 8961 to recover SQL database in MS SQL Server 2000? [print this page] How to troubleshoot Error 8961 to recover SQL database in MS SQL Server 2000?
In the SQL Server databases, a text index node is the one that is one level higher than the nodes in the database. In addition, it includes the text pointer in the actual data or index rows. Also, the child node has the same settings as the parent node, which is, sometimes, not followed when the database is corrupt. In such cases, you should try out appropriate corrective measures to recover MDF file. If these methods, do not work then an efficient third-party SQL recovery software should be used to do the needful.
Consider a situation in which you encounter 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_ID1, slot S_ID1, text ID TEXT_ID does not match its reference from page P_ID2, slot S_ID2."
Cause:
The primary cause of this problem is that there is corruption in a text object. In the text object, a child node does not match its parent node.
Resolution:
To rectify this problem, you can perform the following methods ideally in the given sequence:
Resolve the hardware-related issues: In most occasions, these problems are caused due to malfunctioning of the hardware components. You can check the following points to verify the actual cause:
Check the application event logs and SQL Server error logs to see if the error has occurred because of hardware corruption.
Fix the errors that appear after running hardware diagnostics.
Check if write caching is enabled on the hard disks. If yes, then contact the local hardware vendor to get them replaced.
Reinstall operating system after formatting the hard disks.
Restore from backup: If the problem is not hardware-related, then you should restore the database using the clean and updated backup.
Run DBCC CHECKDB: You should run DBCC CHECKDB with the recommended repair clause to repair the damaged database.
If the problem is not solved even after performing these methods, it means that the database is severely damaged. You should use a third-party SQL Database Recovery software to repair the MDF file. With the help of non-destructive scanning mechanisms, these master database file recovery tools recover all the data without any damage to the original database.
Of the various .MDF file recovery utilities, Stellar Phoenix SQL Recovery is the most effective that works for the databases created in MS SQL Server 7.0, 2000, 2005, and 2008. Recovering many database components including tables, NDF files, collations, triggers, defaults, stored procedures, etc, this MS SQL Server recovery software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.
