Merge pull request #34008 from MicrosoftDocs/main

05/05/2025 AM Publishing

Author: v-alje

azure-sql/database-watcher-alerts.md

@@ -5,7 +5,7 @@ description: A detailed description of Azure Monitor Alerts in database watcher
 author: lcwright
 ms.author: lancewright
 ms.reviewer: dfurman
-ms.date: 02/12/2025
+ms.date: 05/04/2025
 ms.service: azure-sql
 ms.subservice: monitoring
 ms.topic: conceptual
@@ -20,7 +20,7 @@ monikerRange: "=azuresql||=azuresql-db||=azuresql-mi"
 
 After you [create and configure](database-watcher-manage.md) a watcher, you can set up [Azure Monitor Alerts](/azure/azure-monitor/alerts/alerts-overview) to receive notifications about high resource usage, notable workload patterns, and other conditions across your Azure SQL estate that might require attention. To do this, you create a [log search alert rule](/azure/azure-monitor/alerts/alerts-create-log-alert-rule) that queries the data store of a watcher on a schedule.
 
-To help you create alert rules, database watcher includes templates for common alert conditions. Once an alert rule is created from a database watcher template, you can manage it just like any other alert rule in Azure Monitor Alerts. You can use all capabilities of Azure alerting: email, SMS, and phone notifications, integration with ITSM products, webhooks, event hubs, and more. You can customize alert rules created from database watcher templates, or create your own alert rules.
+To help you create alert rules, database watcher includes templates for common alert conditions. Once an alert rule is created from a template, you can manage it just like any other alert rule in Azure Monitor Alerts. You can use all capabilities of Azure alerting: email, SMS, and phone notifications, integration with ITSM products, webhooks, event hubs, and more. You can customize alert rules created from database watcher templates, or create your own alert rules.
 
 To learn more about Azure Monitor Alerts, see:
 
@@ -201,8 +201,8 @@ You can see all alert instances and their state on the Azure Monitor **Alerts**
 
 - [What are Azure Monitor alerts?](/azure/azure-monitor/alerts/alerts-overview)
 - [Monitor Azure SQL workloads with database watcher (preview)](database-watcher-overview.md)
-- [Quickstart: Create a database watcher to monitor Azure SQL (preview)](database-watcher-quickstart.md)
-- [Create and configure a database watcher (preview)](database-watcher-manage.md)
+- [Quickstart: Create a watcher to monitor Azure SQL (preview)](database-watcher-quickstart.md)
+- [Create and configure a watcher (preview)](database-watcher-manage.md)
 - [Database watcher data collection and datasets (preview)](database-watcher-data.md)
 - [Analyze database watcher monitoring data (preview)](database-watcher-analyze.md)
 - [Database watcher FAQ](database-watcher-faq.yml)

azure-sql/database-watcher-analyze.md

@@ -5,7 +5,7 @@ description: Examples of analytical queries that use database watcher monitoring
 author: lcwright
 ms.author: lancewright
 ms.reviewer: dfurman
-ms.date: 02/07/2025
+ms.date: 05/04/2025
 ms.service: azure-sql
 ms.subservice: monitoring
 ms.topic: how-to
@@ -778,7 +778,7 @@ You can connect to your Azure Data Explorer or Real-Time Analytics database from
 >
 > The [SQL to Kusto Query Language cheat sheet](/azure/data-explorer/kusto/query/sql-cheat-sheet) can help you translate your T-SQL queries to KQL if you find that T-SQL support is insufficient for your needs, or if you want to convert your T-SQL queries to KQL to use its advanced analytical capabilities.
 
-The following examples show you how to query monitoring data in the database watcher data store using T-SQL.
+The following examples show you how to query monitoring data in the watcher data store using T-SQL.
 
 ### Use T-SQL to analyze resource consumption over time
 
@@ -1661,8 +1661,8 @@ ORDER BY wait_time_ms_per_sec DESC;
 ## Related content
 
 - [Monitor Azure SQL workloads with database watcher (preview)](database-watcher-overview.md)
-- [Quickstart: Create a database watcher to monitor Azure SQL (preview)](database-watcher-quickstart.md)
-- [Create and configure a database watcher (preview)](database-watcher-manage.md)
+- [Quickstart: Create a watcher to monitor Azure SQL (preview)](database-watcher-quickstart.md)
+- [Create and configure a watcher (preview)](database-watcher-manage.md)
 - [Database watcher alerts (preview)](database-watcher-alerts.md)
 - [Database watcher FAQ](database-watcher-faq.yml)
 - [Kusto Query Language learning resources](/azure/data-explorer/kql-learning-resources)

azure-sql/database-watcher-data.md

@@ -5,7 +5,7 @@ description: A detailed description of SQL monitoring data collected by database
 author: lcwright
 ms.author: lancewright
 ms.reviewer: dfurman
-ms.date: 12/20/2024
+ms.date: 05/04/2025
 ms.service: azure-sql
 ms.subservice: monitoring
 ms.topic: conceptual
@@ -40,13 +40,13 @@ To further reduce the risk of impact to application workloads, all database watc
 
 # [SQL managed instance](#tab/sqlmi)
 
-If there is resource contention between your application workloads and database watcher monitoring queries in Azure SQL Managed Instance, you can enable [Resource Governor](/sql/relational-databases/resource-governor/resource-governor) to limit resource consumption by the monitoring queries.
+If there is resource contention between your application workloads and database watcher monitoring queries in Azure SQL Managed Instance, you can enable [resource governor](/sql/relational-databases/resource-governor/resource-governor) to limit resource consumption by the monitoring queries.
 
-The following example configures Resource Governor on a SQL managed instance. It limits CPU consumption by database watcher queries to 30% when there is no CPU contention. When there is CPU contention, this configuration reserves 5% of CPU for the monitoring queries and limits their CPU usage to 10%. It also limits the memory grant size for each monitoring query to 10% of the available memory.
+The following example configures resource governor on a SQL managed instance. It limits CPU consumption by database watcher queries to 30% when there is no CPU contention. When there is CPU contention, this configuration reserves 5% of CPU for the monitoring queries and limits their CPU usage to 10%. It also limits the memory grant size for each monitoring query to 10% of the available memory.
 
 > [!NOTE]
 >
-> If you make Resource Governor configuration too restrictive, for example by using low `MAX_CPU_PERCENT` or `CAP_CPU_PERCENT` values, database watcher might not be able to collect data reliably or at all because of insufficient compute resources.
+> If you make resource governor configuration too restrictive, for example by using low `MAX_CPU_PERCENT` or `CAP_CPU_PERCENT` values, database watcher might not be able to collect data reliably or at all because of insufficient compute resources.
 
 ```sql
 USE master;
@@ -75,7 +75,7 @@ IF EXISTS (
           FROM sys.resource_governor_configuration
           WHERE classifier_function_id <> 0 OR is_enabled <> 0
           )
-    THROW 50001, 'Resource Governor is already configured. No changes were made.', 1;
+    THROW 50001, 'A resource governor configuration is already present. No changes were made.', 1;
 
 CREATE RESOURCE POOL database_watcher_resource_pool
 WITH (MIN_CPU_PERCENT = 5, MAX_CPU_PERCENT = 10, CAP_CPU_PERCENT = 30);
@@ -95,7 +95,7 @@ END CATCH;
 ```
 
 > [!TIP]
-> To make a new Resource Governor configuration effective on a high availability secondary replica of a SQL managed instance immediately, [connect](./database/read-scale-out.md#connect-to-a-read-only-replica) to the replica and execute `ALTER RESOURCE GOVERNOR RECONFIGURE;`.
+> To make a new resource governor configuration effective on a high availability secondary replica of a SQL managed instance immediately, [connect](./database/read-scale-out.md#connect-to-a-read-only-replica) to the `master` database on the replica and execute `ALTER RESOURCE GOVERNOR RECONFIGURE;`.
 
 ---
 
@@ -105,7 +105,7 @@ You might observe gaps in the collected data if the overall resource utilization
 
 ### Data collection in elastic pools
 
-To monitor an elastic pool, you must designate one database in the pool as the **anchor database**. Database watcher connects to the anchor database. Because the watcher [holds](database-watcher-overview.md#watcher-authorization) the `VIEW SERVER PERFORMANCE STATE` permission, system views in the anchor database provide monitoring data for the pool as a whole.
+To monitor an elastic pool, you must designate one database in the pool as the **anchor database**. A watcher connects to the anchor database. Because the watcher [holds](database-watcher-overview.md#watcher-authorization) the `VIEW SERVER PERFORMANCE STATE` permission, system views in the anchor database provide monitoring data for the pool as a whole.
 
 > [!TIP]
 > You can add an empty database to each elastic pool you want to monitor, and designate it as the anchor database. This way, you can move other databases in and out of the pool, or between pools, without interrupting elastic pool monitoring.
@@ -290,13 +290,13 @@ For each SQL target type, datasets have common columns, as described in the foll
 
 A dataset has both `sample_time_utc` and `collection_time_utc` columns if it contains samples observed before the row was collected by database watcher. Otherwise, the observation time and collection time are the same, and the dataset contains only the `sample_time_utc` column.
 
-For example, the `sqldb_database_resource_utilization` dataset is derived from the [sys.dm_db_resource_stats](/sql/relational-databases/system-dynamic-management-views/sys-dm-db-resource-stats-azure-sql-database) dynamic management view (DMV). The DMV contains the `end_time` column, which is the observation time for each row reporting aggregate resource statistics for a 15-second interval. This time is reported in the `sample_time_utc` column. When database watcher queries this DMV, the result set might contain multiple rows, each with a different `end_time`. All of these rows have the same `collection_time_utc` value.
+For example, the `sqldb_database_resource_utilization` dataset is derived from the [sys.dm_db_resource_stats](/sql/relational-databases/system-dynamic-management-views/sys-dm-db-resource-stats-azure-sql-database) dynamic management view (DMV). The DMV contains the `end_time` column, which is the observation time for each row reporting aggregate resource statistics for a 15-second interval. This time is reported in the `sample_time_utc` column. When a watcher queries this DMV, the result set might contain multiple rows, each with a different `end_time`. All of these rows have the same `collection_time_utc` value.
 
 ## Related content
 
 - [Monitor Azure SQL workloads with database watcher (preview)](database-watcher-overview.md)
-- [Quickstart: Create a database watcher to monitor Azure SQL (preview)](database-watcher-quickstart.md)
-- [Create and configure a database watcher (preview)](database-watcher-manage.md)
+- [Quickstart: Create a watcher to monitor Azure SQL (preview)](database-watcher-quickstart.md)
+- [Create and configure a watcher (preview)](database-watcher-manage.md)
 - [Analyze database watcher monitoring data (preview)](database-watcher-analyze.md)
 - [Database watcher alerts (preview)](database-watcher-alerts.md)
 - [Database watcher FAQ](database-watcher-faq.yml)

azure-sql/database-watcher-faq.yml

@@ -5,7 +5,7 @@ metadata:
   description: Frequently asked questions about database watcher for Azure SQL
   author: lcwright
   ms.author: lancewright
-  ms.date: 02/07/2025
+  ms.date: 05/04/2025
   ms.reviewer: wiassaf, dfurman
   ms.service: azure-sql
   ms.subservice: monitoring
@@ -70,7 +70,7 @@ sections:
     questions:
       - question: |
           Can I create and configure a watcher using Bicep, an ARM template, or Terraform?
-        answer: Yes. See [Create a database watcher](/samples/azure/azure-quickstart-templates/create-watcher/) for Bicep and ARM template examples you can customize to your needs. See [Azure resource reference](/azure/templates/microsoft.databasewatcher/watchers) documentation for Bicep, ARM template, and Terraform resource definitions.
+        answer: Yes. See [Create a watcher](/samples/azure/azure-quickstart-templates/create-watcher/) for Bicep and ARM template examples you can customize to your needs. See [Azure resource reference](/azure/templates/microsoft.databasewatcher/watchers) documentation for Bicep, ARM template, and Terraform resource definitions.
 
       - question: |
           Can I create and configure a watcher with PowerShell or Azure CLI?
@@ -95,7 +95,7 @@ sections:
         answer: You can use a database on an [Azure Data Explorer cluster](/azure/data-explorer/data-explorer-overview), on a [free Azure Data Explorer cluster](/azure/data-explorer/start-for-free), or in [Real-Time Analytics](/fabric/real-time-analytics/overview) in Microsoft Fabric. To compare between these options, see [What is the difference between Real-Time Analytics and Azure Data Explorer?](/fabric/real-time-analytics/realtime-analytics-compare)
 
       - question: |
-          I already have an Azure Data Explorer cluster. Can I use it for my database watcher data store?
+          I already have an Azure Data Explorer cluster. Can I use it as my watcher's data store?
         answer: Yes, if [streaming ingestion](database-watcher-manage.md#streaming-ingestion) is enabled on this cluster. Create a new database and grant the managed identity of a watcher [access](database-watcher-manage.md#grant-access-to-data-store) to this database. For smaller cluster SKUs, and depending on the query and ingestion workloads already running, you might need to [scale](database-watcher-manage.md#scale-azure-data-explorer-cluster) the cluster to support the additional load.
 
       - question: |
@@ -117,7 +117,7 @@ sections:
         answer: A remote data collection agent running on a Microsoft managed compute hosting platform connects to your Azure SQL resources, periodically executes T-SQL queries to collect monitoring data from SQL system views, and ingests this data into the data store.
 
       - question: |
-          Will database watcher impact my workload performance?
+          Will database watcher affect my workload performance?
         answer: This is unlikely. For details, see [Data collection](database-watcher-data.md#interaction-between-database-watcher-and-application-workloads).
 
       - question: |
@@ -134,7 +134,7 @@ sections:
 
       - question: |
           How does it connect to monitoring targets?
-        answer: Database watcher can use [Azure Private Link](/azure/private-link/private-link-overview) to connect to monitoring targets. When configuring a watcher, create managed private endpoints for your Azure SQL resources. The resource owner must approve each private endpoint for database watcher to use it. Public connectivity is supported as well. For more information, see [Network connectivity](database-watcher-overview.md#network-connectivity).
+        answer: Database watcher can use [Azure Private Link](/azure/private-link/private-link-overview) to connect to monitoring targets. When configuring a watcher, create managed private endpoints for your Azure SQL resources. The resource owner must approve each private endpoint for a watcher to use it. Public connectivity is supported as well. For more information, see [Network connectivity](database-watcher-overview.md#network-connectivity).
 
       - question: |
           How does it authenticate to monitoring targets?
@@ -168,8 +168,8 @@ additionalContent: |
   ## Related content
   
   - [Monitor Azure SQL workloads with database watcher](database-watcher-overview.md)
-  - [Quickstart: Create a database watcher to monitor Azure SQL](database-watcher-quickstart.md)
-  - [Create and configure a database watcher](database-watcher-manage.md)
+  - [Quickstart: Create a watcher to monitor Azure SQL](database-watcher-quickstart.md)
+  - [Create and configure a watcher](database-watcher-manage.md)
   - [Database watcher data collection and datasets](database-watcher-data.md)
   - [Analyze database watcher monitoring data](database-watcher-analyze.md)
   - [Database watcher alerts](database-watcher-alerts.md)