Results 1 to 2 of 2
  1. #1
    Join Date
    Jul 2002

    Unanswered: Index reported as corrupt after upgrading to 2005

    After upgrading a server from SQL Server 2000 to 2005,
    an index was suddenly being reported as corrupt in the SQL Server log
    (probably every time an Insert was done). DBCC CHECKDB / CHECKTABLE
    reported no errors, with or without the new WITH DATA_PURITY option.

    Anyone else experienced something similar?

    How can an index be reported as corrupt when DBCC doesn't report it?

    Dropping and re-creating the index solved the problem.
    I've restored a backup of the database (made before dropping/re-creating
    the index) to try repeating the problem, but no success so far.
    Last edited by Coolberg; 10-30-06 at 11:00.

  2. #2
    Join Date
    Jan 2003
    Provided Answers: 11
    The only data purity issue I have had in SQL 2005 so far has been with an XML index on a set of XML documents that may or may not be well formed. The developers are rethinking their strategy at the moment.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts