You maintain a Microsoft SQL Server database named DB1. You create a maintenance plan to run the DBCC CHECKDB command regularly to identify possible database corruption.
DB1 has the following table:
Filegroup FG1 is read-only. You set FG1 to read-only and create a full backup.
The maintenance plan does not identify any errors after the backup.
However, you observe the following error in the logs.
Msg 8979, Level 16, State 1, Line 1 Table error: Object ID 885578193, index ID 3, partition ID***, alloc unit ID *** (type In-row data). Page (***) is missing a reference from previous page (***). Possible chain linkage problem.
You need to resolve the database corruption issues.
What should you do?
A . Restore FG1 from the most recent backup.
B . Drop and rebuild index ID 3 in Table1.
C . Change FG1 from read-only to read/write.
D . Update the statistics on index ID 3 in Table1.
E . Backup the tail-logs in DB1.
Answer: A
Explanation:
A full restore of the database is the safest bet in case of a chain linkage problem.
References: http://sqlsoldier.net/wp/sqlserver/introductiontointegritychainlinkageproblems
Leave a Reply