User Tools

Site Tools


microsoft:microsoft_sql_server:sql:trace_flags

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
microsoft:microsoft_sql_server:sql:trace_flags [2021/08/05 15:37] petermicrosoft:microsoft_sql_server:sql:trace_flags [2021/08/05 15:38] (current) peter
Line 7: Line 7:
   * Some flags can only be enabled as global, and some can be enabled at either global or session scope.   * Some flags can only be enabled as global, and some can be enabled at either global or session scope.
  
-  * There are three scopes at which trace flags can work: +There are three scopes at which trace flags can work: 
-    * **Query**:  Query trace flags are active for the context of a specific query. + 
-    * **Session**:  Session trace flags are active for a connection and are visible only to that connection. +  * **Query**:  Query trace flags are active for the context of a specific query. 
-      * A trace flag that is enabled at the session level never affects another session, and the effect of the trace flag is lost when the SPID that opened the session logs out. +  * **Session**:  Session trace flags are active for a connection and are visible only to that connection. 
-    * **Global**:  Global trace flags are set at the server level and are visible to every connection on the server. +    * A trace flag that is enabled at the session level never affects another session, and the effect of the trace flag is lost when the SPID that opened the session logs out. 
-      * A global trace flag must be enabled globally, otherwise, the trace flag has no effect. +  * **Global**:  Global trace flags are set at the server level and are visible to every connection on the server. 
-      * It is recommended that you enable global trace flags at startup, by using the **-T** command line option. +    * A global trace flag must be enabled globally, otherwise, the trace flag has no effect. 
-        * This ensures the trace flag remains active after a server restart. +    * It is recommended that you enable global trace flags at startup, by using the **-T** command line option. 
-      * Restart SQL Server for the trace flag to take effect.+      * This ensures the trace flag remains active after a server restart. 
 +    * Restart SQL Server for the trace flag to take effect.
  
 <WRAP info> <WRAP info>
microsoft/microsoft_sql_server/sql/trace_flags.1628177874.txt.gz · Last modified: 2021/08/05 15:37 by peter

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki