June 3, 2009 at 12:11 pm
I have a database in full recovery mode, full backup runs once daily at 18:30, with diff backups every 4 hours during the day and transaction log every 15 mins.
The transaction log usually takes 1-2 seconds to complete.
My database size is very small, circa 350MB.
The Transaction Log size is 140MB. With 93% unused.
I shrank the transaction log prior to a full backup and the file was reduced to 20MB, and still had plenty of free space.
Once the full backup completed I checked the DB and the transaction log file size had increased to 140MB - again with 93% unused.
I am a novice on SQL Server, but I cannot understand why the log file is increasing in size when the additional space is not being used?
Any guidance would really be appreciated.
Thanks in advance.
June 3, 2009 at 1:21 pm
Because the transaction log needs 140MB at some point in time to handle the transactions that occur between your transaction log backups.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply