Post reply

SQL 2005 Database Integrity Check Error

  • November 14, 2007 at 2:51 pm

    #119471

    When running a database maintenance plan to check the integrity, the following error has appeared.

    Failed:(-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS

    " failed with the following error: "The In-row data RSVD page count for object "MyTable", index ID 0, partition ID 128201655517184, alloc unit ID 128201655517184 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.

    CHECKDB found 0 allocation errors and 1 consistency errors in table 'MyTable' (object ID 1956202019).

    CHECKDB found 0 allocation errors and 1 consistency errors in database 'MyDB'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    Any ideas on what this error is and what the best and easiest fix would be?

    I could use anyones assistance on this.

  • November 15, 2007 at 12:51 am

    #751393

    The number of pages that the metadata says belong to the table don't agree with the number of pages actually allocated.

    As the error says, try running DBCC UPDATEUSAGE and see if it fixes the problem.

    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

  • November 15, 2007 at 9:03 am

    #751565

    I believe I have it figured out now. Thanks for the help.

  • February 29, 2008 at 2:06 pm

    #784044

    Scott Pearson (11/15/2007)

    I believe I have it figured out now. Thanks for the help.

    Scott, what did you do to fix it? Did you run DBCC UPDATEUSAGE?

    Kindest Regards, Rod Connect with me on LinkedIn.

  • August 1, 2008 at 6:38 am

    #851828

    Hi Gail, saw your reply to this thread, does this mismatch between the metadata and the physical allocation have any impact any the data resturned by any operations on the database.

    Essentially could this cause incorrect data to be returned by a query or a failure to return the correct recordset for a query

    Many thanks

  • August 1, 2008 at 7:36 am

    #851871

    Simon (8/1/2008)

    Hi Gail, saw your reply to this thread, does this mismatch between the metadata and the physical allocation have any impact any the data resturned by any operations on the database.

    Essentially could this cause incorrect data to be returned by a query or a failure to return the correct recordset for a query

    Many thanks

    Don't think so, just incorrect space used and space available reports.

    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

  • August 1, 2008 at 9:11 am

    #851969

    Thanks for that Gail

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

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