Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

DBCC CHECKDB with Data_Purity consistency errors Expand / Collapse
Author
Message
Posted Monday, September 17, 2012 9:08 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 4:37 PM
Points: 81, Visits: 641
DBCC CHECKDB with Data_Purity consistency errors

This is the first time I ran this command and had errors. I am new to the company and they never had a DBA before. There SQL server has been upgraded all the way back from SQL 7 to 2008 R2.

I ran the DBCC CHECKDB with Data_Purity consistency errors and here are a few if someone could point me in the correct direction to try and fix some of these which there are 11000

They all are similar to these

Msg 2570 Level 16 State 3 Line 1
Page (1:275392) slot 2 in object ID 536649255 index ID 1 partition ID 72057594088390656 alloc unit ID 72057594089635840 (type "In-row data"). Column "LTV" value is out of range for data type "real". Update column to a legal value.

Msg 2570 Level 16 State 3 Line 1
Page (1:275392) slot 8 in object ID 536649255 index ID 1 partition ID 72057594088390656 alloc unit ID 72057594089635840 (type "In-row data"). Column "LTV" value is out of range for data type "real". Update column to a legal value.

Msg 2570 Level 16 State 3 Line 1
Page (1:275392) slot 15 in object ID 536649255 index ID 1 partition ID 72057594088390656 alloc unit ID 72057594089635840 (type "In-row data"). Column "LTV" value is out of range for data type "real". Update column to a legal value.

Msg 2570 Level 16 State 3 Line 1
Page (1:275393) slot 0 in object ID 536649255 index ID 1 partition ID 72057594088390656 alloc unit ID 72057594089635840 (type "In-row data"). Column "LTV" value is out of range for data type "real". Update column to a legal value.
Post #1360269
Posted Monday, September 17, 2012 9:56 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 9:36 AM
Points: 42,765, Visits: 35,863
Take a look at this article. http://www.sqlservercentral.com/articles/65804/

There's a section in there on data purity errors.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1360300
Posted Monday, September 17, 2012 10:22 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 4:37 PM
Points: 81, Visits: 641
Thanks I started to update the tables to the correct data type. Would you know of an easy way to update the value with say 400000 rows. I have one table left to update and its complaining about large size of data then errors out.

Much appreciated thanks
Post #1360314
Posted Monday, September 17, 2012 10:37 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 9:36 AM
Points: 42,765, Visits: 35,863
You're going to have to identify which row have the bad values and update them (or you can just update the entire table and set the column say to 0, but then you lose whatever meaning that column had)

The article I referenced has a link to a kb article that explains how to identify the rows with the bad values.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1360323
Posted Tuesday, September 25, 2012 8:40 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 4:37 PM
Points: 81, Visits: 641
Thanks, I have been working on this still. I have figured out that I need to change the data type to nvarchar then update all the values that had NaN to 0. The problem I am having is once I'm completed on updating those values. I then change the data type to Decimal this works on the smaller tables but the ones with 200000 plus rows error out.

Any suggestions on how to get past that? I have even scripted out the table to move the data over then drop that table but that also errors out.

Thanks
Post #1364090
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse