July 7, 2017 at 11:50 pm
hi,
Following is the out put of dbcc checkdb.
Msg 5282, Level 16, State 2, Line 1Table error: Object ID 683941979, index ID 1, partition ID 72057608853127168, alloc unit ID 72057610800988160 (type In-row data), page (30426:11). The header of the page is invalid: the IS_IN_SYSXACT flag bit is set.Msg 5282, Level 16, State 1, Line 1Table error: Object ID 683941979, index ID 1, partition ID 72057608853127168, alloc unit ID 72057610800988160 (type In-row data), page (61501:11). The header of the page is invalid: the IS_IN_SYSXACT flag bit is set.CHECKDB found 0 allocation errors and 2 consistency errors in table 'rptpb' (object ID 683941979).CHECKDB found 0 allocation errors and 2 consistency errors in database 'abc'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (abc).
generally i have seen when currption in any index comes , it does not put the database in suspect mode,
i want to know why this time it has put it in suspect mode.
secondly , can i find the sources of this error.
yours sincerley
July 8, 2017 at 6:35 am
First things first, repair with allow_data_loss is not the first thing you should try. It's a last resort. It loses data. How much, hard to tell.
Restoring from a clean backup is the recommended method of fixing corruption.
Most corruption is caused by IO subsystem problems, and a database will go into the suspect state if corruption is detected during a rollback or a database recovery.
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
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply