tigertoolbox
tigertoolbox copied to clipboard
Need better support for very large log files
This limitation to 1024MB of increment size wouldn't be optimal in highly active databases with very large transaction log files. It could cause an adverse effect and actually INCREASE the number of VLFs.
https://github.com/microsoft/tigertoolbox/blob/14947834e4a5351dc2fb8ac5c9900fdb78cea9da/Fixing-VLFs/Fix_VLFs.sql#L226-L228
Wouldn't it be better to perform one single growth back to original size, as suggested by David Levy here? http://adventuresinsql.com/2009/12/a-busyaccidental-dbas-guide-to-managing-vlfs/