SharePoint 數據庫的一致性錯誤

當我使用以下命令檢查我的數據庫（SQL Server 2008 R2、Windows Server 2008 R2、SharePoint 2007 DB）時：

DBCC CheckDB

我得到 12 個一致性錯誤（見下文）。

是修復它的唯一方法repair_allow_data_loss嗎？

還有一種方法可以獲取文件名並刪除我的 SharePoint 中的文件嗎？

Msg 8928, Level 16, State 1, Line 1
Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057594044940288 (type LOB data): Page (1:5718) could not be processed.  See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057594044940288 (type LOB data), page (1:5718). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -4.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057594044940288 (type LOB data). The off-row data node at page (1:5718), slot 0, text ID 410976256 is referenced by page (1:5682), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057594044940288 (type LOB data): Page (1:62999) could not be processed.  See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057594044940288 (type LOB data), page (1:62999). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -4.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057594044940288 (type LOB data). The off-row data node at page (1:62999), slot 0, text ID 1788739584 is referenced by page (1:62231), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057594044940288 (type LOB data): Page (1:72779) could not be processed.  See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057594044940288 (type LOB data), page (1:72779). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -4.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057594044940288 (type LOB data). The off-row data node at page (1:72779), slot 0, text ID 1898315776 is referenced by page (1:72782), slot 0, but was not seen in the scan.
Msg 8929, Level 16, State 1, Line 1
Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057599818924032 (type In-row data): Errors found in off-row data with ID 1898315776 owned by data record identified by RID = (1:72370:23)
Msg 8929, Level 16, State 1, Line 1
Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057599818924032 (type In-row data): Errors found in off-row data with ID 410976256 owned by data record identified by RID = (1:72375:20)
Msg 8929, Level 16, State 1, Line 1
Object ID 293576084, index ID 1, partition ID 72057599643549696, alloc unit ID 72057599818924032 (type In-row data): Errors found in off-row data with ID 1788739584 owned by data record identified by RID = (1:72448:16)
CHECKDB found 0 allocation errors and 12 consistency errors in table 'AllDocStreams' (object ID 293576084).
CHECKDB found 0 allocation errors and 12 consistency errors in database 'DatabaseName'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (DatabaseName).

如果可能，從備份中恢復。

“允許數據失去”確實是一個糟糕的選擇。

這篇優秀的文章將幫助您：

http://www.sql-server-pro.com/dbcc-checkdb.html

我最近在這裡就如何處理腐敗問題給出了非常有力的解釋。

看看吧。我會先嘗試刪除/重新創建索引，如果它不能解決問題，您可能需要在您的情況下執行 repair_allow_data_loss。

引用自：https://dba.stackexchange.com/questions/27163