November 12, 2008 at 6:34 am
I get frequent issues with low disk space and every time we shrink db's for that. we have limited disk and so we have to manage.
if need to archive a db i do shrink first then back it up which is consuming time, how can i shrink while doing a backup.
FYI.. we use LiteSPeed for backups.
November 12, 2008 at 11:10 am
Hi Mike
The simple answer is add some space, again why is that your database is growing, find the root casuse, if this is due to data growth then go for some more space. Shrinking is not a good idea 😀
November 12, 2008 at 11:12 am
There are some discussions going on in the same forum about shrinking db, i found the below link from one of the post on the same forum , please have a look
November 12, 2008 at 11:25 am
Maybe you can Purge the historical data and also Update statistics with full scan.Shrinking a DB that needs to grow is a temporal solution. As said in the above post, if there is constant growth please add more disk space..
Thanks!!
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
November 13, 2008 at 7:31 am
Mike Levan (11/12/2008)
I get frequent issues with low disk space and every time we shrink db's for that. we have limited disk and so we have to manage.if need to archive a db i do shrink first then back it up which is consuming time, how can i shrink while doing a backup.
FYI.. we use LiteSPeed for backups.
Shrinking a DB is a false savings. the cost of storage is so low, the price of an out of space event is so large, the side effects bad enough, you should avoid at all costs.
The only time I could see truly recommending a shrink is if you are using a size limited (like SQL Express) and you're hitting the limit.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply