SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


DBCC CHECKDB with Data_Purity consistency errors


DBCC CHECKDB with Data_Purity consistency errors

Author
Message
D-SQL
D-SQL
Old Hand
Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)

Group: General Forum Members
Points: 387 Visits: 807
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.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)

Group: General Forum Members
Points: 228441 Visits: 46342
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, MVP, M.Sc (Comp Sci)
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


D-SQL
D-SQL
Old Hand
Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)

Group: General Forum Members
Points: 387 Visits: 807
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
GilaMonster
GilaMonster
SSC Guru
SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)

Group: General Forum Members
Points: 228441 Visits: 46342
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, MVP, M.Sc (Comp Sci)
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


D-SQL
D-SQL
Old Hand
Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)Old Hand (387 reputation)

Group: General Forum Members
Points: 387 Visits: 807
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search