Shrink DB

Question

Shrink DB

Mike Levan

SSChampion

Points: 14201
More actions
August 13, 2007 at 7:28 am

#174782

After Shrinking my DB I was expecting to cut down the size but it increased to 100mb, why is it so?
I tried using
DBCC
SHRINKDATABASE (SIRS_Dev)
DBCC SHRINKDATABASE (SIRS_Dev,10)

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Sql Junkie-204042 Hall of Fame Points: 3874 More actions · Answer 1

It's likely that the original size was set to 100mb when the DB was created. That the max it can reduce to it even if all data is deleted.

Mike Levan SSChampion Points: 14201 More actions · Answer 2

or is it something like there is no free space available to shrink any more.

Steve Jones - SSC Editor SSC Guru Points: 736270 More actions · Answer 3

Were you shrinking the entire db? (log and data)

Shrinking is not recommended for data files. It disturbs your indexes, creates fragmentation, etc. You shouldn't do this to data files at all.

Log files might grow because of some error or mis-run process, load, etc., so there are reasons where you need to shrink them, but they work differently. It's possible you need to create some transactions to get these to shrink since they only shrink from the back and there are "virtual log files" inside the main file.

http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=26

JeremyE SSCoach Points: 16201 More actions · Answer 4

My bet is the db was shrunk to leave no free space, set to auto grow at some interval around 100MB, and someone inserted some data causing the database to grow after the shrink.