Comments on: Transaction log growth best practices

By: yupsay

yupsay — Thu, 12 Jul 2012 09:33:21 +0000

This is slightly away from the topic but TLOG size only. As per the documentation the TLOG files are capped at 2 TB (typically you wount be using one this big) you may refer to the MS document at http://msdn.microsoft.com/en-us/library/ms143432. All the papers say that the LDF growth is limited to 2 TB, but here in this test case I've a log file at 2.7 TB. Believe the 2 TB limit is for MBR partitions & no holds bar for GPT. Pressuming for documentation this was tested on MBR but with GPT I'm sitting on a LDF 2.72 TB in size. If you all can please share your comments here at https://connect.microsoft.com/SQLServer/feedback/details/753184/sql-server-transactional-log-file-ldf-having-a-2-tb-limit

By: Mrdenny

Mrdenny — Fri, 08 Jul 2011 17:21:03 +0000

As I understand the bug as it was explained to me, create a database, then increase the log by 4 or 8 Gigs manually. It then should only increase in size by 32k. It may not do it every time as specific conditions must be met for the bug to show itself, and I don’t have a list of those conditions.

By: SolaS

SolaS — Fri, 08 Jul 2011 13:46:54 +0000

…. also tried on SQL 2k5 and again I got 20 VLF with 8 gb autogrowth…

By: SolaS

SolaS — Fri, 08 Jul 2011 11:48:13 +0000

Hi Denny,

I didn’t managed to reproduce this bug on SQL Server 2008 R2 developer edition.
I created new database, new table, set log autogrowh on 9000 MB and run insert operation.
When autogrowth operation finished I had 20 VLF in the log file.
Did I miss something here?

Thank you in advance.

Best regards,
Slaven