Merging changes synced from https://github.com/MicrosoftDocs/sql-docs-pr (branch live)

Author: Learn Build Service GitHub App

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: 02/21/2024
+ms.date: 03/13/2025
 ms.service: azure-sql
 ms.subservice: monitoring
 ms.topic: conceptual
@@ -250,6 +250,7 @@ During preview, database watcher has the following known issues.
 | Data is not collected if you use a database in Real-Time Analytics as the data store, and the **OneLake availability** option is enabled. | Disable the **OneLake availability** option and restart the watcher to resume data collection. |
 | Because of a known issue in Azure SQL Database, data in the **Backup history** dataset for Azure SQL databases is not collected if the database catalog collation is other than the default `SQL_Latin1_General_CP1_CI_AS`. | None at this time. |
 | Because of a known issue in Azure Monitor Alerts, if you edit an alert rule created from a database watcher template, the scope of any fired alert will be set to the Azure Data Explorer cluster used as the watcher data store instead of the SQL target that the alert applies to. | Edit the alert rule programmatically, for example using Bicep or an ARM template, and set the `resourceIdColumn` property to the value `resource_id`. For more information, see [Resource Manager template samples for log search alert rules in Azure Monitor](/azure/azure-monitor/alerts/resource-manager-alerts-log). |
+| A database watcher deployment via Bicep, an ARM template, Terraform, or REST API fails if the **subscription ID**, **resource group name**, or **watcher name** deployment parameters use inconsistent casing. For example, adding a SQL target for an existing watcher named `example-watcher` fails if the deployment parameter uses `Example-Watcher` as the parameter value. | Use consistent casing for string parameters. For example, standardize on the lower case. |
 
 ## Troubleshoot
 

azure-sql/managed-instance/doc-changes-updates-known-issues.md

@@ -5,7 +5,7 @@ description: Learn about the currently known issues with Azure SQL Managed Insta
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest, mathoma
-ms.date: 07/02/2024
+ms.date: 03/14/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: service-overview
 ms.topic: troubleshooting-known-issue
@@ -24,6 +24,7 @@ This article lists the currently known issues with [Azure SQL Managed Instance](
 
 | Issue | Date discovered | Status | Date resolved |
 | --- | --- | --- | --- |
+| [Error 8992 when running DBCC CHECKDB on a SQL Server database that originated from SQL Managed Instance](#error-8992-when-running-dbcc-checkdb-on-a-sql-server-database-that-originated-from-sql-managed-instance) | March 2025 | Has workaround| |
 | [Differential backups aren't taken when an instance is linked to SQL Server](#differential-backups-arent-taken-when-an-instance-is-linked-to-sql-server) | Sept 2024 | By design | |
 | [List of long-term backups in Azure portal shows backup files for active and deleted databases with the same name](#list-of-long-term-backups-in-azure-portal-shows-backup-files-for-active-and-deleted-databases-with-the-same-name) | Mar 2024 | Has Workaround | |
 | [Temporary instance inaccessibility using the failover group listener during scaling operation](#temporary-instance-inaccessibility-using-the-failover-group-listener-during-scaling-operation) | Jan 2024 | No resolution | |
@@ -69,6 +70,17 @@ This article lists the currently known issues with [Azure SQL Managed Instance](
 
 ## Has workaround
 
+### Error 8992 when running DBCC CHECKDB on a SQL Server database that originated from SQL Managed Instance
+
+You may see the following error when you run the DBCC CHECKDB command on a SQL Server 2022 database after you delete an index, or a table with an index, and the database originated from Azure SQL Managed Instance, such as after restoring a backup file, or from the [Managed Instance link feature](/azure/azure-sql/managed-instance/managed-instance-link-feature-overview): 
+
+```
+_Msg 8992, Level 16, State 1, Line <Line_Number>an
+Check Catalog Msg 3853, State 1: Attribute (%ls) of row (%ls) in sys.sysrowsetrefs does not have a matching row (%ls) in sys.indexes._
+```
+
+To work around the issue, first drop the index, or the table with the index, from the source database in Azure SQL Managed Instance, and then restore, or link, the database to SQL Server 2022 again. If recreating the database from the source Azure SQL Managed Instance isn't possible, please contact Microsoft support to help resolve this issue. 
+
 ### List of long-term backups in Azure portal shows backup files for active and deleted databases with the same name
 
 Long-term backups can be listed and managed on Azure portal page for an Azure SQL Managed Instance on _Backups_ tab. The page lists active or deleted databases, basic information about their long-term backups, and link for managing backups. When you select the _Manage_ link, a new side pane opens with list of backups. Due to an issue with the filtering logic, the list shows backups for both active database and deleted databases with the same name. This requires a special attention when selecting backups for deletion, to avoid deleting backups for a wrong database.

azure-sql/managed-instance/restore-database-to-sql-server.md

@@ -83,7 +83,6 @@ TO URL = 'https://<mystorageaccountname>.blob.core.windows.net/<containername>/S
 WITH COPY_ONLY
 ```
 
-
 ## Restore to SQL Server 
 
 Restore the database to SQL Server by using the `WITH MOVE` option of the RESTORE DATABASE T-SQL command and providing explicit file paths for your files on the destination server.
@@ -109,6 +108,7 @@ When you're restoring a database to SQL Server, consider the following:
 - You must use the `WITH MOVE` qualifier and provide explicit paths for the data files. 
 - Databases that are encrypted with service-managed TDE keys can't be restored to SQL Server. You can restore an encrypted database to SQL Server only if it was encrypted with a customer-managed key and the destination server has access to the same key that's used to encrypt the database. For more information, see [Set up SQL Server TDE with Azure Key Vault](/sql/relational-databases/security/encryption/setup-steps-for-extensible-key-management-using-the-azure-key-vault). 
 - This capability is only available to instances with the [**SQL Server 2022** update policy](update-policy.md#sql-server-2022-update-policy). You will not be able to restore your database backup to SQL Server 2022 from an instance with the **Always up to date** update policy. 
+- After restoring an Azure SQL Managed Instance database to SQL Server 2022, and dropping an index, or a table with an index, you may see [Error 8992](doc-changes-updates-known-issues.md#error-8992-when-running-dbcc-checkdb-on-a-sql-server-database-that-originated-from-sql-managed-instance) when running the `DBCC CHECKDB` command.
 
 ## Next steps
 

azure-sql/virtual-machines/windows/sql-server-iaas-agent-extension-automate-management.md

@@ -191,7 +191,7 @@ Starting in March 2023, when you first register with the extension, binaries are
 The SQL IaaS Agent extension only supports: 
 
 - SQL Server VMs deployed through the Azure Resource Manager. SQL Server VMs deployed through the classic model aren't supported. 
-- SQL Server VMs deployed to the public or Azure Government cloud. Deployments to other private or government clouds aren't supported. 
+- SQL Server VMs deployed to the public cloud, Azure Government cloud, and 21Vianet (Azure in China). Deployments to other private or government clouds aren't supported. 
 - TCP/IP must be enabled in SQL Server Configuration Manager and for the VM for the extension to work with your SQL Server on Azure VMs. 
 - SQL Server FCIs with limited functionality. SQL Server FCIs registered with the extension don't support features that require the agent, such as automated backup, patching, and advanced portal management. 
 - VMs with a default instance, or a single named instance when no default instance is present.

docs/sql-server/sql-server-2022-release-notes.md

@@ -4,7 +4,7 @@ description: Find information about SQL Server 2022 (16.x) limitations, known is
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest
-ms.date: 02/09/2023
+ms.date: 03/14/2025
 ms.service: sql
 ms.subservice: release-landing
 ms.topic: release-notes
@@ -116,6 +116,18 @@ You may notice excessive growth in the transaction log size for databases with t
 
 For more information, review [Transaction log file grows for databases with In-Memory OLTP in SQL Server 2022](/troubleshoot/sql/database-engine/general/transaction-log-file-grows-databases-in-memory-oltp).
 
+### DBCC CHECKDB command reports inconsistency after dropping index
+Applies to: [!INCLUDE [sssql22-md](../includes/sssql22-md.md)] databases that originated from [!INCLUDE [ssazuremi-md](../includes/ssazuremi-md.md)]
+
+You may see the following error when you run the DBCC CHECKDB command on a [!INCLUDE [sssql22-md](../includes/sssql22-md.md)] database after you delete an index, or a table with an index, and the database originated from [!INCLUDE [ssazuremi-md](../includes/ssazuremi-md.md)], such as after restoring a backup file, or from the [Managed Instance link feature](/azure/azure-sql/managed-instance/managed-instance-link-feature-overview): 
+
+```
+_Msg 8992, Level 16, State 1, Line <Line_Number>an
+Check Catalog Msg 3853, State 1: Attribute (%ls) of row (%ls) in sys.sysrowsetrefs does not have a matching row (%ls) in sys.indexes._
+```
+
+To work around the issue, first drop the index, or the table with the index, from the source database in [!INCLUDE [ssazuremi-md](../includes/ssazuremi-md.md)], and then restore, or link, the database to [!INCLUDE [sssql22-md](../includes/sssql22-md.md)] again. If recreating the database from the source [!INCLUDE [ssazuremi-md](../includes/ssazuremi-md.md)] isn't possible, please contact Microsoft support to help resolve this issue. 
+
 ## Build number
 
 | Preview build | Version number | Date |