Timeline for Ideal VLF size - SQL Server transaction log
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 27 at 9:11 | comment | added | sepupic | @DMDM Maybe it should sound like this: if you have only 2 giant VLFs, in case of long running transaction, it can fill up some last log records within the first VLF and continue in the second, in this case the log cannot wrap around as the first VLF even if it has only few active records cannot be cleared so it will cause the log to grow, even if the first VLF in your case will have almost 6Gb free. But I don't think you'll ever want to truncate your log to leave only 2 VLFs | |
| Feb 27 at 3:14 | comment | added | DMDM | Why would it prevent the log being able to wrap around and avoid auto growth? Didn't understand that part. | |
| Feb 26 at 10:45 | history | edited | sepupic | CC BY-SA 4.0 |
added 231 characters in body
|
| Feb 26 at 10:35 | history | answered | sepupic | CC BY-SA 4.0 |