July 8, 2009 at 12:23 am
Hi, a month ago, we executed the following commands:
shrinkfile, shrinkdatabase, dbcc reindex
Our log file shrunk to 1MB, then now it's already 20MB.
How did it happen and what shall I do to manage its size and bring it back to 1MB?
Thanks for any help.
-Isabel
July 8, 2009 at 12:30 am
Sounds like your database is using either the BULK-LOGGED or FULL recovery models and you are only running full backups and possibly differential backups between full backups. Neither of these backups will truncate (not the same as shrinking) the transaction log. The only way to do that is to either place your database in the SIMPLE recovery model, which will not allow you to do a point in time recovery of the your database, or schedule periodic transaction log backups.
July 8, 2009 at 12:53 am
that makes me crazier about my problem. because our database is in simple recovery model. we do full backups every sunday, and differential backups from mondays to saturdays.
pls help me on what to do with this.
July 8, 2009 at 1:05 am
Sounds like you have some large transactions that need 20 MB of log space. Index rebuilds are a prime candidate, or a large data load.
20MB is tiny for a log. Why are you worries about such a small file?
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
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply