Update dbcc-traceon-trace-flags-transact-sql.md

ktaranov · web-flow · commit 72b3e2eaaf95 · 2018-01-09T22:13:18.000+03:00
Update trace flags 11023 and 11024 Scope value
diff --git a/docs/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md b/docs/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md
@@ -143,8 +143,8 @@ The following table lists and describes the trace flags that are available in [!
 |**9939**|Enables parallel plans and parallel scan of memory-optimized tables and table variables in DML operations that reference memory-optimized tables or table variables, as long as they are not the target of the DML operation in [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)]. For more information, see this [Microsoft Support article](http://support.microsoft.com/kb/4013877).<br /><br />**Note:** Trace flag 9939 is not needed if trace flag 4199 is also explicitly enabled.<br /><br />**Scope**: global or session or query|   
 |**10204**|Disables merge/recompress during columnstore index reorganization. In [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)], when a columnstore index is reorganized, there is new functionality to automatically merge any small compressed rowgroups into larger compressed rowgroups, as well as recompressing any rowgroups that have a large number of deleted rows.<br /><br />**Note:** Trace flag 10204 does not apply to columnstore indexes which are created on memory-optimized tables.<br /><br />**Scope**: global or session|   
 |**10316**|Enables creation of additional indexes on [internal memory-optimized staging temporal table](../../relational-databases/tables/system-versioned-temporal-tables-with-memory-optimized-tables.md), beside the default one. If you have specific query pattern that includes columns which are not covered by the default index you may consider adding additional ones.<br /><br />**Note:** System-versioned temporal tables for Memory-Optimized Tables are designed to provide high transactional throughput. Please be aware that creating additional indexes may introduce overhead for DML operations that update or delete rows in the current table. With the additional indexes you should aim to find the right  balance between performance of temporal queries and additional DML overhead.<br /><br />**Scope**: global or session|
-|**11023**|Disables the use of the last persisted sample rate, for all subsequent statistics update where a sample rate is not specified explicitly as part of the [UPDATE STATISTICS](../../t-sql/statements/update-statistics-transact-sql.md) statement. For more information, see this [Microsoft Support article](http://support.microsoft.com/kb/4039284).<br /><br />**Scope**: global|    
-|**11024**|Enables triggering the auto update of statistics when the modification count of any partition exceeds the local [threshold](../../relational-databases/statistics/statistics.md#AutoUpdateStats). For more information, see this [Microsoft Support article](http://support.microsoft.com/kb/4041811).<br /><br />**Scope**: global| 
+|**11023**|Disables the use of the last persisted sample rate, for all subsequent statistics update where a sample rate is not specified explicitly as part of the [UPDATE STATISTICS](../../t-sql/statements/update-statistics-transact-sql.md) statement. For more information, see this [Microsoft Support article](http://support.microsoft.com/kb/4039284).<br /><br />**Scope**: global or session|    
+|**11024**|Enables triggering the auto update of statistics when the modification count of any partition exceeds the local [threshold](../../relational-databases/statistics/statistics.md#AutoUpdateStats). For more information, see this [Microsoft Support article](http://support.microsoft.com/kb/4041811).<br /><br />**Scope**: global or session| 
   
 ## Remarks  
  In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], there are three types of trace flags: query, session and global. Query trace flags are active for the context of a specific query. Session trace flags are active for a connection and are visible only to that connection. Global trace flags are set at the server level and are visible to every connection on the server. Some flags can only be enabled as global, and some can be enabled at either global or session scope.  
