Saturday, December 5, 2009

Resolving “Forward row mismatch” Error message

In SQL Server database, rows of a table are divided and stored into a series of partitions. These rows can either be saved in heap or B-tree structure. In heap tree structure, the table does not contain any Index and the forward row always points back to the forwarding row. However, in B-tree structure the rows are saved in accordance to the Index values. Corruption in metadata structure of your SQL database results in changing the values of these rows, thereby resulting in inaccessibility of all database records. An easy way to surpass such corruption scenarios is by using restoring the data from an updated backup. But, the possibility of backup being corrupted or damaged always exist. In such situations, an ideal way is to repair your database by using an effective SQL Server Recovery software.

Consider a scenario, where the underneath error message pops up every time you attempt to mount your database:

“Forwarded row mismatch: Object ID O_ID, page P_ID1, slot S_ID1 points to forwarded row page P_ID2, slot S_ID2; the forwarded row points back to page P_ID3, slot S_ID3.”

Your database records become inaccessible after the above error message appears.


The main reason of the above error message is that the forwarded row (S_ID2 on page P_ID2) instead of pointing to forwarding row (S_ID1 on page P_ID1), is pointing to the wrong row.

Note: The above case can occur due to both logical and physical corruption scenarios.


The resolution for the above error message is mentioned below:

Swap the system component that is damaged with a new component.
Execute DBCC CHECKDB command.

While the former resolution to overcome hardware related issues is perfect, the later solution might fail to resolve logical corruption issues. For complete and systematic resolution in all logical corruption scenarios, you will need to opt for advanced SQL Database Repair tool. Such tools provide maximum MS SQL Repair by employing high end scanning and repairing algorithms. These tools are non-destructive and perform recovery without making any changes in the original database file.

No comments:

Post a Comment