Wednesday, December 16, 2009

Resolving “Row error: Object ID....created NOT NULL, but is NULL in the row ”

SQL Server database corruption can have severe effects on the records stored in database components. One of the effect that most database users might encounter is wrong values being displayed under a particular column. Few major causes for database corruption can be improper system shutdown, SQL Server malfunction, virus infection, and more. An easy way to access data after corruption due to any of the above reasons is to restore the data from an updated backup. However, there might be circumstances where you have either not created any backup or backup itself is damaged corrupted. In such situations, you will need to search for advanced MS SQL Repair application that can systematically repair your corrupted database.

For example, the below error message pops up each time you attempt to mount your SQL Server database:

“Row error: Object ID O_ID, index ID I_ID, page ID P_ID, row ID S_ID. Column 'COLUMN' was created NOT NULL, but is NULL in the row.”

As the error message states, the columns which had NOT NULL values, now hold NULL values. The above error is 'severity level 16' message and can occur either due to software or hardware corruption issues.


The above error message can be resolved by following underneath error messages:

To isolate the problem caused due to physical damage of the system component, you will need to swap out the damaged system components with new components.
To completely resolve the issues created due to logical damage, you will need to execute DBCC CHECKDB command with appropriate repair clause.
Restore the database by using an updated database backup.

While the above resolutions are helpful in most of the issues, they fail in below situations:

DBCC fails to repair
Unavailability of database backup

To overcome both the above database corruption issues, you will need to use effective SQL Database Recovery software. Such SQL Repair tools thoroughly scan your database and allow you to restore the repaired database at user-specified location. These tools can be easily understood even by novice user.

No comments:

Post a Comment