Possible schema corruption message when reindexing

Question

Post reply

Possible schema corruption message when reindexing

brian_winzeler

Mr or Mrs. 500

Points: 564
More actions
September 1, 2010 at 8:41 am

#228519

In the last couple of days I've noticed the reindex operations (rebuilding indexes with fragmentation > then 10%), have been failing with this message upon hitting certain indexes:
Msg 211, Level 23, State 5, Line 1
Possible schema corruption. Run DBCC CHECKCATALOG.
I've identified the index in question to be the tables clustered index. DBCC CheckDB produces no errors. For some reason I can reorganize this index, but not rebuild. Any ideas why this would happen?
Our current idea to fix this is to drop and recreate the index. If this is the only way to fix this that's fine, but I would like a root cause if possible.

Viewing 4 posts - 1 through 3 (of 3 total)

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

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Does DBCC CheckCatalog return any errors?

What's the exact version of this SQL instance (SELECT @@version)

What options are on for that rebuild?

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

David Baffaleuf SSCrazy Points: 2159 More actions · Answer 2

Hi,

There was a bug fixed in SQL Server 2008 concerning rebuilding index using with drop existing and case mismatch. Is this the way you rebuild your indexes ?

cf the connect entry: http://connect.microsoft.com/SQLServer/feedback/details/301393/create-index-with-drop-existing-applied-to-an-index-supporting-a-primary-key-or-unique-constraint-yields-possible-schema-corruption-message-if-index-name-provided-in-different-case

David B.

brian_winzeler Mr or Mrs. 500 Points: 564 More actions · Answer 3

The version is 9.0.4035.

The current command for rebuilding is pulling the names from sql server so I doubt a case mismatch is the problem. According to the statements they're matching up.

Here is the alter index command being run:

ALTER INDEX PK_index ON dbo.table REBUILD WITH (FILLFACTOR = 85) .

DBCC CheckCatalog returns no errors.