Configure One Way Merge Replication for SQL Server

By:   |   Comments (5)   |   Related: > Replication


We are using SQL Server Merge replication and we have a need to setup a one way publication. We needed Data Manipulation Language (DML) changes on the publisher to get replicated to one of the subscribers, but not from that subscriber to the publisher.  In this tip we look at how this can be done.


Here is what the environment looks like.  DB1 is the publisher database and DB2 and DB3 are subscriber databases. We have Merge replication already configured on DB1 and DB2 and the data needs to go both ways.  Now we need replicate data from DB1 to DB3 and not from DB3 to DB1.


Steps to Configure one way Merge SQL Server Replication

Let's create a new SQL Server Merge publication called OneWay. Right click on Local Publications and select New Publication.

create a new SQL Server Merge publication called OneWay

Select the DB1 database.

Select the SQL Server Publisher Database

Add table and finish the wizard.

Add the tables to the Article in SQL Server Merge Replication

We need to add the subscriber to this publication, so right click on the publication and select New Subscription.

New SQL Server Subscription

Select the publication.

Select the Publication as Subscriber1

Specify where the Merge Agent will run.

Specifiy where the Merge Agent will run

Select the subscriber and subscription database and finish the wizard.

Select the subscriber and subscription database and finish the wizard

Now Launch Replication Monitor, by right clicking on Local Publications and selecting Launch Replication Monitor.

Launch Replication Monitor

Go to the All Subscriptions tab and select View Details.

All Subscriptions tab and select View Details

Go to the Merge Agent Job Properties.

Merge Agent Job Properties

In the job you need to add -ExchangeType 2 to the command as shown below.

add -Exchange Type 2 to the command

Restart the Merge SQL Server Agent Job and one way Merge replication should now be configured.

Next Steps

sql server categories

sql server webinars

subscribe to mssqltips

sql server tutorials

sql server white papers

next tip

About the author
MSSQLTips author Ranga Babu Ranga Babu is a SQL Server DBA with experience on performance tuning and high availability.

This author pledges the content of this article is based on professional experience and not AI generated.

View all my tips

Comments For This Article

Friday, June 28, 2024 - 7:52:19 AM - Cem Solumaz Back To Top (92351)
First of all, thank you very much for preparing such a beautiful portal and for your labour.

-DB1 is Publication, DB3 is Sunscribers. I want to use Data Diode and use unidirectional structure. Will UDP support when I want to use physical isolation of data and UDP in unidirectional transmission?
-How should I create a static route to show SQL DB3 in different vLAN and network?
Or do you have a suggestion?

Monday, October 2, 2023 - 2:47:03 PM - AnandGok Back To Top (91614)
hello, how can we configure the merge replication to listener in "always on"

Thursday, September 28, 2023 - 1:40:00 PM - Kosta Back To Top (91606)
Hi is it possible with this configuration to make changes at the subscriber database doing updates and on next replication job execution just to add the new records from publication to subscriber need to find replication solution that allows the subscriber to do its own data changes without going back to the publisher.

Friday, September 27, 2019 - 7:07:29 AM - Ranga Back To Top (82585)

Hi Bob,

you can replicate across instances.

if you need one way replication go for transactional.

Thursday, September 26, 2019 - 2:05:54 PM - bob Back To Top (82580)

Hi - does this one-way DB table replication rely on the  2 DBs being located in the same instance or can i replicate across instances

Thanks in advance


get free sql tips
agree to terms