Forum Discussion
Replicate Azure SQL database with a lag
Hello, I am new to Azure SQL database. I am being asked by my manager to replicate our Azure SQL databases to an Azure SQL VM with a lag of 3 hours. Does anyone know what solutions are availa...
Built-in geo-replication and failover groups are designed for near-real-time replication. They do not provide a fixed 3-hour intentional lag.
For a controlled delay to SQL Server on an Azure VM, use a scheduled data movement process instead, for example:
- Azure Data Factory or Synapse pipeline scheduled every 3 hours.
- Incremental copy based on watermark columns, change tracking, CDC, or last modified timestamps.
- SQL Agent/SSIS/custom ETL if you prefer to manage it on the VM side.
Avoid full database copy every 3 hours unless the database is very small. For most production cases, use incremental loading so the SQL Server VM receives changes on the schedule you control.
So the answer is: use ETL/scheduled incremental replication for a deliberate lag; use geo-replication/failover groups for HA/DR near-real-time replication.