subject: Resolving Error 7965 and recovering corrupt database in SQL Server 2000 [print this page] Resolving Error 7965 and recovering corrupt database in SQL Server 2000
In SQL Server databases, an Index Allocation Map (IAM) page is a page type that stores the details about the extents, which is a collection of eight pages. These IAM pages are used to navigate through the heap, thereby making the searching process much faster. Well, at times these IAM pages do not exhibit the desired working due to database corruption. Database corruption can occur due to various reasons such as power outages, human errors, damaged hardware components, virus infections, etc. You should find out the cause and the resolution to recover SQL database. If you are not able to recover the database, then you should use a third-party SQL database recovery software to do the needful.
Consider a scenario wherein you encounter the following error message while working on the SQL Server 2000 database:
"Table error: Could not check object ID O_ID, index ID I_ID due to invalid allocation (IAM) page(s)."
Cause:
The root cause of this error message is that one of the IAM pages, which was identified by various Ids, has corrupted.
Resolution:
To resolve this erroneous situation, you should recover SQL database using the following methods, in the given order:
Check the hardware-related reasons: You should check the error log reports to check whether the error has occurred due to malfunctioning hardware components. You can also consider swapping the hardware components to isolate the actual reason for error. You may also consider reformatting the hard disks and reinstalling the operating system to get a fresh system to work on.
Restore from backup: If the problem is not hardware related, then you should check if the database backup is updated and clean. If yes, then restore the database from its backup.
Run DBCC CHECKDB: If the backup is not updated, then you should run the DBCC CHECKDB command to repair the database. You should run it without any repair clause to know the level of corruption, and then with the recommended repair clause to repair the database.
However, if the problem is not resolved even after performing these methods then you should use a third-party SQL database recovery software. These read-only tools are able to recover SQL database without overwriting the original database.
Stellar Phoenix SQL Data Recovery is an MS SQL recovery software that recovers corrupted SQL databases from all instances of corruption. It is able to recover SQL databases created in SQL Server 2000, 2005, and 2008. This SQL Server recovery tool restores various database objects such as tables, queries, stored procedures, triggers, defaults, etc. In addition, this SQL recovery utility is capable of preserving database constraints and user-defined functions and data types. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.
