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 |
|
lordzoster
Starting Member
29 Posts |
 Posted - 2009-01-07 : 05:48:13
|
| hallo i have a database (full model) whose log file size doesn't go under 130MB, neither after a full backup, a DBCC SHRINK, a BACKUP WITH TRUNCATE ONLY etc.It's minimum size is 130MB, full stopCould i detach the ldf and recreate it (in some manner)? Is there any counter-indication in keeping current situation? |
|
|
tosscrosby
Aged Yak Warrior
676 Posts |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-01-07 : 10:12:21
|
| Probably millions of posts over here as Tosscrossby said . We deal with this issue atleast twice a day. Leave the size as it is because it has to grow again. |
 |
|
|
lordzoster
Starting Member
29 Posts |
Posted - 2009-01-07 : 10:21:49
|
quote:
Originally posted by sodeep
Probably millions of posts over here as Tosscrossby said . We deal with this issue atleast twice a day.
Thanks for your replies, but like i wrote, i already tried every hint and trick and DBCC SHRINKFILE and so on.Just to be clearer, the "zero" size of this log is 130MB, it doesn't lower: let's say it grows of 2MB, up to 132MB: after a full backup the log returns to 130MB.A couple of scissors... |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-01-07 : 10:41:18
|
| You can't shrink lower than initial size.You just need to Backup Log frequently to minimize log growth.Remember Full backup doesn't remove inactive portions of log. |
|
|
|
lordzoster
Starting Member
29 Posts |
Posted - 2009-01-07 : 11:05:24
|
| i think that this is not the "initial size" as setted by the developer, but a scrambled portion of an old log file.Actually, the dev uses to retain default settings while creating databases, and if i recall right this db has been detached and attached more than once. |
|
|
|
|
|
|
|
|
cannot lower log size