February 8, 2008 at 7:55 pm
I have 200GB DB I want to Shrink I can there is 75GB of space available....IF I shrink this DB how long will it take??
ANy idea this is in 2000?
Nita
February 10, 2008 at 5:31 am
Shrinking databases is generally a bad idea. A database needs some space in it for normal operation.
How long is a question that's very hard to answer. It depends on the drives the DB is on, any concurrent access, anything else on the server and a number of other factors.
If you do decide to shrink the DB, be sure to rebuild all your indexes afterwards. Shrinking a DB shuffles index pages badly. See - "Shrinking databases[/url]"
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
February 10, 2008 at 9:00 am
How much is your data growing by? 75GB isn't that much and it's good to keep free space in there. It's used during index rebuilds, data growth, etc.
As Gail mentioned, I wouldn't shrink unless you had to and even then, I'd make sure you have a few months of free space in there.
February 11, 2008 at 4:48 am
In addtiontion to Gail & Steve;
Shrink database is resource consuming hence use cautiously on the production server.
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
February 11, 2008 at 7:44 pm
...AND...
Until you figure out what made it grow that big to begin with, it's not gonna do you any good to shrink it because the same something is gonna make it grow again. The more times you do this, the more fragmented the disk storage will be for the DB and the slower your DB will become over time... unless you also have a good disk defrag program running on the server.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply