Sharepoint database 'docs' corruption ... what if?

  • Long story short 😀

    We inherited a sharepoint database on SQL2k with corruption dating back 2 years (so no usable backups). Corruption is affecting only 1 document stored in the docs table (99% sure - from the checkdb results it looks like one of the pages storing this document is damaged, opening the document from Sharepoint fails and gives a a corresponding 823 error in the log)

    DBCC CheckDB says that repair_allow_data_loss is the minumum repair option

    However - what would happen if the document was just deleted from Sharepoint? It sounds plausible, but I'm assuming that there is more to it than that 😀

  • The delete would probably fail.

    Please run the following and post the full and complete output.

    DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • The xxxs held the details of the file that was identified

    Server: Msg 8929, Level 16, State 1, Line 1

    Object ID 1993058136: Errors found in text ID 412871884800 owned by data record identified by RID = (1:14232938:0) SiteId = xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx and DirName = 'xxxx/xxxx/xxxxx/xxxxxx/xxxxxxx' and LeafName = 'xxxxxxxxxxxx'

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 1993058136, index ID 255: Page (1:5051560) could not be processed. See other errors for details.

    Server: Msg 8939, Level 16, State 1, Line 1

    Table error: Object ID 1993058136, index ID 255, page (1:5051560). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.

    Server: Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 1993058136. The text, ntext, or image node at page (1:5051560), slot 0, text ID 412871884800 is referenced by page (1:5051497), slot 0, but was not seen in the scan.

    CHECKDB found 0 allocation errors and 4 consistency errors in table 'Docs' (object ID 1993058136).

    CHECKDB found 0 allocation errors and 4 consistency errors in database 'databasename'.

    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (databasename).

  • In that case, since it's a single text page, deleting the doc may remove the corruption (or may not). CheckDB with repair will just remove that one document

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Excellent thanks, we'll try a deletion & if it doesn't work, a repair

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply