Post reply

Difference between shrinking a database and shrinking individual files separately

  • August 5, 2017 at 2:06 pm

    #332097

    Hi All,
    I've planned to free up some space in our database by dropping some tables that are no more required . Weighing between the idea of shrinking the database in one go and shrinking individual files . Pls advise which option is better with some pros and cons. Thank you.

    Arshad

  • August 6, 2017 at 4:42 am

    #1954225

    They're both terrible.
    Shrinking the DB just shrinks all the files in it (including the log file)

    Unless you expect the space freed up to not be used in some time (6 months or more) it may be better just to leave the DB as-is. SQL will re-use the space in the data files.

    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

  • August 7, 2017 at 4:50 am

    #1954275

    GilaMonster - Sunday, August 6, 2017 4:42 AM

    They're both terrible.
    Shrinking the DB just shrinks all the files in it (including the log file)

    Unless you expect the space freed up to not be used in some time (6 months or more) it may be better just to leave the DB as-is. SQL will re-use the space in the data files.

    Hi Gail,
    Thank you for the answer and the advice.

    Arshad

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

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