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 |
|
beza
Starting Member
16 Posts |
 Posted - 2009-07-01 : 06:06:33
|
| Heymy DB had reached 4 GB and the log File almost 5I read somewhere about the shrink DB command .. ran it and it was working great.afterward I continued reading a little bit more and it appears to be something bad to do ... most of the threads I read in were saying no to this command ...can someone please explain this to me ... and is there any chance I could have screwed my DB because of it ?first I ran the command with truncate only, afterward with just the DB name but it was taking too long so I stopped it after 10 minutesThanks a lot! |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-07-01 : 09:10:34
|
| You didn't mess up your DB, but shrinking is not recommended. Why do you want to shrink? Why do you think that shrinking's going to do anything?From the size of the log in comparison to the data, I'm guessing full recovery and no log backups. Is that the case?If so, [lease read through this - [url]http://www.sqlservercentral.com/articles/64582/[/url]--Gail ShawSQL Server MVP |
 |
|
|
|
|
|
Shrink DB