Post reply

The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.

  • September 9, 2012 at 7:49 am

    #280981

    restored database from SQL2000 to SQL 200R2

    After restore I got bunch message in the logs.

    Any idea? what is fix? Or i can ignore the warning?

    Message

    Warning: A column nullability inconsistency was detected in the metadata of index "_WA_Sys_OPERATION_SEQ_NUM_10566F31" (index_id = 4) on object ID 274100017 in database "DB_name". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.

  • September 9, 2012 at 8:08 am

    #1535474

    And, did you run CheckTable as the error said? If so what's the output?

    If not, please run this and post the full and unedited results.

    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

  • September 9, 2012 at 9:04 am

    #1535479

    Hi Gila

    Command(s) completed successfully.

  • September 9, 2012 at 9:34 am

    #1535480

    Is the statistic _WA_Sys_OPERATION_SEQ_NUM_10566F31 still present?

    If so, maybe drop it. SQL can always recreate it if it needs to.

    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 9, 2012 at 10:21 am

    #1535483

    Gila,

    1)There wont be any issue, If I drop?

    2)After dropping, Can i recreate?

    there are approx 100 of them in sql logs for that database.

  • September 9, 2012 at 10:25 am

    #1535484

    No issues, as I said SQL can recreate it if necessary.

    Yes, drop any stats that were mentioned in 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 9, 2012 at 10:48 am

    #1535490

    One of the steps of upgrading from 2000 to anything later (2005, 2008, 2008R2, 2012) is to update all statistics. That is a post-upgrade requirement.

    If you perform that step - it should take care of these types of errors.

    The next item you want to perform is: DBCC CHECKDB(database) WITH DATA_PURITY;

    This is a one time operation and should complete successfully. If it doesn't complete successfully, fix the errors either on the 2000 instance (because someone manually modified the system tables) or on the 2005 instance by recreating the affected objects.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

Viewing 7 posts - 1 through 6 (of 6 total)

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