If the scope of the trace flag is global only does it mean I can't use it only for one connection while not affecting the performance of others?
SQL Server – Global Only Scoped Trace Flags
sql servertrace-flags
Related Question
- SQL Server – Methods for Finding New Trace Flags
- SQL Server Trace Flags – Should Trace Flag 1118 Be Turned On for Every SQL Instance?
- SQL Server 2016 – Using Trace Flag 10260
- SQL Server Best Practices – Before Applying Trace Flags
- SQL Server – Processor Affinity with Trace Flag 8002 ON
- Sql-server – Difference in behaviour between `DBCC TRACEON` and `QUERYTRACEON`
Best Answer
The scope signifies the affect of trace flag, a global scope means it will be applicable to all connections of SQL Server, it cannot be made to work only for particular connection/session. On the other hand trace flags whose scope are limited to session will be applicable to particular session.
If you refer to Trace Flags documentation it says
If you are using SQL Server 2008 and above you have extended events to get deadlock information. Please see