Trace Flag error while doing assessment using DMA tool from on-premise SQL server to Azure SQL Managed Instance

Question

Trace Flag, hearing the name first time.
Got Trace flag error while doing assessment using DMA tool for the on-premise SQL server to Azure SQL Managed Instance as target server. Some of the Trace flags are now supported in the Azure SQL Managed Instance but these two Trace flag names are still not supported. Done googling and reading all the documents but no luck to resolve this error.
Need help to remove this Trace flag error from assessment for smooth migration of schema and data to my target server.
Trying to migrate the server from on-premise to Azure SQL Managed Instance.
Attaching the screenshot of the error.

Answer 1

Hi @Nilesh Patel ,

Azure SQL Managed Instance supports the following global Trace Flags: 460, 2301, 2389, 2390, 2453, 2467, 7471, 8207, 9389, 10316, and 11024. Session trace-flags are not yet supported in Managed Instance. Refer to this MS document.

Suggest you turning off the two trace flags before doing a migration. Using below T-SQL to turn off the two flags.

DBCC TRACEOFF (3226, -1);     
GO    
  
DBCC TRACEOFF (8002);     
GO    

By default, every successful backup operation adds an entry in the SQL Server error log and in the system event log. If you create very frequent log backups, these success messages accumulate quickly, resulting in huge error logs in which finding other messages is problematic. With 3226 trace flag, you can suppress these log entries. This is useful if you are running frequent log backups and if none of your scripts depend on those entries.

Trace Flag: 8002 Function: Changes CPU Affinity behavior

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".