November 23, 2013 at 12:48 pm
We have a DB of 450 GB configured with Mirroring
Every week we are deleting around 25 GB of data in it
Currently It has around 200 GB of free space in all files
Should I shrink the database or not?
Disk space is a major criteria for and we have planned to restrict the db size to 150 GB
Please suggest an advice on this.
November 23, 2013 at 1:06 pm
only if you need the drive space or have issues copying the database to other environments with the file that size,
Having empty space in a file does no harm, and at least your backups are getting progressively smaller
---------------------------------------------------------------------
November 23, 2013 at 1:34 pm
Is the database going to grow again? If not, if you never expect it to get back to the 450GB, then do a once-off shrink. Be sure to leave enough free space for index rebuilds. Leave about 1.5x the size of the largest index/table in the database as free space. Rebuild your indexes after the shrink.
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
November 23, 2013 at 1:36 pm
GilaMonster (11/23/2013)
Is the database going to grow again? If not, if you never expect it to get back to the 450GB, then do a once-off shrink. Be sure to leave enough free space for index rebuilds. Leave about 1.5x the size of the largest index/table in the database as free space. Rebuild your indexes after the shrink.
It has only one table.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply