• kevaburg (12/10/2016)


    Ed Wagner (12/10/2016)


    kevaburg (12/9/2016)


    Try a shrinkdatabase:

    exec sp_msforeachdb 'DBCC SHRINKDATABASE [?]';

    It is far from ideal and you will most likely experience performance problems during the run (do it in a maintenance window) but if you have significant white space in a datafile you could win it back. That could win you enough time to physically increase the volume by whatever means.

    The problem is what happens if you have a lot of data movement and this white space builds up at a rapid rate again.

    This will get you some space back, but it'll also fragment your indexes to 99%. Rebuilding them will bloat the size of the data file and you'll be right back where you are now.

    Agreed. Then perhaps now is a good time to identify unused and duplicate indexes and remove them before rebuilding them. Then identify only the databases whereby a significant amount of space could be reclaimed and rebuild the Indexes only on them.

    Another idea (or perhaps complimentary to it) is (and now some will laugh) buy a USB3 harddisk and move the databases that have very little to do onto it as a temporary measure.

    A question like this doesn't Sound to me like a professional storage Team is on Hand......

    You're probably right about the storage team. With the lack of specifics, I guess my best advice would be to add another drive and move some databases.