แก้ไข

แชร์ผ่าน

Replication to Azure SQL Database

  • บทความ

Applies to: Azure SQL Database

You can configure Azure SQL Database as the push subscriber in a one-way transactional or snapshot replication topology from SQL Server and Azure SQL Managed Instance.

Note

This article describes the use of transactional replication in Azure SQL Database. It is unrelated to active geo-replication, an Azure SQL Database feature that allows you to create complete readable replicas of individual databases.

Supported configurations

Versions

To successfully replicate to a database in Azure SQL Database, SQL Server publishers and distributors must be using (at least) one of the following versions:

Publishing to any Azure SQL Database from a SQL Server database is supported by the following versions of SQL Server:

Note

Attempting to configure replication using an unsupported version can result in error number MSSQL_REPL20084 (The process could not connect to Subscriber.) and MSSQL_REPL40532 (Cannot open server <name> requested by the login. The login failed.).

To use all the features of Azure SQL Database, you must be using the latest versions of SQL Server Management Studio (SSMS) and SQL Server Data Tools.

Types of replication

There are different types of replication:

Replication Azure SQL Database Azure SQL Managed Instance
Standard Transactional Yes (only as subscriber) Yes
Snapshot Yes (only as subscriber) Yes
Merge replication No No
Peer-to-peer No No
Bidirectional No Yes
Updatable subscriptions No No

Remarks

  • Only push subscriptions to Azure SQL Database are supported.
  • Replication can be configured by using SQL Server Management Studio or by executing Transact-SQL statements on the publisher. You cannot configure replication by using the Azure portal.
  • Replication can only use SQL Server authentication logins to connect to Azure SQL Database.
  • Replicated tables must have a primary key.
  • You must have an existing Azure subscription.
  • The Azure SQL Database subscriber can be in any region.
  • A single publication on SQL Server can support both Azure SQL Database and SQL Server (on-premises and SQL Server in an Azure virtual machine) subscribers.
  • Replication management, monitoring, and troubleshooting must be performed from SQL Server rather than Azure SQL Database.
  • Only @subscriber_type = 0 is supported in sp_addsubscription for SQL Database.
  • Azure SQL Database does not support bi-directional, immediate, updatable, or peer-to-peer replication.

Replication Architecture

Diagram shows the replication architecture with Azure SQL Database, which contains several subscriber clusters in different regions, and on-premises Azure virtual machines, which contains a Publisher, Logread executable, and distributor executables that connect to remote clusters.

Scenarios

Typical Replication Scenario

  1. Create a transactional replication publication on a SQL Server database.
  2. On SQL Server use the New Subscription Wizard or Transact-SQL statements to create a push to subscription to Azure SQL Database.
  3. With single and pooled databases in Azure SQL Database, the initial data set is a snapshot that is created by the Snapshot Agent and distributed and applied by the Distribution Agent. With a SQL Managed Instance publisher, you can also use a database backup to seed the Azure SQL Database subscriber.

Data migration scenario

  1. Use transactional replication to replicate data from a SQL Server database to Azure SQL Database.
  2. Redirect the client or middle-tier applications to update the database copy.
  3. Stop updating the SQL Server version of the table and remove the publication.

Limitations

Replication with the following options are not supported by Azure SQL Database:

  • Copy file groups association
  • Copy table partitioning schemes
  • Copy index partitioning schemes
  • Copy user defined statistics
  • Copy default bindings
  • Copy rule bindings
  • Copy fulltext indexes
  • Copy XML XSD
  • Copy XML indexes
  • Copy permissions
  • Copy spatial indexes
  • Copy filtered indexes
  • Copy data compression attribute
  • Copy sparse column attribute
  • Convert filestream to MAX data types
  • Convert hierarchyid to MAX data types
  • Convert spatial to MAX data types
  • Copy extended properties

Limitations to be determined

  • Copy collation
  • Execution in a serialized transaction of the SP

Examples

Create a publication and a push subscription. For more information, see:

  • Create a Publication
  • Create a Push Subscription by using the server name as the subscriber (for example N'azuresqldbdns.database.windows.net') and the Azure SQL Database name as the destination database (for example AdventureWorks).

See Also