Merge pull request #21283 from PiJoCoder/patch-3

Removing the incorrect anchor for auto-create stats

Author: PRMerger16

docs/relational-databases/statistics/statistics.md

@@ -86,7 +86,7 @@ The density vector contains one density for each prefix of columns in the statis
 ### Statistics Options  
  There are three options that affect when and how statistics are created and updated. These options are configurable at the database level only.  
 
-#### <a name="AutoUpdateStats"></a>AUTO_CREATE_STATISTICS Option  
+#### AUTO_CREATE_STATISTICS Option  
  When the automatic create statistics option, [AUTO_CREATE_STATISTICS](../../t-sql/statements/alter-database-transact-sql-set-options.md#auto_create_statistics) is ON, the Query Optimizer creates statistics on individual columns in the query predicate, as necessary, to improve cardinality estimates for the query plan. These single-column statistics are created on columns that do not already have a [histogram](#histogram) in an existing statistics object. The AUTO_CREATE_STATISTICS option does not determine whether statistics get created for indexes. This option also does not generate filtered statistics. It applies strictly to single-column statistics for the full table.  
 
  When the Query Optimizer creates statistics as a result of using the AUTO_CREATE_STATISTICS option, the statistics name starts with `_WA`. You can use the following query to determine if the Query Optimizer has created statistics for a query predicate column.  

docs/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md

@@ -205,7 +205,7 @@ The following table lists and describes the trace flags that are available in [!
 |<a name="tf10207"></a>**10207**|Allows clustered columnstore index (CCI) scans to skip corrupt segments or metadata, allowing data retrieval from a corrupt CCI. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/3067257).<br /><br />**Scope**: global or session| 
 |<a name="tf10316"></a>**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|
 |<a name="tf11023"></a>**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](https://support.microsoft.com/kb/4039284).<br /><br />**Scope**: global only|    
-|<a name="tf11024"></a>**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](https://support.microsoft.com/kb/4041811).<br /><br />**Note:** This trace flag applies to [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] SP2, [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU3, and higher builds.<br /><br />**Scope**: global only| 
+|<a name="tf11024"></a>**11024**|Enables triggering the auto update of statistics when the modification count of any partition exceeds the local [threshold](../../relational-databases/statistics/statistics.md#auto_update_statistics-option). For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/4041811).<br /><br />**Note:** This trace flag applies to [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] SP2, [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU3, and higher builds.<br /><br />**Scope**: global only| 
 |<a name="tf11047"></a>**11047**|Applies the default timeout set by `query wait (s)` or the Resource Governor `REQUEST_MEMORY_GRANT_TIMEOUT_SEC` configuration to columnstore index build operations. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/4480641).<br /><br />**Note:** This trace flag applies to [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] SP2 CU5, [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU14, and higher builds.<br /><br />**Scope**: global only| 
 |<a name="tf11064"></a>**11064**|Improves the scalability of data loading operations into columnstore indexes, by optimizing memory distribution between the `SELECT` and `INSERT` statements. For more information on loading data into a columnstore index, see [Columnstore indexes - Data loading guidance](../../relational-databases/indexes/columnstore-indexes-data-loading-guidance.md).<br /><br />**Note:** This trace flag applies to [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] and higher builds.<br /><br />**Scope**: global only| 
 |<a name="tf11068"></a>**11068**|Uses the server, database, or resource pool configured max degree of parallelism (MAXDOP) value for columnstore index insert operations. For more information on overriding degrees of parallelism, see the [Query Processing Architecture Guide](../../relational-databases/query-processing-architecture-guide.md#overriding-degrees-of-parallelism).<br /><br />**Important:** This trace flag is only effective if trace flag 11064 is also enabled.<br /><br />**Important:** Use this trace flag when faster data loads are preferred over maintaining [columnstore segment](../../relational-databases/indexes/columnstore-indexes-overview.md#column-segment) quality. For example, using this trace flag when loading 1,048,577 rows into a columnstore may result in more than one compressed rowgroup, if the insert operation is executing in parallel mode. Without this trace flag, the insert operation would result in one compressed rowgroup.<br /><br />**Note:** This trace flag applies to [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] and higher builds.<br /><br />**Scope**: global only|