Post reply

DBCC CHECKDB

  • September 14, 2014 at 5:06 am

    #293174

    hello all.

    I checked my Db with DBCC CHECKDB('DBName') WITH NO_INFOMSGS, ALL_ERRORMSGS

    and I got this errors:

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177860) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    what should I do?

  • September 14, 2014 at 11:07 am

    #1745329

    Please post the full output of that CheckDB statement, the entire thing, no edits, no omissions.

    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

  • September 15, 2014 at 12:32 am

    #1745366

    hi.

    how to reach output of checkDB?I post one of error wich was occured.

  • September 15, 2014 at 1:38 am

    #1745381

    elham_azizi_62 (9/15/2014)

    hi.

    how to reach output of checkDB?I post one of error wich was occured.

    Either re-run the command or check for SQLDUMPnnnn.txt file in the SQL Server Log directory.

    One error is not enough to assert the situation, the whole, unedited output is required.

    😎

  • September 15, 2014 at 2:28 am

    #1745388

    elham_azizi_62 (9/15/2014)

    how to reach output of checkDB?I post one of error wich was occured.

    Run it again if you didn't save the output. I need to see everything that CheckDB returned.

    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

  • September 15, 2014 at 5:41 am

    #1745433

    thank you for your reply Dear GilaMonster.this is checkDB Output:

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177842) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177843) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177844) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177845) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177846) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177847) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177848) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177849) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177850) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177851) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177852) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177853) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177854) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177855) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177856) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177857) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177858) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177859) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177860) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177861) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177862) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177863) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

    CHECKDB found 0 allocation errors and 22 consistency errors not associated with any single object.

    Msg 8909, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data), page ID (1:4911282) contains an incorrect page ID in its page header. The PageId in the page header = (1:4911010).

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:4911282) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:4911282), slot 0, text ID 35438133248 is referenced by page (1:4911275), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177841) could not be processed. See other errors for details.

    Msg 8939, Level 16, State 98, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data), page (1:5177841). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177841), slot 0, text ID 37571592192 is referenced by page (1:5177761), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177842) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177842), slot 0, text ID 37571592192 is referenced by page (1:5177761), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177843) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177843), slot 0, text ID 37571592192 is referenced by page (1:5177761), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177844) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177844), slot 0, text ID 37571592192 is referenced by page (1:5177761), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177845) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177845), slot 0, text ID 37571592192 is referenced by page (1:5177761), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177846) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177846), slot 0, text ID 37571592192 is referenced by page (1:5177761), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177847) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177847), slot 0, text ID 37571592192 is referenced by page (1:5177761), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177848) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177848), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177849) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177849), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177850) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177850), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177851) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177851), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177852) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177852), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177853) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177853), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177854) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177854), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177855) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177855), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177856) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177856), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177857) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177857), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177858) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177858), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177859) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177859), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177860) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177860), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177861) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177861), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177862) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177862), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data): Page (1:5177863) could not be processed. See other errors for details.

    Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:5177863), slot 0, text ID 37571723264 is referenced by page (1:5177763), slot 0, but was not seen in the scan.

    Msg 8929, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043695104 (type In-row data): Errors found in off-row data with ID 35438133248 owned by data record identified by RID = (1:4901379:6)

    Msg 8929, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043695104 (type In-row data): Errors found in off-row data with ID 37571723264 owned by data record identified by RID = (1:5161028:7)

    Msg 8929, Level 16, State 1, Line 1

    Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043695104 (type In-row data): Errors found in off-row data with ID 37571592192 owned by data record identified by RID = (1:5161028:9)

    CHECKDB found 0 allocation errors and 53 consistency errors in table 'T_DABIR_NamehFiles' (object ID 2121058592).

    CHECKDB found 0 allocation errors and 75 consistency errors in database 'ArakAttachDb'.

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

  • September 15, 2014 at 5:49 am

    #1745436

    Ok, not too bad.

    Do you have a clean backup from before the corruption occurred as well as an unbroken chain of log backups up to current time?

    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

  • September 15, 2014 at 4:13 pm

    #1745628

    For the error message like this "Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:5177842) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).", this is indicate the PageID in the page header is invalid(actually it is zero). And there are a lot of such error messages. It seems that some pages in your database are filled with all zeros.

    For the error message like this "Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:4911282), slot 0, text ID 35438133248 is referenced by page (1:4911275), slot 0, but was not seen in the scan.", which actually means a page (1:4911275) is referencing a slot in page (1:4911282), but the slot does not exist. Both page ID looks normal, so it is possible that one of the page is corrupt or both are corrupt.

    You can find more information about the SQL Server error messages at http://www.datanumen.com/sql-recovery/sql-server-problem.htm

  • September 15, 2014 at 5:18 pm

    #1745636

    bob199214 (9/15/2014)

    For the error message like this "Table error: Object ID 2121058592, index ID 1, partition ID 72057594038648832, alloc unit ID 72057594043629568 (type LOB data). The off-row data node at page (1:4911282), slot 0, text ID 35438133248 is referenced by page (1:4911275), slot 0, but was not seen in the scan.", which actually means a page (1:4911275) is referencing a slot in page (1:4911282), but the slot does not exist. Both page ID looks normal, so it is possible that one of the page is corrupt or both are corrupt.

    It means that one of the pages that was zeroed out contained text data, and since the page has been zeroed out, the scan couldn't find the off row data entry when it looked for it.

    In short, 24 pages or more of the data file has been overwritten with zeroes and multiple errors are being raised for each page damaged in that way. There's also some incorrect page IDs as well.

    The link you posted however is useless, it doesn't have any information at all about these specific 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

  • September 16, 2014 at 12:40 am

    This was removed by the editor as SPAM

  • September 16, 2014 at 3:06 am

    #1745704

    Thank you for your reply.

    In this situation Wich T-Sql command should I run for reparing this data?

  • September 16, 2014 at 3:10 am

    #1745706

    Before you go hunting a repair command, please answer my question.

    GilaMonster (9/15/2014)

    Do you have a clean backup from before the corruption occurred as well as an unbroken chain of log backups up to current time?

    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

  • September 16, 2014 at 4:30 am

    #1745721

    I have Backup every day but my data base is increased every moment and I need to whole Data from it.

  • September 16, 2014 at 4:32 am

    #1745722

    Can you afford to lose a pile of data from the table T_DABIR_NamehFiles? Probably around 50 odd rows.

    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

  • September 16, 2014 at 5:12 am

    #1745732

    No unfortunatly.Because every data is important for my customer's company.

Viewing 15 posts - 1 through 15 (of 19 total)

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