Problem:
Server: Msg 8964, Level 16, State 1, Line 1
Table
error: Object ID 515532920. The text, ntext, or image node at page
(1:377289), slot 1, text ID 897099563008 is not referenced.
Table error: Object ID
515532920. The text, ntext, or image node at page (1:1124698), slot 1,
text ID 896822476800 is not referenced.
CHECKDB found 0 allocation errors and 8 consistency errors in table 'CC_Document' (object ID 515532920).
CHECKDB found 0 allocation errors and 8 consistency errors in database 'crmproded'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (crmproded ).
Cause:
The text fragments
listed in the CHECKDB output aren't referenced by any rows in the
clustered index. When a data row has a LOB value then usually (unless
you've tweaked the text_in_row option) the LOB value is stored off-row
with a root pointer stored in the data row itself. What's happened in
this case is that some data rows have been deleted but their
corresponding LOB values have not been. This should be benign but we
should try to work out why it happened.
Server: Msg 8964, Level 16, State 1, Line 1
Table
error: Object ID 515532920. The text, ntext, or image node at page
(1:377289), slot 1, text ID 897099563008 is not referenced.
Table error: Object ID
515532920. The text, ntext, or image node at page (1:1124698), slot 1,
text ID 896822476800 is not referenced.
CHECKDB found 0 allocation errors and 8 consistency errors in table 'CC_Document' (object ID 515532920).
CHECKDB found 0 allocation errors and 8 consistency errors in database 'crmproded'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (crmproded ).
Cause:
The text fragments
listed in the CHECKDB output aren't referenced by any rows in the
clustered index. When a data row has a LOB value then usually (unless
you've tweaked the text_in_row option) the LOB value is stored off-row
with a root pointer stored in the data row itself. What's happened in
this case is that some data rows have been deleted but their
corresponding LOB values have not been. This should be benign but we
should try to work out why it happened.
powered by performancing firefox
No comments:
Post a Comment