Merge pull request #2465 from MicrosoftDocs/main639002522112976912sync_temp

learn-build-service-prod[bot] · web-flow · commit e684b7e4c800 · 2025-12-02T06:03:43.000Z
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
diff --git a/docs/mirroring/azure-sql-database-limitations.md b/docs/mirroring/azure-sql-database-limitations.md
@@ -49,8 +49,8 @@ For troubleshooting, see:
 
 ## Table level
 
-- A table cannot be mirrored if the primary key is one of the data types: **sql_variant**, **timestamp**/**rowversion**.
-- Tables with clustered index on unsupported types cannot be mirrored - **computed columns**, **user-defined types**, **geometry**, **geography**, **hierarchy ID**, **SQL variant**, **timestamp**, **datetime2(7)**, **datetimeoffset(7)**, or **time(7)**.
+- Tables with primary key or a clustered index (when a primary key does not exist) on unsupported types cannot be mirrored - **computed columns**, **user-defined types**, **geometry**, **geography**, **hierarchy ID**, **SQL variant**, **timestamp**, **datetime2(7)**, **datetimeoffset(7)**, or **time(7)**.
+
 - Delta lake supports only six digits of precision.
    - Columns of SQL type **datetime2**, with precision of 7 fractional second digits, do not have a corresponding data type with same precision in Delta files in Fabric OneLake. A precision loss happens if columns of this type are mirrored and seventh decimal second digit will be trimmed.
    - A table cannot be mirrored if the primary key is one of these data types: **datetime2(7)**, **datetimeoffset(7)**, **time(7)**, where `7` is seven digits of precision.
diff --git a/docs/mirroring/azure-sql-database-troubleshoot.md b/docs/mirroring/azure-sql-database-troubleshoot.md
@@ -24,7 +24,7 @@ Changes to the Fabric capacity or workspace can affect mirroring. For more infor
 | Cause    | Result | Recommended resolution     |
 |:--|:--|:--|
 | Workspace deleted | Mirroring stops automatically and disables the change feed in Azure SQL Database |In case mirroring is still active on the Azure SQL Database, execute the following stored procedure on your Azure SQL Database: `exec sp_change_feed_disable_db;`. |
-| Persistent errors | Mirroring is disabled |To ensure your compute resources aren't affected and to protect your source Azure SQL Database, mirroring can be disabled on any persistent errors. Review [sys.dm_change_feed_errors](/sql/relational-databases/system-dynamic-management-views/sys-dm-change-feed-errors/?view=azuresqldb-current&preserve-view=true) and resolve the underlying errors before re-enabling the table for mirroring.|
+| Persistent errors | Mirroring is disabled for the affected database|To ensure your compute resources aren't affected and to protect your source Azure SQL Database, mirroring will be disabled on any persistent errors. Review [sys.dm_change_feed_errors](/sql/relational-databases/system-dynamic-management-views/sys-dm-change-feed-errors/?view=azuresqldb-current&preserve-view=true) and resolve the underlying errors before re-enabling the database for mirroring.|
 | "Users can access data stored in OneLake with apps external to Fabric" setting disabled | "Replicator - Tables Cannot Reach Replicating Status" |Enable the Tenant setting [Users can access data stored in OneLake with apps external to Fabric](../admin/tenant-settings-index.md#onelake-settings).|
 
 For additional troubleshooting scenarios, see [Troubleshoot Fabric Mirrored Databases - Microsoft Fabric](/fabric/mirroring/troubleshooting).
diff --git a/docs/mirroring/azure-sql-managed-instance-limitations.md b/docs/mirroring/azure-sql-managed-instance-limitations.md
@@ -57,14 +57,12 @@ The feature availability also depends on Fabric regions. For a complete list of
 
 ## Table level
 
-- A table cannot be mirrored if the primary key is one of the data types: **sql_variant**, **timestamp**/**rowversion, datetime2(7)**, **datetimeoffset(7)**, **time(7)**, where `7` is seven digits of precision.
+- Tables with primary key or a clustered index (when a primary key does not exist) on unsupported types cannot be mirrored - **computed columns**, **user-defined types**, **geometry**, **geography**, **hierarchy ID**, **SQL variant**, **timestamp**, **datetime2(7)**, **datetimeoffset(7)**, or **time(7)**.
 
 - Delta lake supports only six digits of precision.
   - Columns of SQL type **datetime2**, with precision of 7 fractional second digits, do not have a corresponding data type with same precision in Delta files in Fabric OneLake. A precision loss happens if columns of this type are mirrored and seventh decimal second digit will be trimmed.
   - The **datetimeoffset(7)** data type does not have a corresponding data type with same precision in Delta files in Fabric OneLake. A precision loss (loss of time zone and seventh time decimal) occurs if columns of this type are mirrored.   
 - Clustered columnstore indexes aren't currently supported.
-- Tables with clustered index on unsupported types cannot be mirrored - **computed columns**, **user-defined types**, **geometry**, **geography**, **hierarchy ID**, **SQL variant**, **timestamp**, **datetime2(7)**, **datetimeoffset(7**) or **time(7).**
-
 - If one or more columns in the table is of type Large Binary Object (LOB) with a **size > 1 MB**, the column data is **truncated** to size of 1 MB in Fabric OneLake. [Configure the max text repl size](/sql/database-engine/configure-windows/configure-the-max-text-repl-size-server-configuration-option) server configuration option to allow more than 65,536 bytes if you want to allow large inserts.
 - Source tables that have any of the following features in use can't be mirrored:
   - Temporal history tables and ledger history tables  
diff --git a/docs/mirroring/azure-sql-managed-instance-troubleshoot.md b/docs/mirroring/azure-sql-managed-instance-troubleshoot.md
@@ -13,13 +13,15 @@ This article covers troubleshooting steps troubleshooting for mirroring Azure SQ
 
 ## Changes to Fabric capacity or workspace
 
-Learn more from [Changes to Fabric capacity](troubleshooting.md#changes-to-fabric-capacity). 
+Changes to the Fabric capacity or workspace can affect mirroring. For more information, review the effects on mirroring from [Changes to Fabric capacity](troubleshooting.md#changes-to-fabric-capacity). 
 
-In addition, note the following for Azure SQL Managed Instance specifically:
+## Azure SQL Managed Instance troubleshooting
 
-| Cause    | Result | Recommended resolution     |
-|:--|:--|:--|
-| Workspace deleted | Mirroring stops automatically and disables the change feed in Azure SQL Managed Instance | In case the mirroring is still active on the Azure SQL Managed Instance, execute the following stored procedure on your Azure SQL Managed Instance: `exec sp_change_feed_disable_db;`. |
+|Cause|Result|Recommended resolution|
+| :-- | :-- | :-- |
+|Workspace deleted|Mirroring stops automatically and disables the change feed in Azure SQL Managed Instance|In case mirroring is still active on the Azure SQL Managed Instance, execute the following stored procedure for each affected database on your Azure SQL Managed Instance: `exec sp_change_feed_disable_db;`.|
+|Persistent errors|Mirroring is disabled for the affected database|To ensure your compute resources aren't affected and to protect your source database in Azure SQL Managed Instance, mirroring will be disabled on any persistent errors. Review [sys.dm_change_feed_errors](/sql/relational-databases/system-dynamic-management-views/sys-dm-change-feed-errors?view=azuresqldb-mi-current&preserve-view=true) and resolve the underlying errors before re-enabling the database for mirroring.|
+|"Users can access data stored in OneLake with apps external to Fabric" setting disabled|"Replicator - Tables Cannot Reach Replicating Status"|Enable the Tenant setting [Users can access data stored in OneLake with apps external to Fabric](../admin/tenant-settings-index.md#onelake-settings).|
 
 ## T-SQL queries for troubleshooting
 
diff --git a/docs/mirroring/includes/fabric-mirroring-azure-sql-database-managed-instance-automatic-reseed.md b/docs/mirroring/includes/fabric-mirroring-azure-sql-database-managed-instance-automatic-reseed.md
@@ -1,14 +1,14 @@
 ---
 author: WilliamDAssafMSFT
 ms.author: wiassaf
-ms.date: 11/25/2025
+ms.date: 12/01/2025
 ms.topic: include
 # For docs\mirroring\azure-sql-database-automatic-reseed.md and docs\mirroring\azure-sql-managed-instance-automatic-reseed.md
 ---
 
 Under certain conditions if there is a delay in mirroring to Fabric, increased transaction log file usage can result. The transaction log cannot be truncated until after committed changes are replicated to the mirrored database. Once the transaction log size reaches its maximum defined limit, writes to the database fail. To safeguard operational databases from write failures for critical OLTP transactions, you can set up an autoreseed mechanism that allows the transaction log to be truncated and reinitializes the database mirroring to Fabric.
 
-The autoreseed feature is enabled and cannot be managed or disabled in Azure SQL Database and Azure SQL Managed Instance.
+To safeguard operational databases from write failures for critical OLTP transactions, mirroring in Azure SQL Database and Azure SQL Managed Instance uses the autoreseed capability that allows the transaction log to be truncated and reinitializes the database mirroring to Fabric.
 
 A reseed stops flow of transactions to Microsoft Fabric from the mirrored database and reinitializes the mirroring at the present state. A reseed involves generating a new initial snapshot of the tables configured for mirroring, and replicating that to Microsoft Fabric. After the snapshot, incremental changes are replicated. 
 
@@ -32,8 +32,6 @@ A reseed at the database level protects database write availability by ensuring
       > [!NOTE]  
       > Support for User Assigned Managed Identity (UAMI) is currently in preview.
 
-    To safeguard against this issue, mirroring triggers an automatic reseed of the whole database when the log space used has passed a certain threshold of total configured log space.
-
 - If the Fabric capacity is paused and resumed, the mirrored database status remains **Paused**. As a result, changes made in the source aren't replicated to OneLake. To resume mirroring, go to the mirrored database in the Fabric portal, select **Resume replication**. Mirroring continues from where it was paused. 
 
    If the Fabric capacity remains paused for a long time, mirroring might not resume from its stopping point and will reseed data from the beginning. This is because pausing mirroring for a long time can cause the source database transaction log usage to grow and hold up log truncation. When mirroring is resumed, if the transaction log file space used is close to full, a reseed of the database will be initiated to release the held up log space.
diff --git a/docs/mirroring/sql-server-limitations.md b/docs/mirroring/sql-server-limitations.md
@@ -55,15 +55,13 @@ For troubleshooting, see:
 
 ## Table level
 
-- A table cannot be mirrored if the primary key is one of the data types: **sql_variant**, **timestamp**/**rowversion****, datetime2(7)**, **datetimeoffset(7)**, **time(7)**, where `7` is seven digits of precision.
+- Tables with primary key or a clustered index (when a primary key does not exist) on unsupported types cannot be mirrored - **computed columns**, **user-defined types**, **geometry**, **geography**, **hierarchy ID**, **SQL variant**, **timestamp**, **datetime2(7)**, **datetimeoffset(7)**, or **time(7)**.
 
 - When mirroring SQL Server 2016 thru SQL Server 2022, a table cannot be mirrored if it does not have a primary key.
 - Delta lake supports only six digits of precision.
    - Columns of SQL type **datetime2**, with precision of 7 fractional second digits, do not have a corresponding data type with same precision in Delta files in Fabric OneLake. A precision loss happens if columns of this type are mirrored and seventh decimal second digit will be trimmed.
   - The **datetimeoffset(7)** data type does not have a corresponding data type with same precision in Delta files in Fabric OneLake. A precision loss (loss of time zone and seventh time decimal) occurs if columns of this type are mirrored.
 - Clustered columnstore indexes are not currently supported.
-- Tables with clustered index on unsupported types cannot be mirrored - **computed columns**, **user-defined types**, **geometry**, **geography**, **hierarchy ID**, **SQL variant**, **timestamp**, **datetime2(7)**, **datetimeoffset(7**) or **time(7).**
-
 - If one or more columns in the table is of type Large Binary Object (LOB) with a size > 1 MB, the column data is truncated to size of 1 MB in Fabric OneLake.
 - Source tables that have any of the following features in use cannot be mirrored.
     - Temporal history tables and ledger history tables  
