Open MPowellFDB opened 1 year ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub. Please see https://aka.ms/biceptypesinfo for troubleshooting help.
Author: | MPowellFDB |
---|---|
Assignees: | - |
Labels: | `Needs: Triage :mag:`, `Service Attention`, `SQL - VM` |
Milestone: | - |
Bicep version Bicep CLI version 0.16.2 (de7fdd2b33)
Describe the bug When deploying a SQL Virtual Machine using Microsoft.SqlVirtualMachine/sqlVirtualMachines@2022-07-01-preview, the sqlTempDbSettings > dataFileCount and dataFileSize settings appear to be ignored.
When I create a VM, it always creates tempdb files based on the number of Cores the VM has, with an 8MB file size.
To Reproduce Enter top 5 parameter values and run the following template for a Standard_F2s_v2 VM in Bicep. Check the tempdb file count and size (existing vnet/subnet required):
Deploy command using Azure CLI:
Additional Information
This is important for us, as we would like to provision the machines at a smaller size, then eventually scale the machines up when running performance tests on them. Our Production machines have 8 data files for TempDB and 1024MB file size. We're provisioning a new environment with like-for-like Production infrastructure to allow us to run these tests.