Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
helpgeek63
Starting Member
4 Posts |
 Posted - 2008-12-09 : 11:28:11
|
| Good morning allI have a server running sql 2005. I noticed that the backups have been failing. It seems that my DB is 65 gig, my "stored back" files are 2.3 gig and I only have 23 gig of free space left on the sever.Since I don't know much about SQL (I'm considered a backup jockey here), I started to read about shrinking DBs. Here is what I have done so far:In SQL Management Studio, rt click on the DB to check my last backup (11/26/08). The initial size of the DB is 62824, autogrowth is 1 mb unrestricted (shouldn't it be at least 10 mb?) Log file is 2111.If I rt click on the DB, tasks, shrink, DB, I see that the space is 64934.31 with free space 397.25 megs (0%). Shrink log files shows space alloted is 2110.31 and free space is 2064.91I tried to give as much backround info to ask this: If I run a DBCC SHRINKDATABASE, would it help me? From what I've read, this command basically goes through and releases "white space" from the database (much like in Exchange). I'm also concerned that I may fragement the DB if I do this.I appreciate any and all advice RegardsRussYou don't get paid for the hour. You get paid for the value you bring to the hour. - Jim Rohn |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2008-12-09 : 11:40:39
|
| Don't shrink.http://sqlinthewild.co.za/index.php/2007/09/08/shrinking-databases/From what you posted, you've got almost no free space in that DB anyway. A 65 GB database with 300 MB free is not worth shrinking, you'll get no space back and you will fragment your indexes.As for autogrow, you should be monitoring and managing the free space yourself. Autogorw should only be for unexpected growths that you didn't notice were needed. But, yes, that should be bigger. Maybe 1 GB (since the DB is 65 GB)--Gail ShawSQL Server MVP |
 |
|
|
helpgeek63
Starting Member
4 Posts |
Posted - 2008-12-09 : 11:55:32
|
| Thank you for your advice. I guess I'm not that far off the mark. Is there anything else I can do to bring the size down?RegardsRYou don't get paid for the hour. You get paid for the value you bring to the hour. - Jim Rohn |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2008-12-09 : 16:53:32
|
| Delete or archive data. If the data in the DB is taking up 65 GB, then it means that it's containing 65 GB of data.I'd suggest that you try and get more storage. Databases tend to grow. It's in their nature.--Gail ShawSQL Server MVP |
|
|
|
|
|
|
|
|
Complete Newbie question about shrinking a DB