Merge pull request #9343 from CarlRabeler/20190307-joe

[sql} remove AQP from TOC

Author: TrishaMc

docs/database-engine/whats-new-in-sql-server-2017.md

@@ -27,7 +27,7 @@ This topic describes improvements made to the [!INCLUDE[ssdenoversion-md](../inc
 - Resumable online index rebuild. Resumable online index rebuild allows you to resume an online index rebuild operation from where it stopped after a failure (such as a failover to a replica or insufficient disk space). You can also pause and later resume an online index rebuild operation. For example, you might need to temporarily free up systems resources in order to execute a high priority task or complete the index rebuild in another maintenance window if the available maintenance windows is too short for a large table. Finally, resumable online index rebuild does not require significant log space, which allows you to perform log truncation while the resumable rebuild operation is running. See [ALTER INDEX](../t-sql/statements/alter-index-transact-sql.md) and [Guidelines for online index operations](../relational-databases/indexes/guidelines-for-online-index-operations.md).
 - **IDENTITY_CACHE option for ALTER DATABASE SCOPED CONFIGURATION**. A new option IDENTITY_CACHE was added to `ALTER DATABASE SCOPED CONFIGURATION` T-SQL statement. When this option is set to `OFF`, it allows the Database Engine to avoid gaps in the values of identity columns in case a server restarts unexpectedly or fails over to a secondary server. See [ALTER DATABASE SCOPED CONFIGURATION](../t-sql/statements/alter-database-scoped-configuration-transact-sql.md).   
 -  [!INCLUDE[ssnoversion](../includes/ssnoversion-md.md)] now offers graph database capabilities to model more meaninginful relationship-oriented data. This includes new [CREATE TABLE](../t-sql/statements/create-table-sql-graph.md) syntax for creating node and edge tables, and the keyword [MATCH](../t-sql/queries/match-sql-graph.md) for queries. For more information, see [Graph Processing with SQL Server 2017](../relational-databases/graphs/sql-graph-overview.md).   
-- A new generation of query processing improvements that will adapt optimization strategies to your application workload's runtime conditions. For this first version of the **adaptive query processing** feature family, we have three new improvements: **batch mode adaptive joins**, **batch mode memory grant feedback**, and **interleaved execution** for multi-statement table valued functions.  See [Adaptive query processing in SQL databases](../relational-databases/performance/adaptive-query-processing.md).
+- A new generation of query processing improvements that will adapt optimization strategies to your application workload's runtime conditions. For this first version of the **adaptive query processing** feature family, we have three new improvements: **batch mode adaptive joins**, **batch mode memory grant feedback**, and **interleaved execution** for multi-statement table valued functions.  See [Intelligent query processing in SQL databases](../relational-databases/performance/intelligent-query-processing.md).
 - Automatic tuning is a database feature that provides insight into potential query performance problems, recommend solutions, and automatically fix identified problems. Automatic tuning in [!INCLUDE[ssnoversion](../includes/ssnoversion-md.md)], notifies you whenever a potential performance issue is detected, and lets you apply corrective actions, or lets the [!INCLUDE[ssde-md](../includes/ssde-md.md)] automatically fix performance problems. For more information, see [Automatic tuning](../relational-databases/automatic-tuning/automatic-tuning.md).
 - PERFORMANCE ENHANCEMENT FOR NON CLUSTERED INDEX BUILD ON MEMORY-OPTIMIZED TABLES. Performance of bwtree (non-clustered) index rebuild for MEMORY_OPTIMIZED tables during database recovery has been significantly optimized. This improvement substantially reduces the database recovery time when non-clustered indexes are used.  
 - [sys.dm_os_sys_info](../relational-databases/system-dynamic-management-views/sys-dm-os-sys-info-transact-sql.md) has three new columns: socket_count, cores_per_socket, numa_node_count. This is useful when you run your server in a VM, as exceding NUMA can lead overcommited hosts that in the end transforms to performance issues.

docs/relational-databases/performance/adaptive-query-processing.md

@@ -62,7 +62,7 @@ manager: craigg
 |![security-center-both](../../relational-databases/performance/media/security-center-both.png "security-center-both") **Query optimizer optimization**|[ALTER DATABASE SCOPED CONFIGURATION &#40;Transact-SQL&#41;](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md)<br />[USE HINT query hint](../../t-sql/queries/hints-transact-sql-query.md#use_hint)|  
 |![security-center-both](../../relational-databases/performance/media/security-center-both.png "security-center-both") **[Statistics](../../relational-databases/statistics/statistics.md)**|[When to Update Statistics](../statistics/statistics.md)<br />[Update Statistics](../../relational-databases/statistics/update-statistics.md)|  
 |![security-center-both](../../relational-databases/performance/media/security-center-both.png "security-center-both")  **[In-Memory OLTP &#40;In-Memory Optimization&#41;](../../relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization.md)**|[Memory-Optimized Tables](../../relational-databases/in-memory-oltp/memory-optimized-tables.md)<br />[Natively Compiled Stored Procedures](../../relational-databases/in-memory-oltp/natively-compiled-stored-procedures.md)<br />[Creating and Accessing Tables in TempDB from Natively Compiled Stored Procedures](../../relational-databases/in-memory-oltp/create-and-access-tables-in-tempdb-from-stored-procedures.md)<br />[Troubleshooting Common Performance Problems with Memory-Optimized Hash Indexes](https://msdn.microsoft.com/library/1954a997-7585-4713-81fd-76d429b8d095)<br />[Demonstration: Performance Improvement of In-Memory OLTP](../../relational-databases/in-memory-oltp/demonstration-performance-improvement-of-in-memory-oltp.md)|
-|![security-center-both](../../relational-databases/performance/media/security-center-both.png "security-center-both")  **[Intelligent query processing](../../relational-databases/performance/intelligent-query-processing.md)**|[Adaptive query processing](../../relational-databases/performance/adaptive-query-processing.md)|
+|![security-center-both](../../relational-databases/performance/media/security-center-both.png "security-center-both")  **[Intelligent query processing](../../relational-databases/performance/intelligent-query-processing.md)**|[Intelligent query processing](../../relational-databases/performance/intelligent-query-processing.md)|
 
 ## See Also  
  [Monitor and Tune for Performance](../../relational-databases/performance/monitor-and-tune-for-performance.md)   

docs/relational-databases/performance/performance-center-for-sql-server-database-engine-and-azure-sql-database.md

@@ -1192,7 +1192,7 @@ GO
  [Extended Events](../relational-databases/extended-events/extended-events.md)  
  [Best Practice with the Query Store](../relational-databases/performance/best-practice-with-the-query-store.md)  
  [Cardinality Estimation](../relational-databases/performance/cardinality-estimation-sql-server.md)  
- [Adaptive query processing](../relational-databases/performance/adaptive-query-processing.md)   
+ [Intelligent query processing](../relational-databases/performance/intelligent-query-processing.md)   
  [Operator Precedence](../t-sql/language-elements/operator-precedence-transact-sql.md)    
  [Execution Plans](../relational-databases/performance/execution-plans.md)    
  [Performance Center for SQL Server Database Engine and Azure SQL Database](../relational-databases/performance/performance-center-for-sql-server-database-engine-and-azure-sql-database.md)

docs/relational-databases/query-processing-architecture-guide.md

@@ -194,7 +194,7 @@ Joining to an MSTVF in a `FROM` clause is possible, but can result in poor perfo
 > [!IMPORTANT]
 > MSTVFs have a fixed cardinality guess of 100 starting with [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)], and 1 for earlier [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] versions.    
 > Starting with [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)], optimizing an execution plan that uses MSTVFs can leverage interleaved execution, which results in using actual cardinality instead of the above heuristics.     
-> For more information, see [Interleaved execution for multi-statement table valued functions](../../relational-databases/performance/adaptive-query-processing.md#interleaved-execution-for-multi-statement-table-valued-functions).
+> For more information, see [Interleaved execution for multi-statement table valued functions](../../relational-databases/performance/intelligent-query-processing.md#interleaved-execution-for-mstvfs).
 
 > [!NOTE]  
 > ANSI_WARNINGS is not honored when you pass parameters in a stored procedure, user-defined function, or when you declare and set variables in a batch statement. For example, if a variable is defined as **char(3)**, and then set to a value larger than three characters, the data is truncated to the defined size and the `INSERT` or `UPDATE` statement succeeds.

docs/relational-databases/user-defined-functions/create-user-defined-functions-database-engine.md

@@ -27,7 +27,7 @@ SQL Server 2017 includes many new Database Engine features, enhancements, and pe
 - **CLR assemblies** can now be added to a whitelist, as a workaround for the `clr strict security` feature described in CTP 2.0. [sp_add_trusted_assembly](../relational-databases/system-stored-procedures/sys-sp-add-trusted-assembly-transact-sql.md), [sp_drop_trusted_assembly](../relational-databases/system-stored-procedures/sys-sp-drop-trusted-assembly-transact-sql.md), and [sys.trusted_asssemblies](../relational-databases/system-catalog-views/sys-trusted-assemblies-transact-sql.md) are added to support the white list of trusted assemblies (RC1).  
 - **Resumable online index rebuild** resumes an online index rebuild operation from where it stopped after a failure (such as a failover to a replica or insufficient disk space), or pauses and later resumes an online index rebuild operation. See [ALTER INDEX](../t-sql/statements/alter-index-transact-sql.md) and [Guidelines for online index operations](../relational-databases/indexes/guidelines-for-online-index-operations.md). (CTP 2.0)
 - The **IDENTITY_CACHE** option for ALTER DATABASE SCOPED CONFIGURATION allows you to avoid gaps in the values of identity columns if a server restarts unexpectedly or fails over to a secondary server. See [ALTER DATABASE SCOPED CONFIGURATION](../t-sql/statements/alter-database-scoped-configuration-transact-sql.md). (CTP 2.0)
-- A new generation of query processing improvements that will adapt optimization strategies to your application workload's runtime conditions. For this first version of the **adaptive query processing** feature family, we have three new improvements: **batch mode adaptive joins**, **batch mode memory grant feedback**, and **interleaved execution** for multi-statement table valued functions.  See [Adaptive query processing in SQL databases](../relational-databases/performance/adaptive-query-processing.md).
+- A new generation of query processing improvements that will adapt optimization strategies to your application workload's runtime conditions. For this first version of the **adaptive query processing** feature family, we have three new improvements: **batch mode adaptive joins**, **batch mode memory grant feedback**, and **interleaved execution** for multi-statement table valued functions.  See [Intelligent query processing in SQL databases](../relational-databases/performance/intelligent-query-processing.md).
 - **Automatic database tuning** provides insight into potential query performance problems, recommends solutions, and can automatically fix identified problems. See [Automatic tuning](../relational-databases/automatic-tuning/automatic-tuning.md). (CTP 2.0)
 - New **graph database capabilities** for modeling many-to-many relationships include new [CREATE TABLE](../t-sql/statements/create-table-sql-graph.md) syntax for creating node and edge tables, and the keyword [MATCH](../t-sql/queries/match-sql-graph.md) for queries. See [Graph Processing with SQL Server 2017](../relational-databases/graphs/sql-graph-overview.md). (CTP 2.0)
 - An sp_configure option called `clr strict security` is enabled by default to enhance the security of CLR assemblies. See [CLR strict security](../database-engine/configure-windows/clr-strict-security.md). (CTP 2.0)

docs/sql-server/what-s-new-in-sql-server-2017.md

@@ -130,7 +130,7 @@ The following table lists and describes the trace flags that are available in [!
 |**9347**|Disables batch mode for sort operator. [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] introduced a new batch mode sort operator that boosts performance for many analytical queries. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/3172787).<br /><br />**Scope**: global or session or query|
 |**9349**|Disables batch mode for top N sort operator. [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] introduced a new batch mode top sort operator that boosts performance for many analytical queries.<br /><br />**Scope**: global or session or query|
 |**9389**|Enables additional dynamic memory grant for batch mode operators. If a query does not get all the memory it needs, it spills data to tempdb, incurring additional I/O and potentially impacting query performance. If the dynamic memory grant trace flag is enabled, a batch mode operator may ask for additional memory and avoid spilling to tempdb if additional memory is available. For more information, see the *Effects of min memory per query* section of the [Memory Management Architecture Guide](../../relational-databases/memory-management-architecture-guide.md#effects-of-min-memory-per-query).<br /><br />**Scope**: global or session| 
-|**9398**|Disables [Adaptive Join](../../relational-databases/performance/adaptive-query-processing.md#batch-mode-adaptive-joins) operator that enables the choice of a [Hash join or Nested Loops join](../../relational-databases/performance/joins.md) method to be deferred until the after the first input has been scanned, as introduced in [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)]. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/4099126).<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope**: global and session and query|
+|**9398**|Disables [Adaptive Join](../../relational-databases/performance/intelligent-query-processing.md#batch-mode-adaptive-joins) operator that enables the choice of a [Hash join or Nested Loops join](../../relational-databases/performance/joins.md) method to be deferred until the after the first input has been scanned, as introduced in [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)]. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/4099126).<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope**: global and session and query|
 |**9453**|Disables batch mode execution. For more information, see this [Microsoft Support article](https://support.microsoft.com/help/4016902).<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope:** global and session and query|
 |**9471**|Causes [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to generate a plan using minimum selectivity for single-table filters, under the query optimizer cardinality estimation model of [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] through [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] versions.<br /><br />Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] SP1, to accomplish this at the query level, add the USE HINT 'ASSUME_MIN_SELECTIVITY_FOR_FILTER_ESTIMATES' [query hint](../../t-sql/queries/hints-transact-sql-query.md) instead of using this trace flag.<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Note:** This trace flag does not apply to CE version 70. Use trace flag 4137 instead.<br /><br />**Scope**: global or session or query| 
 |**9476**|Causes [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to generate a plan using the Simple Containment assumption instead of the default Base Containment assumption, under the query optimizer cardinality estimation model of [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] through [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] versions. For more information, see this  [Microsoft Support article](https://support.microsoft.com/kb/3189675).<br /><br />Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] SP1, to accomplish this at the query level, add the USE HINT 'ASSUME_JOIN_PREDICATE_DEPENDS_ON_FILTERS' [query hint](../../t-sql/queries/hints-transact-sql-query.md) instead of using this trace flag.<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope**: global or session or query|