Transaction log file size will not grow exactly 4GB when filegrowth=4GB.
When I set filegrowth to 4GB , 4096MB or 8GB for transaction log file of any database, after the log fills up, the autogrowth will kick in and then I monitor file growth of the log file. It will not grow exactly 4GB or 8GB. It grows in much smaller chunks. Something like, 248KB.
If I set log filegrowth to 3GB, 5GB, 4095MB, 4097MB or anything that's not exactly 4GB, it will grow exactly the set size for filegrowth.
This also happens on SQL2005 Developer Edition and Standard Edition on x86.
Upvotes: 5<=-=Aug 12 2008 1:22PM=-=>
Thank you for your report. This does seem like an interesting anomaly. We will see if we can reproduce this in the current product and addess it in ongoing development.<=-=Aug 4 2009 9:44AM=-=>
I’m seeing behavior similar to this now with VLF and log files on the latest CUs of SQL 2005 and 2008.
I was attempting to create a 40GB log file in 5 steps of 8GB each and I don’t arrive at 16 × 5 VLFs of the same size. I’m going to do some more testing before I log a bug.