We have 250GB of images that have been added into the database over the last 10 years. We would like to remove the images from the database and link to files in a filesystem.
Our data size would go from 275GB to 50Gb or so. We will not be adding images further so it will grow more slowly. The images are the only thing in tha Secondary filegroup. Would we not want to reclaim the space in some way?
Thanks
Mark
Thanks for your comment.
Of course, in that case you can run a Shrink operation.
Shrinks are not always bad, but you have to be aware of the side-effects – like index fragmentation.
6 thoughts on “SQL Server Quickie #16 – Database Shrink Operations”
Hi Klaus,
Your Free Videos are very help full.
Mashrur
Hello Mashrur,
Thanks for the nice feedback 🙂
Best regards,
-Klaus
Thank Klaus very much, all video and articles are very useful. I love it so much
Hello Vinth,
Thanks for the great feedback!
Best regards,
-Klaus
We have 250GB of images that have been added into the database over the last 10 years. We would like to remove the images from the database and link to files in a filesystem.
Our data size would go from 275GB to 50Gb or so. We will not be adding images further so it will grow more slowly. The images are the only thing in tha Secondary filegroup. Would we not want to reclaim the space in some way?
Thanks
Mark
Hello Mark,
Thanks for your comment.
Of course, in that case you can run a Shrink operation.
Shrinks are not always bad, but you have to be aware of the side-effects – like index fragmentation.
Thanks,
-Klaus