Corrupt database

[mabroman]

Hi,
I have a problem with one of our databases that reports the following errors after running DBCC CHECKDB WITH NO_INFOMSGS, ALL_ERRORMSGS . Unfortunately there is no backup to restore (don´t ask why!) and my question is if there are any possibility to correct the database without exporting the data to a new one?

Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3851, State 1: An invalid row (class=112,depid=1342332930,depsubid=2) was found in the system table sys.syssingleobjrefs (class=112).
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3855, State 1: Attribute (referenced_object_id=1413580074,referenced_column_id=1) exists without a row (constraint_object_id=1982070247,constraint_column_id=1) in sys.foreign_key_columns.
CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.
Msg 8944, Level 16, State 28, Line 1
Table error: Object ID 74, index ID 1, partition ID 281474981560320, alloc unit ID 281474981560320 (type In-row data), page (1:2405), row 150. Test (!(hdr->r_tagA & (RecConst::VERSION_MASK | RecConst::RECTAG_RESV_B))) failed. Values are 144 and 129.
Msg 8944, Level 16, State 28, Line 1
Table error: Object ID 74, index ID 1, partition ID 281474981560320, alloc unit ID 281474981560320 (type In-row data), page (1:2405), row 150. Test (!(hdr->r_tagA & (RecConst::VERSION_MASK | RecConst::RECTAG_RESV_B))) failed. Values are 144 and 129.
Msg 8928, Level 16, State 1, Line 1
Object ID 74, index ID 1, partition ID 281474981560320, alloc unit ID 281474981560320 (type In-row data): Page (1:2405) could not be processed. See other errors for details.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 74, index ID 1, partition ID 281474981560320, alloc unit ID 281474981560320 (type In-row data). Page (1:2003) is missing a reference from previous page (1:2405). Possible chain linkage problem.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 74, index ID 1, partition ID 281474981560320, alloc unit ID 281474981560320 (type In-row data). Page (1:2405) was not seen in the scan although its parent (1:3896) and previous (1:2002) refer to it. Check any previous errors.
CHECKDB found 0 allocation errors and 5 consistency errors in table 'sys.syssingleobjrefs' (object ID 74).
CHECKDB found 0 allocation errors and 7 consistency errors in database 'Tmp112741_20151'.

Grateful for any help.

[ahmeds08]

If you don't have a good backup to restore, then the other thing you could do is use a third party tool or run dbcc checkdb repair_allow_data_loss.

[mabroman]

Hi Ahmeds08,
Unfortunately the problem has been present for a while, but invoked in Connection with a program update, so backup is out of the question. Also I´ve tried checkdb with the suggested parameter without success. You mentioned third party tool, do you have any experience from such tool, and where to get it?

Thanks

[ahmeds08]

whats was the issue when you executed dbcc checkdb repair_allow_data_loss?
can you share the output?

[jason_clark]

Hiiee
As you have said that you don't have any backup, you will not be able to repair inconsistencies in the system catalog. So, you have to use third party tool like SysTools SQL Recovery for repairing your database.