Merge pull request #33325 from WilliamDAssafMSFT/20250227-data-sync

20250227 data sync

Author: prmerger-automator[bot]

azure-sql/database/sql-data-sync-data-sql-server-sql-database.md

@@ -4,7 +4,7 @@ description: This overview introduces SQL Data Sync for Azure, which allows you
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: mathoma, hudequei
-ms.date: 02/21/2025
+ms.date: 02/27/2025
 ms.service: azure-sql-database
 ms.subservice: sql-data-sync
 ms.topic: concept-article
@@ -163,20 +163,21 @@ Provisioning and deprovisioning during sync group creation, update, and deletion
 - Data Sync supports only the following two index properties: Unique, Clustered/Non-Clustered. Other properties of an index, like `IGNORE_DUP_KEY` or the `WHERE` filter predicate, aren't supported and the destination index is provisioned without these properties even if the source Index has these properties set.
 - An Azure Elastic jobs database can't be used as the SQL Data Sync Metadata database, and vice versa.
 - SQL Data Sync isn't supported for [ledger databases](/sql/relational-databases/security/ledger/ledger-database-ledger).
+- Data Sync is not a disaster recovery or high availability tool and does not synchronize its own Sync Group information. There is no automatic disaster recovery for Data Sync.
 
 #### Unsupported data types
 
 - FileStream
 - SQL/CLR UDT
 - XMLSchemaCollection (XML supported)
-- Cursor, RowVersion, Timestamp, Hierarchyid
+- Cursor, **RowVersion**, **Timestamp**, **Hierarchyid**
 
 #### Unsupported column types
 
 Data Sync can't sync read-only or system-generated columns. For example:
 
-- Computed columns.
-- System-generated columns for temporal tables.
+- Computed columns
+- System-generated columns for temporal tables
 
 #### Limitations on service and database dimensions
 
@@ -273,7 +274,7 @@ The Dynamics 365 bring your own database feature lets administrators export data
 
 ### How do I create Data Sync in Failover group to support Disaster Recovery?
 
-- To ensure data sync operations in failover region are at par with Primary region, after failover you have to manually re-create the Sync Group in failover region with same settings as primary region.
+SQL Data Sync offers no automatic failover or disaster recovery capabilities. In case of database failover to another region, Sync Group will stop working. Manually re-create the Sync Group in failover region with same settings as primary region.
 
 ## Related content