Post reply

Database needs reducing in size

  • October 19, 2012 at 5:10 am

    #393424

    Hi

    We have a database supplied by a 3rd party for their application that kept every record relating to messages being sent/received form it. We now have it configured to only keep so many messages but the database is quite large with lots of empty space as lots of the old messages have been pruned.

    I've read lots about shrinking databases and its generally considered a bad idea due to issues with fragmentation of indexes (I think!). I need to get this DB smaller because of disk space issues and wondered what the best approach would be.

    Thanks

  • October 19, 2012 at 5:37 am

    #1550807

    A once-off shrink (followed by index rebuilds) is not a problem. Just don't automate and schedule the shrinks.

    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

  • October 19, 2012 at 6:34 am

    #1550834

    OK, Thanks for the quick reply.

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

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