-> The list of trace flags enabled by default in an Azure Managed Instance doesn’t contain trace flag 1117.

-> The official documentation states that “A Managed Instance runs with all of the features of the most recent version of SQL Server, including online operations, automatic plan corrections, and other enterprise performance enhancements.”. This advises us that features related to trace flag 1117 should be enabled by default even though the trace flag is not explicitly enabled.

-> Lets check if this is actually true!

-> Managed instance that I am testing has below Tempdb files,

-> I am inserting some data into a temporary table and check if all the tempdb files grow,

-> It is pretty clear that all the tempdb files have grown. Lets check the SQL Server error log to see if there are any messages related to Tempdb autogrow,

-> The messages recorded above shows us that autogrow has happened.

-> This proves that the features related to trace flag 1117 are enabled in the managed instance and it is not required for us to enable it explicitly.

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.

-> There are many trace flags enabled by default in Azure Managed Instance.

-> At this point, I am not sure if these trace flags will be enabled after the preview. But I can see trace flags that are used to write finer details to errorlog. So I think these may be removed later.

-> Lets see what these trace flags do. Some details can be incorrect, I will change it going forward as required.

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.