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


REPAIR_ALLOW_DATA_LOSS


REPAIR_ALLOW_DATA_LOSS

Author
Message
baposts
baposts
Forum Newbie
Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)

Group: General Forum Members
Points: 7 Visits: 4
here is the results of the DBCC CHECKTABLE on the 2 tables I have issues with:

dbcc checktable('Web_claim')

Server: Msg 8928, Level 16, State 1, Line 1
Object ID 294292108, index ID 0: Page (1:1834754) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 294292108, index ID 0, page (1:1834754), row 62. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 154 and 53.
DBCC results for 'Web_Claim'.
There are 918513 rows in 6767 pages for object 'Web_Claim'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'Web_Claim' (object ID 294292108).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (Prod.dbo.Web_Claim ).

dbcc checktable('Claim_item')

Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1618820829, index ID 0: Page (1:1835914) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1618820829, index ID 0, page (1:1835914), row 8. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 1263 and 398.
DBCC results for 'Claim_Item'.
There are 5402810 rows in 314154 pages for object 'Claim_Item'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'Claim_Item' (object ID 1618820829).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (Prod.dbo.Claim_Item ).



And also one more thing

SELECT COUNT(*) FROM Web_CLAIM
--918,646 (DBCC 918513 , so i guess a loss of 133 rows)

SELECT COUNT(*) FROM Claim_item
--5,402,828 (DBCC 5402810, so i guess a loss of 8 rows)

Now I know the count of rows I might lose, but can I avoid losing it or could i in anyway identify the rows which I am gonna lose.

And we cant restore from the recent backups because this corruption happened 2 months back.
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