From 0d5dd9be647c91fb71bc901b20200cdd1fde6b5d Mon Sep 17 00:00:00 2001 From: kendra-little <146201001+kendra-little@users.noreply.github.com> Date: Tue, 3 Jun 2025 09:56:15 -0400 Subject: [PATCH] Add information that catalog corruption can cause instance crashes Please document that the catalog corruption can cause stack dumps and crashes of the SQL Server service. This has been verified by Microsoft Support, see case TrackingID #2504240010002403 --- azure-sql/managed-instance/doc-changes-updates-known-issues.md | 1 + 1 file changed, 1 insertion(+) diff --git a/azure-sql/managed-instance/doc-changes-updates-known-issues.md b/azure-sql/managed-instance/doc-changes-updates-known-issues.md index 892e1a70f71..ad17a55f8c6 100644 --- a/azure-sql/managed-instance/doc-changes-updates-known-issues.md +++ b/azure-sql/managed-instance/doc-changes-updates-known-issues.md @@ -92,6 +92,7 @@ You may see the following error when you run the DBCC CHECKDB command on a SQL S _Msg 8992, Level 16, State 1, Line 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._ ``` +This metadata corruption may cause stack dumps and crashes of the SQL Server service. 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.