December 16, 2015 at 11:53 am
Environment Details.
Test environment. (DW)
Log Auto-Growth is set to 64 MB which creates 4 VLFs and each VLF is 16 MB.
Recovery Model is set to Simple.
After shrinking the log file, DB is left with 79 VLFs.
Question regarding my assumptions.
16MB (each VLF) mulitply by 8620 (# of VLFs) = 137 GB ( So I am assuming some batch job ran which created 137 GB worth of log)
So what I am trying to do is, I am trying to change the Log Auto-Growth setting to 8 GB, which should create 16 VLFs (each vlf is 512 MB)
or set it to 16 GB, (each VLF is 1 GB in size). The reason why I would like to do it because allocating space constantly can be expensive operation. Should I be changing the setting or not. Any advice will be highly appreciated.
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
December 17, 2015 at 4:34 am
Do you know that that batch job won't run again?
Do you know how big your TLog is likely to get? If so, size for that (or an appreciable fraction of that), and set the growth factors accordingly.
Thomas Rushton
blog: https://thelonedba.wordpress.com
December 17, 2015 at 6:08 am
New Born DBA (12/16/2015)
I am trying to change the Log Auto-Growth setting to 8 GB,
even with fast disks this will take time to initialise the space.
You'll likely get timeout issues with your batch job before the file grows. As Thomas has said, set the files initial size to what will be required and catch any further space increases with a sensible autogrowth setting
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply