Post reply

Long runing Database Integrity Check after aborted index creation.

  • June 29, 2011 at 2:06 pm

    #389865

    Hi, I was wondering if I can get any advice on a problem we our having.

    An index was being created on a table in SQL Server 2005, this was on a large table and before it completed the transaction was aborted.

    Since that's happened the weekly database integrity check now takes alot longer, over an hour longer then it used to.

    Is this related and if so is there a way I can get the database integrity check back to normal running times?

    Any help appreciated.

  • July 18, 2011 at 5:45 am

    #1354168

    I'm thinking that perhaps the database size expanded a lot in preparing for the new index creation (and you say it was a large table) and therefore its taking longer for the checkdb to run due to the larger db file size.

Viewing 2 posts - 1 through 1 (of 1 total)

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