Essential Trace Flags to enable at SQL Server Services startup
List of trace flags to enable on SQL server service startup:
Reason:
Server Name | Trace Flag | Status | Global | Session |
---|---|---|---|---|
PRD-MSSQL01C | 1222 | 1 | 1 | 0 |
PRD-MSSQL01C | 1224 | 1 | 1 | 0 |
PRD-MSSQL01C | 4136 | 1 | 1 | 0 |
Reason:
- 4136 will help in preventing parameter sniffing on sql server and in turn will result in query optimizer to create optimized plans for same queries having different parameters which will result in better performance. Note: Please ensure that you thoroughly test this option, before rolling it into a production environment.
Scope: Global or session - 1224 disables lock escalation based on the number of locks. However, memory pressure can still activate lock escalation. This helps avoid "out-of-locks" errors when many locks are being used.
Scope: Global or session - 1222 helps in detecting deadlocks returns the resources and types of locks that are participating in a deadlock and also the current command affected, in an XML format that does not comply with any XSD schema.
Note: Avoid using trace flag 1222 on workload-intensive systems causing deadlocks.
Scope: Global only
Comments
Post a Comment
Note:Please be gentle while commenting and avoid spamming as comment are anyways moderated thank you.