In SQL Server databases, the data is stored in heaps when the data is not logically sorted in the tables. This heap can sometimes display abnormal behavior while working on the SQL database. Such cases can occur because of various reasons such as virus infections, power outages, abrupt system shutdown, hardware malfunctions, etc. In such cases, you should try to resolve the problem using in-house recovery methods. If you are not able to recover SQL database, then you should use a third-party SQL recovery software.
Consider a scenario wherein you encounter the following error message while working on an MS SQL Server 2008 database:
“Object ID O_ID, forwarded row page P_ID1, slot S_ID1 should be pointed to by forwarding row page P_ID2, slot S_ID2. Did not encounter forwarding row. Possible allocation error.”
The root cause of this erroneous situation is that there is a forwarded row in a heap that is missing the forwarding row that should point to it.
To resolve this problem, you need to do MDF file recovery. For this, you should perform the following methods:
Check for hardware issues: You should check the hardware components to ascertain whether the error has occurred because of any hardware malfunctions or not. You can also swap the hardware components to isolate the actual problem. Last but not the least, you can even consider reformatting hard disks and reinstalling operating system.
Restore from backup: If it is not a hardware related problem, then you should check the backup of the database. If it is updated and clean, then you should restore the database with its backup.
Run DBCC CHECKDB: If the database is not clean, then you should run DBCC CHECKDB command with the suggested clause to repair the corrupted database. It will convert the forwarded row into a regular data row.
These methods should be able to repair the corrupted SQL component. However, if you are still getting the same error, then you should use a third-party SQL database recovery software to perform SQL recovery. Such MDF recovery tools are read-only in nature that do not overwrite the existing database while scanning.
Stellar Phoenix SQL Data Recovery is a master database file recovery software that recovers MDF files from all instances of logical corruption.
Consider a scenario wherein you encounter the following error message while working on an MS SQL Server 2008 database:
“Object ID O_ID, forwarded row page P_ID1, slot S_ID1 should be pointed to by forwarding row page P_ID2, slot S_ID2. Did not encounter forwarding row. Possible allocation error.”
The root cause of this erroneous situation is that there is a forwarded row in a heap that is missing the forwarding row that should point to it.
To resolve this problem, you need to do MDF file recovery. For this, you should perform the following methods:
Check for hardware issues: You should check the hardware components to ascertain whether the error has occurred because of any hardware malfunctions or not. You can also swap the hardware components to isolate the actual problem. Last but not the least, you can even consider reformatting hard disks and reinstalling operating system.
Restore from backup: If it is not a hardware related problem, then you should check the backup of the database. If it is updated and clean, then you should restore the database with its backup.
Run DBCC CHECKDB: If the database is not clean, then you should run DBCC CHECKDB command with the suggested clause to repair the corrupted database. It will convert the forwarded row into a regular data row.
These methods should be able to repair the corrupted SQL component. However, if you are still getting the same error, then you should use a third-party SQL database recovery software to perform SQL recovery. Such MDF recovery tools are read-only in nature that do not overwrite the existing database while scanning.
Stellar Phoenix SQL Data Recovery is a master database file recovery software that recovers MDF files from all instances of logical corruption.
Know how to remove SQL row error 8994 in MS SQL database with SQL recovery tool. http://www.sqlrecoverysoftware.net/blog/sql-error-8994.html
ReplyDelete