Updates from editor

Author: v-phoebh

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

@@ -1,25 +1,21 @@
 ---
-title: Error 3853 When Using Incremental Statistics And Resumable Index Operations
-description: Resolve SQL Server error 3853 that occurs when you use incremental statistics and resumable index operations concurrently.
-ms.date: 03/19/2025
+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: 03/26/2025
 ms.custom: sap:File, Filegroup, Database Operations or Corruption
 ms.reviewer: rtownsend
 ---
 
 # SQL Server error 3853 when using incremental statistics and resumable index operations concurrently
 
-## Applies to
-
-- Microsoft SQL Server 2019
-- Microsoft SQL Server 2017
-- Microsoft SQL Server 2016
+_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 %ld possibly due to schema or catalog inconsistency. Run DBCC CHECKCATALOG.
+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:
@@ -31,26 +27,26 @@ 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 while the corresponding `stats_id` in `syssingleobjrefs` is `896002`, indicating a mismatch. The issue occurs under the following scenarios:
+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 occurs under the following scenarios:
 
 - 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.
+- 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](#applies-to) section.  Microsoft has also confirmed that the issue has been fixed in [Microsoft SQL Server 2022](https://www.microsoft.com/sql-server/sql-server-downloads).
+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).
 
 ## Resolution
 
 If the issue occurs, try the following options:
 
 - Contact the Microsoft Customer Support team to request assistance with correcting the metadata.
 - Restore the database from the most recent valid backup.
-- Create a new database and import the data from the corrupted database using SQL Server Import and Export Wizard, BCP utility, or manual export-import methods.
-- Upgrade to SQL Server 2022 where the issue has been fixed.
+- 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.
 
 ## Workaround
 
-To avoid this issue, refrain from using incremental statistics and resumable index operations on the same table or index simultaneously.
+To avoid this issue, don't use incremental statistics and resumable index operations on the same table or index simultaneously.