MS SQL Server is renowned computer based application which is widely used for creation and maintenance of large databases. You can easily store and manages huge amount data using SQL. It stores data in the form of indexes which is very easy to access. File of SQl Server consists of various pages which stores the allocation structures. IAM i.e. Index Allocation Map pages are one of them which contains informations about the indexes and tables. It stores one bit per extent in the Global Index Map of SQL. It indicates which extent is allocated to particular index. At times due to any adverse causes two IAM pages refer to same GAM interval due to which multiple IAM pages error 8947 appears in SQL.

At some point of time you receive SQL error 8947 when multiple Index Allocation Map pages refers to single object. In such cases, usually SQL users come across below error message:

Server: Msg 8947, Level 16, State 1 Table error: Multiple IAM pages for object ID O_ID index ID I_ID contain allocations for the same interval. IAM pages P_IDI and P_ID2.

SQL multiple IAM pages error 8947 appears only when IAM page for the given index consists of two IAM pages which occupy the same GAM interval. Occurrence of SQL error 8947 message indicates the table corruption which might occurs due to database header corruption, hardware failure, abrupt system shutdown, power failure and virus infections etc.

To work around this problem you have to check every issue responsible for the table corruption and then repair the damage properly. In order to achieve this task first of all you have to run hardware diagnostics and SQL Server error log to check the hardware related issues. If you find any damage then replace the hardware components. You can also run DBCC CHECKDB utility with repair clause to repair the damaged table and fix multiple IAM pages error 8947. In this way you can easily resolve the issue. In the database is corrupted too much extent then you have to use MSSQL Database Repair Software. It safely repairs the damaged table, indexes and entire database and hence fixes SQL error 8947.