TechTutorials - Free Computer Tutorials  







Record Check Failed in SQL Server 
 


Added: 08/18/2009, Hits: 4,875, Rating: 0, Comments: 0, Votes: 0
Add To Favorites | Comment on this article
An SQL Server database table might get corrupted due to unexpected crash, virus infection, application bugs and similar reasons. To troubleshoot all such issues, you require using your backup, running DBCC CHECKDB command or scanning the database using MDF Repair utilities.

For an instance, you might come across the similar error as below with your SQL Server database table:

“Table error: Object ID O_ID, index ID I_ID, page P_ID, row ROW_ID. Record check (CHECK_TEXT) failed. Values are VALUE1 and VALUE2.”

This errors is recorded as 2337 in SQL log and is encountered in different states.

Cause

SQL Server has performed CHECK_TEXT to test the integrity of row ROW_ID that it has failed. The values VALUE1 and VALUE2 vary depending on the state of error message as described below:

.State 40: Value1 (length of column) is greater than Value2 (maximum length specified in metadata).
.State 43:

1.Value1 (variant column's data length) is longer than Value2 (maximum length allowed of variant type)
2.Value1 is relational ID of column and Value2 is ). The error occurs due to check failure of computed or variant column.

.State 100: Value1 is invalid record type recorded on data page and Value2 is 0.
.State 101: Value1 (index record's size) is greater than Value2 (maximum allowed size in metadata)
.State 401: Value1 is invalid record type recorded on index page and Value2 is 0.
.State 510: Value1 (number of child links in a node) is more than Value2 (possible space in child link array) for node type BLB_LARGE_ROOT_2, BLB_LARGE_INTERNAL

or BLB_LARGE_ROOT
.State 511: Value1 (number of child links in a node) is more than Value2 (maximum fan-out defined)
.State 512: Value1( number of children in a text node) is larger than Value2 (available space)
.State 513: Value1 (minimum record length) cannot hold Value2 (BlobMan::DATA_NODE_HEAD_SIZE)

Solution

Use these methods to solve error 2537:

  • Execute DBCC CHECKDB to know the required repair clause and run the same command with the suggested repair clause.

  • Since performing the above steps can cause data loss, use repair mdf file tools that allow achieving safe and complete SQL database repair results. MDF Repair utilities scan the damaged database and serve as most valid tools to restore it.

    Stellar Phoenix SQL Recovery is an advanced mdf file repair tool that repairs and restores damaged SQL Server database created with SQL Server 2008, 2005 and 2000. It is a comprehensive database repair product for all database objects and is embedded with unique set of features. It is compatible with Windows Vista, XP, 2003, 2000 and NT.




  • Comments (0)

    Be the first to comment on this article


    Related Items








    7 Seconds Resources, Inc.




    IT Showcase