SQL Server Performance Forum – Threads Archive
one way merge replicationHi We have one production site and we want to replicate that data to another database server. one of our DBA is suggesting for merge replication as he says we can do that in one way merge. and i am suggesting a transactional replication or snapshot replication.
and i have a doubt that we cant do a oneway update in merge replication
can anybody suggest whic is a better option to go ? as we dont have any problem regarding hardware ,network connectivity
pls help !
It referred by one of the MVP
By default, with merge replication you pass data in both directions: changes at a publisher are sent to a subscriber, and changes at a subscriber are sent back to a publisher. In some cases, you might want to use merge replication, but allow data to flow in only one direction. SQL Server does not provide an interface to do this. The merge job in SQL Server Agent simply calls this executable and passes command-line arguments to it. One of those optional command-line arguments is ExchangeType, which has three possible values: 1 specifies push, 2 specifies pull, and 3 specifies two-way (this is the default). If you set up merge replication with a push subscription and also set the ExchangeType to 1, then SQL Server will push data from the publisher to the subscriber, and not send data back from the subscriber to the publisher. We have used merge replication but with default approach of 2 way. But this 1 way approach looks better as compared to the other. But if you don’t have any issues with h/w, network and other resources, then its better to go with default process of Merge Replication.
You say if i have one Publishe and one subscriber and there is nothing updated on the subcriber
do u suggest a one way merge replication rather than a transactional or snapshot ?? can u explain me why as i am not convinced
it will be very helpul to me thaanx a looot!!