Merge pull request #30266 from dimitri-furman/database-watcher

Add REST API doc links and a known issue

Author: prmerger-automator[bot]

azure-sql/database-watcher-faq.yml

@@ -71,7 +71,7 @@ sections:
     questions:
       - question: |
           Can I create and configure a watcher with PowerShell or Azure CLI?
-        answer: Not at this time. You can create and configure watchers in the Azure portal or using ARM and Bicep templates. For planned improvements to database watcher, see the roadmap section in the database watcher [preview announcement](https://aka.ms/dbwatcher-preview-announcement).
+        answer: Not at this time. You can create and configure watchers in the Azure portal, using ARM and Bicep templates, or using [REST API](/rest/api/databasewatcher). For planned improvements to database watcher, see the roadmap section in the database watcher [preview announcement](https://aka.ms/dbwatcher-preview-announcement).
 
       - question: |
           Does a watcher have an identity I can use to grant it access to my Azure resources?

azure-sql/database-watcher-manage.md

@@ -24,6 +24,8 @@ This article contains detailed steps for creating, configuring, and starting a d
 
 For a step-by-step example of creating and configuring a database watcher, see [Quickstart: Create a database watcher to monitor Azure SQL](database-watcher-quickstart.md).
 
+To manage watchers programmatically, see the database watcher [REST API](/rest/api/databasewatcher) documentation.
+
 > [!NOTE]
 > Database watcher is currently in preview. Preview features are released with limited capabilities, but are made available on a *preview* basis so customers can get early access and provide feedback. Preview features are subject to separate [supplemental preview terms](https://go.microsoft.com/fwlink/?linkid=2240967), and aren't subject to SLAs. Support is provided as best effort in certain cases. However, Microsoft Support is eager to get your feedback on the preview functionality, and might provide best effort support in certain cases. Preview features might have limited or restricted functionality, and might be available only in selected geographic areas.
 

azure-sql/database-watcher-overview.md

@@ -205,6 +205,7 @@ During preview, database watcher has the following known issues.
 | When adding a **SQL database** target, the list of databases shown in the dropdown is incomplete if there are more than 1,000 databases on the selected logical server. | None at this time. |
 | Feedback sent using the smiley face button on the database watcher dashboards in Azure portal might not reach the database watcher product team. | Use the options in [Send feedback](#send-feedback). |
 | Because of a known issue in Azure SQL Database, you cannot create [database copies](./database/database-copy.md#copy-using-transact-sql) and [geo-replicas](./database/active-geo-replication-overview.md#programmatically-managing-active-geo-replication) via T-SQL when a login is added to a [server role](./database/security-server-roles.md). Because database watcher logins must be [added to a set of server roles](#watcher-authorization), creation of database copies and geo-replicas via T-SQL stops working if you enable database watcher. | To create database copies or geo-replicas via T-SQL, remove the database watcher login from the `##MS_ServerPerformanceStateReader##`, `##MS_DefinitionReader##`, and `##MS_DatabaseConnector##` server roles. To restore database watcher functionality once a database copy completes or once a geo-replica is created, add the login to these server roles again to [grant the watcher access](database-watcher-manage.md#grant-access-to-sql-targets) to SQL targets.</br></br>Database copies and geo-replicas created in the Azure portal or programmatically via PowerShell, Azure CLI, and REST API are not affected. |
+| In Azure SQL Managed Instance, data is not collected if the `EXECUTE` permission on the `sys.xp_msver` system stored procedure is revoked or denied to the `public` role. | Grant the `EXECUTE` permission on `sys.xp_msver` to the database watcher login.</br></br>On every SQL managed instance added as a database watcher target, execute `USE master; CREATE USER [database-watcher-login-placeholder] FOR LOGIN [database-watcher-login-placeholder]; GRANT EXECUTE ON sys.xp_msver TO [database-watcher-login-placeholder];`, replacing `database-watcher-login-placeholder` with the name of the watcher login. |
 
 ## Troubleshoot