Merge pull request #32287 from MicrosoftDocs/main

Emma-yxf · web-flow · commit 9433bb76b0c5 · 2024-11-04T10:33:32.000-08:00
11/04/2024 AM Publish
diff --git a/azure-sql/database-watcher-overview.md b/azure-sql/database-watcher-overview.md
@@ -5,7 +5,7 @@ description: An overview of database watcher for Azure SQL, a managed monitoring
 author: dimitri-furman
 ms.author: dfurman
 ms.reviewer: wiassaf
-ms.date: 10/29/2024
+ms.date: 11/04/2024
 ms.service: azure-sql
 ms.subservice: monitoring
 ms.topic: conceptual
@@ -94,7 +94,7 @@ There is a limit on the number of SQL targets per watcher, and the number of wat
 
 | Parameter | Limit |
 |:--|:--|
-| SQL targets per watcher<sup>1</sup> | 50 |
+| SQL targets per watcher<sup>1</sup> | 100 |
 | Watchers per subscription | 20 |
 
 <sup>1</sup>A high availability replica of a database, elastic pool, or SQL managed instance is monitored independently of its parent replica, and is considered a separate target.
@@ -199,6 +199,7 @@ This section describes recent database watcher fixes, changes, and improvements.
 
 | Time period | Changes |
 |:--|:--|
+| November 2024 | - Increase the limit on the number of SQL targets per watcher from 50 to 100. |
 | October 2024 | - Fix a bug where the **Table metadata** dataset was not collected if there are any views with invalid table references, or any tables with multiple column check constraints.</br> - Add support for user assigned identity. For more information, see [Modify watcher identity](database-watcher-manage.md#modify-watcher-identity).</br> - Automatically grant the watcher access to key vault secrets when adding a SQL target that uses SQL authentication.</br> - Automatically grant the watcher access to an Azure Data Explorer database when adding a data store to an existing watcher.</br> - Add the feedback button on the **Overview** page and other pages. |
 | September 2024 | - Fix a bug where the number of user logical sessions in the **Session statistics** dataset was always the same as the number of user sessions, even if [MARS](/sql/relational-databases/native-client/features/using-multiple-active-result-sets-mars) logical sessions were used.</br> - Fix a bug where elastic pool storage utilization wasn't reported correctly for Hyperscale elastic pools.</br> - Resolve an issue where for certain datasets, the first sample collected after a watcher restart might contain data that has already been collected before restart. </br> - Improve collection query performance to avoid timeouts for the **Table metadata** dataset.</br> - Improve collection reliability for the **Query runtime statistics** and **Query wait statistics** datasets on SQL Managed Instance. </br> - Add failover-related columns to the **Database replicas** dataset for SQL Managed Instance.</br> - Add index operational statistics columns to the **Index metadata** datasets.</br> - Add support for selecting multiple Azure SQL databases in the **Add SQL target** blade.|
 | August 2024 | - Enable database watcher in the **Central US**, **East US 2**, **North Europe**, and **Sweden Central** Azure regions.</br> - Add subscription and resource group filters in estate [dashboards](#dashboards). |
diff --git a/docs/relational-databases/system-stored-procedures/sp-executesql-transact-sql.md b/docs/relational-databases/system-stored-procedures/sp-executesql-transact-sql.md
@@ -163,7 +163,7 @@ Being able to substitute parameters in `sp_executesql` offers the following adva
 
 **Applies to:** [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)]
 
-When the [OPTIMIZED_SP_EXECUTESQL database scoped configuration](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md#optimized_sp_executesql) is enabled, the compilation behavior of batches submitted using `sp_executesql` becomes identical to the serialized compilation behavior that objects such as stored procedures and triggers currently employ.
+When the OPTIMIZED_SP_EXECUTESQL [database scoped configuration](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md#optimized_sp_executesql---on--off-) is enabled, the compilation behavior of batches submitted using `sp_executesql` becomes identical to the serialized compilation behavior that objects such as stored procedures and triggers currently employ.
 
 When batches are identical (excluding any parameter differences), the `OPTIMIZED_SP_EXECUTESQL` option tries to obtain a compile lock as an enforcement mechanism to guarantee that the compilation process is serialized. This lock ensures that if multiple sessions invoke `sp_executesql` simultaneously, those sessions will wait while trying to obtain an exclusive compile lock after the first session starts the compilation process. The first execution of `sp_executesql` compiles and inserts its compiled plan into the plan cache. Other sessions abort waiting on the compile lock and reuse the plan once it becomes available.
 
diff --git a/docs/t-sql/statements/alter-database-scoped-configuration-transact-sql.md b/docs/t-sql/statements/alter-database-scoped-configuration-transact-sql.md
@@ -500,7 +500,7 @@ Causes SQL Server to generate a Showplan XML fragment with the ParameterRuntimeV
 > [!IMPORTANT]  
 > The `FORCE_SHOWPLAN_RUNTIME_PARAMETER_COLLECTION` database scoped configuration option isn't meant to be enabled continuously in a production environment, but only for time-limited troubleshooting purposes. Using this database scoped configuration option will introduce additional and possibly significant CPU and memory overhead as we will create a Showplan XML fragment with runtime parameter information, whether the `sys.dm_exec_query_statistics_xml` DMV or lightweight query execution statistics profile infrastructure is enabled or not.
 
-#### OPTIMIZED_SP_EXECUTESQL
+#### OPTIMIZED_SP_EXECUTESQL = { ON | OFF }
 
 **Applies to:** [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)]
 
