Post reply

DOUBT dbcc CheckTable

  • March 10, 2011 at 7:50 am

    #233823

    Hello Everybody

    I have a BIG table (18 Millions Registers) in a server (SQL Serv 2005), recently i pass a checktable and obtain this (see below the message) this require REPAIR_ALLOW_DATA_LOSS, im not worry because the problem is from other time , but my doubt is if is REALLY necessary to repair this, because i estimated to lose 100-200 registers if i choose to do the Repair with lose... the table are used from historical purposes and dont have new inserts... and i can make new backups...please help

    ERROR MESSAGE-----

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 0, page ID (1:258670). The PageId in the page header = (1:1913889).

    Msg 8928, Level 16, State 1, Line 1

    Object ID 1947870006, index ID 0: Page (1:258670) could not be processed. See other errors for details.

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 0, page ID (1:259409). The PageId in the page header = (1:1913886).

    Msg 8928, Level 16, State 1, Line 1

    Object ID 1947870006, index ID 0: Page (1:259409) could not be processed. See other errors for details.

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 0, page ID (1:259428). The PageId in the page header = (1:1913890).

    Msg 8928, Level 16, State 1, Line 1

    Object ID 1947870006, index ID 0: Page (1:259428) could not be processed. See other errors for details.

    Msg 8977, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 1. Parent node for page (1:258669) was not encountered.

    Msg 8976, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 1. Page (1:258670) was not seen in the scan although its parent (1:216018) and previous (1:258458) refer to it. Check any previous errors.

    Msg 8977, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 1. Parent node for page (1:258671) was not encountered.

    .

    .(A lot similar) x 30

    .

    Msg 8977, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 1. Parent node for page (1:258888) was not encountered.

    Msg 8978, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 1. Page (1:258890) is missing a reference from previous page (1:258670). Possible chain linkage problem.

    Msg 8976, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 1. Page (1:259409) was not seen in the scan although its parent (1:259314) and previous (1:259408) refer to it. Check any previous errors.

    Msg 8978, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 1. Page (1:259410) is missing a reference from previous page (1:259409). Possible chain linkage problem.

    Msg 8976, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 1. Page (1:259428) was not seen in the scan although its parent (1:259314) and previous (1:259427) refer to it. Check any previous errors.

    Msg 8978, Level 16, State 1, Line 1

    Table error: Object ID 1947870006, index ID 1. Page (1:259429) is missing a reference from previous page (1:259428). Possible chain linkage problem.

  • March 10, 2011 at 8:14 am

    #1297117

    Yes, you need to repair. You've already lost those registers, the pages they are on are unreadable. Querying them will throw errors.

    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

Viewing 2 posts - 1 through 1 (of 1 total)

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