March 10, 2010 at 5:19 am
Hi,
I am trying to work out what is going on with our merge replication.
We have tables that are being merged replicated to another database. These tables are set as download only i.e. For this table, only changes made at the Publisher or a server subscription are replicated.
What we find however when we run the subscription the synchornisation uploads changes to publisher (only about 120 updates) as well as doing inserts, updates and delete changes to the subscriber.
Is this to be expected?
Thanks for your help, this has caused a big panic becuase we dont want any changes on the subscriber to be replicated to the publisher.
Many Thanks,
Oliver
March 10, 2010 at 5:30 am
March 10, 2010 at 5:32 am
Hey thanks for the reply.
What transactions are applied. I dont wish to have the subscriber sending any data back to the publisher?
Thanks,
Oliver
March 10, 2010 at 5:54 am
All transaction that changes articles in the merge replication (inserts/updates/deletes).
Any conflicts can be resolved within the replication monitor.
It sounds like the app that the subs connect to updates the data, therefore transactions will be passed to the publisher. Depending on what your requirements are it is possible that "Transactional Publication" would give you the required results (not updating the publisher).
If you have a mobile app, im pretty sure that the MS SQL Web service only works with merged replication (not 100% tho).
March 10, 2010 at 7:17 am
Hi,
I like the idea of merge replication becuase there is going to be big gaps between sync's. From what I read merge replication can work essentially one way by selecting the download only for the subscription articles.
however when this is set, there are still some updates going on to the publisher which is cause for concern.
many thanks for your comments.
Oliver
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply