Home » Topic » What to do When Index is Corrupted in SQL Server?

What to do When Index is Corrupted in SQL Server?

Barry Alllen ~ Modified: July 17th, 2018 ~ ~ 1 Minute Reading

Home › Forums › What to do When Index is Corrupted in SQL Server?

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • July 17, 2018 at 10:59 am #7226 Score: 0
    Barry Alllen
    Moderator
    25 pts

    Hello everyone! I have 2015 Database. When I ran DBCC CHECKDB command the output is;

    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:31462320) contains an incorrect page ID in its page header. The Page Id in the page header = (0:0).

    I think my database is corrupted.

    I also ran Repair_Rebuild, but this also failed.

    Do I have a corrupted index, IF yes how can I find table name and actual index?

    July 20, 2018 at 9:32 am #7245 Score: 0
    Eddie Thwan
    Moderator
    44 pts

    If the repair option is “Repair with the Data Loss” I suggest you to restore from your backup otherwise you may not be able to know 100% what data is lost? If you allow data loss you may well have Foreign key inconsistencies and all ghastly outcomes also.

    July 24, 2018 at 10:42 am #7256 Score: 0
    Natalie Chopra
    Moderator

    Just repeat DBCC CHECKDB (after each repair) to see if there is any other Repair Command Request, and then run that and then repeat the DBCC CHECKDB, until you get a “clean” outcome.
    There is a table in MSDB and if that has only rows in it that may suggest falling hardware.
    For easily to understand just go through this article it may helps you a lot.
    “How do I know If Index is Corrupted in SQL Server?” I have also got solution by this article when I got stucked http://www.sqlmvp.org/how-to-check-if-index-is-corrupted-in-sql-server/.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.