Merge pull request #24346 from thesqlsith/patch-11

Update intelligent-query-processing.md

Author: prmerger-automator[bot]

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

@@ -52,9 +52,9 @@ The following table details all intelligent query processing features, along wit
 | [Memory grant feedback (Row Mode)](intelligent-query-processing-feedback.md#row-mode-memory-grant-feedback) | Yes, starting with database compatibility level 150| Yes, starting in [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] with database compatibility level 150|If a row mode query has operations that spill to disk, add more memory for consecutive executions. If a query wastes > 50% of the memory allocated to it, reduce the memory grant size for consecutive executions.|
 | [Memory grant feedback (Percentile)](intelligent-query-processing-feedback.md#percentile-and-persistence-mode-memory-grant-feedback) | Yes, starting with database compatibility level 150| Yes, starting with [!INCLUDE[sql-server-2022](../../includes/sssql22-md.md)]) with database compatibility level 140 | Addresses existing limitations of memory grant feedback in a non-intrusive way. |
 | [Memory Grant, CE, and DOP feedback persistence](intelligent-query-processing-feedback.md#percentile-and-persistence-mode-memory-grant-feedback) | Yes, starting with database compatibility level 160| Yes, starting with [!INCLUDE[sql-server-2022](../../includes/sssql22-md.md)]) with database compatibility level 160 | Addresses existing limitations of memory grant feedback in a non-intrusive way by incorporating past query execution to refine feedback. Requires Query Store to be enabled for the database and in "read write" mode. |
-| [Optimized plan forcing](optimized-plan-forcing-query-store.md) | Yes, starting with database compatibility level 160 | Yes, starting with [!INCLUDE[sql-server-2022](../../includes/sssql22-md.md)]) with database compatibility level 160 | Reduces compilation overhead for repeating forced queries. For more information, see [Optimized plan forcing with Query Store](optimized-plan-forcing-query-store.md). |
+| [Optimized plan forcing](optimized-plan-forcing-query-store.md) | Yes. This feature will be available in public preview soon | Yes, starting with [!INCLUDE[sql-server-2022](../../includes/sssql22-md.md)]) | Reduces compilation overhead for repeating forced queries. For more information, see [Optimized plan forcing with Query Store](optimized-plan-forcing-query-store.md). |
 | [Scalar UDF Inlining](intelligent-query-processing-details.md#scalar-udf-inlining) | Yes, starting with database compatibility level 150 | Yes, starting in [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] with database compatibility level 150|Scalar UDFs are transformed into equivalent relational expressions that are "inlined" into the calling query, often resulting in significant performance gains.|
-| [Parameter Sensitivity Plan Optimization](intelligent-query-processing-details.md#parameter-sensitivity-plan-optimization) | Yes, starting with database compatibility level 150 | Yes, (Starting in [!INCLUDE[sql-server-2022](../../includes/sssql22-md.md)]) with database compatibility level 150 | Parameter Sensitivity Plan Optimization addresses the scenario where a single cached plan for a parameterized query is not optimal for all possible incoming parameter values, for example non-uniform data distributions. |
+| [Parameter Sensitivity Plan Optimization](intelligent-query-processing-details.md#parameter-sensitivity-plan-optimization) | Yes, starting with database compatibility level 160. This feature will be available in public preview soon | Yes, (Starting in [!INCLUDE[sql-server-2022](../../includes/sssql22-md.md)]) with database compatibility level 160 | Parameter Sensitivity Plan Optimization addresses the scenario where a single cached plan for a parameterized query is not optimal for all possible incoming parameter values, for example non-uniform data distributions. |
 | [Table Variable Deferred Compilation](intelligent-query-processing-details.md#table-variable-deferred-compilation) | Yes, starting with database compatibility level 150 | Yes, starting in [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] with database compatibility level 150 | Uses the actual cardinality of the table variable encountered on first compilation instead of a fixed guess.|
 
 ## <a id="sql2019"></a> IQP features for [!INCLUDE[sssql19-md](../../includes/sssql19-md.md)]
@@ -102,4 +102,4 @@ For complete details on all IQP features, including release notes and more in-de
 - [Intelligent query processing demos on GitHub](https://aka.ms/IQPDemos)
 - [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)
 - [Monitor performance by using the Query Store](monitoring-performance-by-using-the-query-store.md)
-- [Best practices with Query Store](best-practice-with-the-query-store.md)
+- [Best practices with Query Store](best-practice-with-the-query-store.md)