Error durinng using DBCC CHECKDB

Last Post 07 Feb 2011 01:20 AM by bipsa. 3 Replies.
AddThis - Bookmarking and Sharing Button
Author Messages
samjoseph74
New Member
New Member

--
07 Jun 2009 11:03 PM
When I check my database integrity using DBCC CHECKDB with DATA_PURITY option enabled and it gives the below error message:

“Msg 2570, Level 16, State 2, Line 1
Page %S_PGID, slot %d in Object %d Index %d Column %.*ls value %.*ls is out of range for data type "%.*ls". Update column to a legal value.”

Please suggest me what to do to overcome this problem.

Davidpoul
New Member
New Member

--
11 Jun 2009 11:05 PM
To correct the above issue, you need to follow any of the below methods:

You should find the affected rows and manually update them with correct values. To do this, you can execute T-SQL (Transact-SQL) queries against the table or alternatively, refer to the information provided by error 2570. You can set it to any of acceptable default or specific value.

Note: You can’t run DBCC command to repair the database as it can’t determine the value to be placed instead of invalid column value.

In case if affected rows are large in number and it is not possible to update them manually, you can restore them from backup.
If the above measure is not feasible because of backup unavailability or corruption, you need to use MDF Recovery applications to safely repair and restore your database. Such MDF Repair software use powerful scanning algorithms and offer advanced repair and restoration options together with interactive user interface.
SQLUSA
New Member
New Member

--
18 Jun 2009 04:29 AM
What is the real message?

What you gave is the printf pattern of the message from documentation.

Kalman Toth, SQL Server 2008 Training
http://www.sqlusa.com
bipsa
New Member
New Member

--
07 Feb 2011 01:20 AM
The affected rows should be found and updated manually with the actual values they should have. A T-SQL query is so far found helpful in the task. DBCC is not capable of determining & putting values to it rows. So, it is better to restore database from backup, however if you don’t have that use mssql database repair to repair corruption encountered and safely restore lost & inaccessible data back.


Acceptable Use Policy
---