SQL Data Sync retirement: Migrate to alternative solutions

Applies to: Azure SQL Database

SQL Data Sync will be retired on 30 September 2027. By then, consider migrating to alternatives data replication/synchronization solutions. This article details alternative solutions to migrate your data synchronization options.

Alternatives to SQL Data Sync

The right solution depends on your individual use case. We'll detail the alternative solutions including Azure Data Factory, Azure Functions, read replicas or SQL features like linked server, mirroring, Always On availability groups, or transactional replication.

SQL Data Sync is a service built on Azure SQL Database that lets you synchronize the data you select bi-directionally across multiple databases, both on premises and in the cloud. The three main scenarios for SQL Data Sync are:

• Hybrid data synchronization: You use SQL Data Sync to synchronize databases in SQL Server and Azure SQL Database.
• Distributed applications: You use SQL Data Sync to separate the workload across different databases for reporting purposes.
• Globally-distributed applications: You use SQL Data Sync to synchronize data across different regions.

The alternatives to replace SQL Data Sync depend on the scenario and platforms. Different use cases and platforms have different alternatives.

Hybrid data synchronization

This scenario is most used to synchronize data from a SQL Server instance (on-premises or Azure Virtual Machine) to Azure SQL Database or Azure SQL Managed Instance. The possible migration paths are:

• Always On availability groups tutorials:

  • Always On availability groups
  • Managed Instance link feature overview - Azure SQL Managed Instance

• Azure Data Factory tutorials:

  • Copy on-premises data using the Azure Copy Data tool - Azure Data Factory
  • Copy data in bulk using Azure portal - Azure Data Factory

• Transactional replication tutorial:

  • Transactional replication - SQL Server

• Linked server tutorial:

  • Linked servers (Database Engine) - SQL Server

Distributed Applications

This scenario focuses on duplicating data to another environment for reading purposes, most predominantly on Azure SQL Database or Azure SQL Managed Instance. The possible migration paths are:

• Read replicas tutorial:

  • Read queries on replicas - Azure SQL Database & Azure SQL Managed Instance

• Always On availability groups tutorial:

  • Always On availability groups

• Database copy tutorial:

  • Copy a database - Azure SQL Database

Globally distributed applications

This scenario synchronizes data across different regions for reading purposes. Most used on Azure SQL Database.

• Azure Data Factory tutorials:

  • Azure Data Factory tutorials
  • Change data capture
  • Mapping data flows
  • Incrementally copy data from a source data store to a destination data store

• Readable active geo-replication tutorial:

  • Active geo-replication - Azure SQL Database

Other alternatives to consider

• Azure Functions tutorial:

  • Azure Functions Overview

• Fabric mirrored databases tutorials:

  • Microsoft Fabric mirrored databases from Azure SQL Database
  • Explore data in your mirrored database using Microsoft Fabric
  • Explore data in your mirrored database directly in OneLake

Migration by platform

Consider the following synchronization solutions by platform.

* SQL Data Sync does not support Azure SQL Managed Instance.

Related content

• Active geo-replication
• Azure Functions
• Always On availability groups
• Managed Instance link feature overview - Azure SQL Managed Instance
• Microsoft Fabric mirrored databases from Azure SQL Database