Merge pull request #8507 from sevend2/Error3853

AB#4639: SQL Server error 3853 when using incremental statistics and …

Author: sevend2

support/sql/database-engine/database-file-operations/error-3853-use-incremental-statistics-resumable-index-operations.md

@@ -0,0 +1,52 @@
+---
+title: Error 3853 When Using Incremental Statistics and Resumable Index Operations
+description: Resolves SQL Server error 3853 that occurs when you use incremental statistics and resumable index operations concurrently.
+ms.date: 04/03/2025
+ms.custom: sap:File, Filegroup, Database Operations or Corruption
+ms.reviewer: rtownsend, jopilov, jaferebe, atsingh, ditikman
+---
+
+# SQL Server error 3853 when using incremental statistics and resumable index operations concurrently
+
+_Applies to:_   SQL Server 2019, SQL Server 2017, SQL Server 2016
+
+## Symptoms
+ 
+When you run a [DBCC CHECKDB](/sql/t-sql/database-console-commands/dbcc-checkdb-transact-sql) command, the following output might be generated:
+
+```output
+Corruption in database ID %I64d, object ID %Id possibly due to schema or catalog inconsistency. Run DBCC CHECKCATALOG.
+```
+
+You might also see the following error message in the SQL Server error log:
+
+```output
+Attribute (%ls) of row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sys.%ls%ls.
+Msg 3853, Level 16, State 1, Line 10
+```
+
+## Cause
+
+The 3853 error is caused by orphaned records in the `sys.syssingleobjrefs` system table. The `stats_id` in `sys.stats` remains as `2`, while the corresponding `stats_id` in `syssingleobjrefs` is `896002`, indicating a mismatch. The issue happens when all of the following conditions are met:
+
+- The source `object_id` is a partitioned table or index.
+- Incremental statistics are in use for a table or index.
+- Index creation or rebuild is performed using the `RESUMABLE` option.
+- Incremental statistics are updated, or the index is rebuilt using the `ONLINE = ON` option.
+
+## Status
+
+Microsoft has confirmed that this is a known issue in the versions of SQL Server listed in the "Applies to" section at the top of the article. Microsoft has also confirmed that the issue has been fixed in [Microsoft SQL Server 2022](https://www.microsoft.com/sql-server/sql-server-downloads).
+
+## Workaround
+
+To avoid this issue, don't use incremental statistics and resumable index operations on the same table or index simultaneously.
+
+## Resolution
+
+If the issue occurs, try the following options:
+
+- Restore the database from the most recent valid backup.
+- Create a new database and import the data from the corrupted database using the SQL Server Import and Export Wizard, Bulk Copy Program (BCP) utility, or manual export-import method.
+- Upgrade to SQL Server 2022, where the issue has been fixed.
+- Contact the Microsoft Customer Support team to request assistance with correcting the metadata.

support/sql/database-engine/database-file-operations/toc.yml

@@ -19,6 +19,8 @@ items:
       href: troubleshoot-dbcc-checkdb-errors.md
 - name: Defragmenting database disk drives
   href: defragmenting-database-disk-drives.md
+- name: Error 3853 with incremental statistics and resumable index operations
+  href: error-3853-use-incremental-statistics-resumable-index-operations.md
 - name: I/O subsystem requirements for the tempdb
   href: io-subsystem-requirements-tempdb.md
 - name: Logging and data storage algorithms
@@ -40,4 +42,4 @@ items:
 - name: Troubleshoot errors related to system disk sector size greater than 4 KB
   href: troubleshoot-os-4kb-disk-sector-size.md
 - name: Virtual host drivers lead to data consistency problems
-  href: virtual-host-driver-lead-data-consistency.md
+  href: virtual-host-driver-lead-data-consistency.md