Configure replication in an Azure SQL Database managed instance database

Transactional replication enables you to replicate data into an Azure SQL Database managed instance database from a SQL Server database or another instance database. You can also use transactional replication to push changes made in an instance database in Azure SQL Database managed instance to a SQL Server database, to a single database in Azure SQL Database, to a pooled database in an Azure SQL Database elastic pool. Transactional replication is in the public preview on Azure SQL Database managed instance. A managed instance can host publisher, distributor, and subscriber databases. See transactional replication configurations for available configurations.


Configuring a managed instance to function as a publisher or a distributor requires:

  • That the managed instance is not currently participating in a geo-replication relationship.


    Single databases and pooled databases in Azure SQL Database can only be subscribers.

  • All managed instances must be on the same vNet.

  • Connectivity uses SQL Authentication between replication participants.

  • An Azure Storage Account share for the replication working directory.

  • Port 445 (TCP outbound) needs to be open in the security rules of the managed instance subnet to access the Azure file share



  • Transactional and snapshot replication mix of SQL Server on-premises and managed instances in Azure SQL Database.
  • Subscribers can be in on-premises SQL Server databases, single databases in Azure SQL Database, or pooled databases in Azure SQL Database elastic pools.
  • One-way or bidirectional replication.

The following features are not supported in a managed instance in Azure SQL Database:

  • Updateable subscriptions.
  • Active geo replication.

Configure publishing and distribution example

  1. Create an Azure SQL Database managed instance in the portal.

  2. Create an Azure Storage Account for the working directory.

    Be sure to copy the storage keys. See View and copy storage access keys.

  3. Create an instance database for the publisher.

    In the example scripts below, replace <Publishing_DB> with the name of the instance database.

  4. Create a database user with SQL Authentication for the distributor. Use a secure password.

    In the example scripts below, use <SQL_USER> and <PASSWORD> with this SQL Server Account database user and password.

  5. Connect to the SQL Database Managed Instance.

  6. Run the following query to add the distributor and the distribution database.

    USE [master]​
    EXEC sp_adddistributor @distributor = @@ServerName​;
    EXEC sp_adddistributiondb @database = N'distribution'​;
  7. To configure a publisher to use a specified distribution database, update and run the following query.

    Replace <SQL_USER> and <PASSWORD> with the SQL Server Account and password.

    Replace \\<STORAGE_ACCOUNT>\<SHARE> with the value of your storage account.

    Replace <STORAGE_CONNECTION_STRING> with the connection string from the Access keys tab of your Microsoft Azure storage account.

    After you update the following query, run it.

    USE [master]​
    EXEC sp_adddistpublisher @publisher = @@ServerName,
                 @distribution_db = N'distribution',​
                 @security_mode = 0,
                 @login = N'<SQL_USER>',
                 @password = N'<PASSWORD>',
                 @working_directory = N'\\<STORAGE_ACCOUNT>\<SHARE>',
                 @storage_connection_string = N'<STORAGE_CONNECTION_STRING>';
  8. Configure the publisher for replication.

    In the following query, replace <Publishing_DB> with the name of your publisher database.

    Replace <Publication_Name> with the name for your publication.

    Replace <SQL_USER> and <PASSWORD> with the SQL Server Account and password.

    After you update the query, run it to create the publication.

    USE [<Publishing_DB>]​
    EXEC sp_replicationdboption @dbname = N'<Publishing_DB>',
                 @optname = N'publish',
                 @value = N'true'​;
    EXEC sp_addpublication @publication = N'<Publication_Name>',
                 @status = N'active';​
    EXEC sp_changelogreader_agent @publisher_security_mode = 0,
                 @publisher_login = N'<SQL_USER>',
                 @publisher_password = N'<PASSWORD>',
                 @job_login = N'<SQL_USER>',
                 @job_password = N'<PASSWORD>';
    EXEC sp_addpublication_snapshot @publication = N'<Publication_Name>',
                 @frequency_type = 1,​
                 @publisher_security_mode = 0,​
                 @publisher_login = N'<SQL_USER>',
                 @publisher_password = N'<PASSWORD>',
                 @job_login = N'<SQL_USER>',
                 @job_password = N'<PASSWORD>'
  9. Add the article, subscription, and push subscription agent.

    To add these objects, update the following script.

    • Replace <Object_Name> with the name of the publication object.
    • Replace <Object_Schema> with the name of the source schema.
    • Replace the other parameters in angle brackets <> to match the values in the previous scripts.
    EXEC sp_addarticle @publication = N'<Publication_Name>',
                 @type = N'logbased',
                 @article = N'<Object_Name>',
                 @source_object = N'<Object_Name>',
                 @source_owner = N'<Object_Schema>'​
    EXEC sp_addsubscription @publication = N'<Publication_Name>',​
                 @subscriber = @@ServerName,
                 @destination_db = N'<Subscribing_DB>',
                 @subscription_type = N'Push'​
    EXEC sp_addpushsubscription_agent @publication = N'<Publication_Name>',
                 @subscriber = @@ServerName,​
                 @subscriber_db = N'<Subscribing_DB>',
                 @subscriber_security_mode = 0,
                 @subscriber_login = N'<SQL_USER>',
                 @subscriber_password = N'<PASSWORD>',
                 @job_login = N'<SQL_USER>',
                 @job_password = N'<PASSWORD>'

See Also