• jasona.work (5/7/2013)


    SQLRNNR (5/7/2013)


    Another option is to find the largest table in the database, multiply it by 1.5. Once you have that number, shrink the file to leave at least that amount of free space in the data file.

    Which sounds like a nice round number to me. Doesn't free up quite as much as I'd like, but still frees up about 30GB

    I should probably have included why to do that in my post.

    The reason is to avoid the multiple IO penalties to grow/shrink the file. If you leave that kind of free space, it permits the reindex operation to function without (hopefully) causing the database to grow.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events