Home Forums SQL Server 2005 Data Corruption corrupt index (nonclustered primary key) after 2005 upgrade RE: corrupt index (nonclustered primary key) after 2005 upgrade

  • Sorry for any confusion.

    The important thing is that you check the system tables to determine if the index exists. I mentioned this in a couple of post earlier today but Iunfortunately I did not mention this in this post.

    Also in the Link it was implied to use an ALTER INDEX Command.

    Thank you for correcting me and looking into and answering the Forum Member's Question.

    Regards...

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/