Tuesday, January 25, 2011

When should you use a third-party SQL recovery software to fix Error 8959 in MS SQL Server 2000 database

The IAM (Index Allocation Map) pages are an important part of SQL databases. The IAM pages enable indexing that results in faster searching and modifying operations. All these pages have a distinct index that should have the same index ID. However, that is not the case when the database is corrupt, which stops you from working on the database. In these circumstances, you should apply different methods for MDF recovery. If these methods do not work, then you should urgently seek the services of a third-party MS SQL Server recovery software.

Consider a scenario in which you are getting the following error message while working on the MS SQL Server 2000 database:

Table error: IAM page P_ID1 for object ID O_ID1, index ID I_ID1 is linked in the IAM chain for object ID O_ID2, index ID I_ID2 by page P_ID2.”


The root cause of this problem is inconsistency in the IAM pages, which is caused due to database corruption. In this case, one of the IAM pages linked into the IAM chain for I_ID2 index has I_ID1 on it.


To rectify this situation, you should recover MDF file. For this purpose, you can employ the following methods preferably in the given sequence:

  • Address hardware-related corruption issues: First of all, you should check whether the problem has occurred due to hardware malfunctioning. This can be done using following methods:

    • Check Windows application logs and SQL Server Error logs to ascertain if the error has caused due to faulty hardware parts or not.

    • Fix the errors that appear after running hardware diagnostics.

    • Exchange hardware parts to isolate the actual error of corruption.

    • Reinstall operating system after formatting the hard disks.

  • Replace database with updated backup: If the database backup is clean and updated, then you should replace the database with its backup.

  • Run DBCC CHECKDB: You should repair the damaged MDF file with the help of DBCC CHECKDB tool with the suggested repair clause.

The problem would be solved easily in similar cases. However, if the database is severely damaged, then you should use a third-party master database file recovery software to repair the database. These SQL recovery tools use fast and sophisticated scanning algorithms that enable quick, easy, and safe database recovery.

1 comment:

  1. To eliminate such index allocation must read this which helps to perform easy recovery in efficient manner click here :-