Determine which index page belongs to which table

  • Hi

    How to determine which index page belongs to which table

    Error: 644, Severity: 21, State: 3

    Could not find the index entry for RID '16d988960100' in index page

    (1:59821), index ID 0, database 'MYDB'.

    Books Online says that I need to "Identify which table and index correspond to the index page number".

    I have figured out that in (1:59821), the 1 is the file number and 59821 is the page number.

    Thanks

    Parthi

    Thanks
    Parthi

  • Rather than looking at that right now, could you post the full output of checkDB and I can help you with resolving it.

    DBCC CheckDB (<Database Name>) WITH No_INFOMSGS, ALL_ERRORMSGS

    To find the object that owns a page, you need an undocumented command - dbcc page. There's a fair bit available on the net (Paul Randal's blog being the main place)

    DBCC TRACEON(3604) -- to direct the output to the client

    DBCC Page(<Database ID>,1,59821)

    DBCC TRACEOFF(3604)

    This may be worth a read

    http://www.sqlservercentral.com/articles/Corruption/65804/

    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
  • GilaMonster (10/12/2010)


    DBCC TRACEON(3604) -- to direct the output to the client

    DBCC Page(<Database ID>,1,59821)

    DBCC TRACEOFF(3604)

    This may be worth a read

    http://www.sqlservercentral.com/articles/Corruption/65804/

    Hi Gila shaw

    Thanks for your replay as it is local i did DBCC CheckDB () WITH No_INFOMSGS.

    Actually why it is happening

    what could be cause for it.

    if it has occured in production can i run DBCC CheckDB () WITH No_INFOMSGS

    Thanks

    Parthi

    Thanks
    Parthi

  • parthi-1705 (10/12/2010)


    Thanks for your replay as it is local i did DBCC CheckDB () WITH No_INFOMSGS.

    And? If you don't post the output I can't help you in fixing it.

    Actually why it is happening

    what could be cause for it.

    The majority of the time corruption is caused by problems with the IO subsystem. Check windows event logs, SAN logs, RAID logs, etc.

    if it has occured in production can i run DBCC CheckDB () WITH No_INFOMSGS

    Go read my article (again). It tells you what the steps are if you get corruption.

    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 4 posts - 1 through 3 (of 3 total)

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