2GB transaction log

[schlivo]

Hi,

I'm wondering if there is a transaction log max size of 2 GB in place as it was in Azure SQL DB couple of years ago ?

I tried to change database transaction log size to MAXSIZE = UNLIMITED but the SQL Engine always revert it back to 2GB.

Is this doumented somewhere ?

[twright-msft]

Is this on a Linux container or Windows container?

[schlivo]

It's on a Windows container. Here are the version détails:

Docker: Kernel Version: 10.0 14393 (14393.1480.amd64fre.rs1_release.170706-2004) Operating System: Hyper-V Server 2016 OSType: windows Architecture: x86_64 CPUs: 4 Total Memory: 15.89 GiB

SQL Engine Microsoft SQL Server 2017 (CTP2.1) - 14.0.600.250 (X64) May 10 2017 12:21:23 Copyright (C) 2017 Microsoft Corporation. All rights reserved. Enterprise Evaluation Edition (64-bit) on Windows Server 2016 Datacenter 10.0 (Build 14393: ) (Hypervisor)

[twright-msft]

@perrysk-msft - can you please take a look at this?

[perrysk-msft]

Sure - As far as I know there are no transaction log max size limits. We'll look into this and update this thread.

[schlivo]

@perrysk-msft I was able to workaround the limitation with a persistent volume. Although the database properties says it's limited (209GB instead of 2GB sorry my mistake) , the datafile grown above 2GB:

PS C:\Docker\MSSQL\Data> dir Directory: C:\Docker\MSSQL\Data

Mode LastWriteTime Length Name

---

-a---- 22/07/2017 23:56 31465668608 DEMO_DW.mdf -a---- 23/07/2017 00:01 291110912 DEMO_DW_log.ldf -a---- 23/07/2017 00:03 2222981120 tempdb.mdf -a---- 23/07/2017 00:03 2222981120 tempdb_2.ndf -a---- 22/07/2017 22:52 8388608 tempdb_mssql_2.ndf -a---- 22/07/2017 22:55 8388608 templog.ldf

So I guess there is indeed a storage limitation using the default Windows storage container settings, it was even worse with tempdb which was not able to grow above 700Mb.

[thecloudtaylor]

You may need to increase the size of the image being presented into the container: Windows container docs - Image size