Please interpret the DBCC CHECKDB output and suggest how much my db is corrupt

Question

Hi All,
DBCC CHECKDB on my database in simple recovery model failed. Please find the error message below. I copied the backup and restored on
a test server and ran DBCC CHECKDB with repair_allow_data_loss. Below bold lines was the one got repaired. Does ths caused any loss of user data. Kindly suggest.
 Repair: The Clustered index successfully rebuilt for the object "sys.sysobjvalues" in database "****".
Repair: The page (1:629823) has been deallocated from object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data).
Executing the query "DBCC CHECKDB(N'****') WITH NO_INFOMSGS
" failed with the following error: "Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -3212797581117423616 (type Unknown), page (40634:1181196049). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
Incorrect PFS free space information for page (1:160) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 95_PCT_FULL, actual value 50_PCT_FULL.
Incorrect PFS free space information for page (1:3427) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 80_PCT_FULL, actual value 95_PCT_FULL.
Incorrect PFS free space information for page (1:22426) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 100_PCT_FULL, actual value 50_PCT_FULL.
Incorrect PFS free space information for page (1:26439) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 50_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:27700) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 95_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:27701) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 80_PCT_FULL, actual value 95_PCT_FULL.
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data): Page
(1:629823)could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 7 consistency errors in table 'sys.sysobjvalues' (object ID 60).
CHECKDB found 0 allocation errors and 8 consistency errors in database '****'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (****).
Thanks Lakshmana Y

Answer 1

Actually there might be a way I am not sure how much accurate that would be but. Lakshman you can run dbcc checkdb repair_allow_data_loss with begin transaction and commit transaction
Begin transaction
dbcc checkdb('db_name', REPAIR_ALLOW_DATA_LOSS)
--Commit--Rollback
Before giving rollback you can check how much data you would loose.  Dont give commit. A more better approach would be take backup of database with continue_after_error( I know this might and might not work, just giving you options) restore on different
server with again continue_after_error and then run repair allow data loss there and see how much data you would loose. Also not constraints would also be removed after doing repair
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP