This question already has an answer here:
- When is it OK to shrink a Database? 5 answers
I have a database, that due to some silly code issues has grown hugely. It is now sitting at 24GB, most of it is very unnecessary logging information (system generated debug information).
My server lives on a cloud hosted server. I am now sitting with 2 issues because of the file size:
I pay for storage. I am happy to pay for my core business, but paying for silly data seems....silly
My backups are now huge also. I do nightly full backups, and then ship them off to an FTP server. This process is taking longer and longer.
Given my issues, is shrinking so bad? I will rebuild all my indexes. I did a dry run, and brought my database down to 6GB.
This guy (who I have always trusted as my SQL guru), says it's bad....mkay "SQL SERVER – Shrinking Database is Bad – Increases Fragmentation – Reduces Performance"