HI @salil singh
Avoid schema refresh timeout
If you have a complex schema to sync, you may encounter an "operation timeout" during a schema refresh if the sync metadata database has a lower SKU (example: basic).
To mitigate this issue, please scale up your sync metadata database to have a higher SKU, such as S3.
Troubleshoot issues with SQL Data Sync
- Tables with a primary key can only be replicated
- User-defined data types are not supported
- Computed columns are not supported
- Tables with identity column which is non-primary key are not supported in Azure SQL data sync
- Tables with the same name but different schema are not supported
- You must manage identity columns manually. No auto identity management like in SQL Server replication. In case if you insert a row with the same identity value on hub and master, the insert will be lost based on your conflict resolution
- Supports only data sync not the schema changes. For example, if you insert a row in member database with identity value 1 and there is an insert with same identity value on hub database, if the conflict resolution is set to member win then the row inserted at the Azure SQL hub database is deleted and row inserted at member will be persisted in both member and hub databases
- The initial sync will only create a table on the member database, not the other objects created on top of the table like triggers, foreign keys, etc.
- Continuous synchronization is not supported. The minimum sync frequency interval is 5 minutes
If the Answer is helpful, please click
Accept Answer and up-vote, this can be beneficial to other community members.