• DBCC ChecKDB('DB1') WITH NO_INFOMSGS, ALL_ERRORMSGS

    errors:-

    Msg 8964, Level 16, State 1, Line 1

    Table error: Object ID 553769030, index ID 1, partition ID 72057595610529792, alloc unit ID 72057594055688192 (type LOB data). The off-row data node at page (1:87637), slot 19, text ID 71636287488 is not referenced.

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:113515) allocated to object ID 553769030, index ID 1, partition ID 72057595610529792, alloc unit ID 72057595737145344 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    Msg 8976, Level 16, State 1, Line 1

    Table error: Object ID 553769030, index ID 1, partition ID 72057595610529792, alloc unit ID 72057595737145344 (type In-row data). Page (1:113515) was not seen in the scan although its parent (1:110561) and previous (1:113514) refer to it. Check any previous errors.

    Msg 8978, Level 16, State 1, Line 1

    Table error: Object ID 553769030, index ID 1, partition ID 72057595610529792, alloc unit ID 72057595737145344 (type In-row data). Page (1:113516) is missing a reference from previous page (1:113515). Possible chain linkage problem.

    CHECKDB found 0 allocation errors and 276 consistency errors in table 'table1' (object ID 553769030).

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:117158) allocated to object ID 1606296782, index ID 0, partition ID 72057594863091712, alloc unit ID 72057594960216064 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    CHECKDB found 0 allocation errors and 1 consistency errors in table 'Table2' (object ID 1606296782).

    CHECKDB found 0 allocation errors and 282 consistency errors in database 'DB1'.

    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (DB1).

    I think Restoration is the only option. Although this is a Test DB for which we had back up also.

    Reagrds