-> 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.
| Trace Flag | Description |
| 1800 | 1) Details related to SQL Server startup. 2) This article mentions this trace flag which is related to “Slow synchronization when disks have different sector sizes for primary and secondary replica log files in SQL Server AG and Logshipping environments” |
| 2551 | |
| 2591 | |
| 3004 | Lists the database Backup / restore details step by step. |
| 3447 | |
| 3605 | Redirects output to SQL Server errorlog |
| 3701 | Script level upgrade scripts will be written to SQL Server errorlog during failures. This gets added automatically to On-Premise SQL Server during patching. |
| 3978 | |
| 4141 | |
| 5521 | |
| 7838 | |
| 8015 | Ignores physical NUMA detection. This article has more details. |
| 8017 | Avoid creating a lot of offline schedulers. |
| 8037 | |
| 8054 | |
| 8057 | |
| 8063 | |
| 8065 | |
| 8086 | |
| 9041 | |
| 9537 | |
| 9570 | |
| 9837 | Details related to checkpoint |
| 9850 | Details related to checkpoint |
| 9883 | |
| 9905 | |
| 9934 | |
| 9940 | |
| 9941 |
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.