November 14, 2008 at 9:05 am
I've implemented merge replication (my only choice since I'm using web-synchronization) and would like one subscriber with bidirectional replication and the other with a "download-only to Subscriber, prohibit Subscriber changes".
I first tried to create an additional publication, set to download-only, but that fails with adding articles with "An article with a different subscriber_upload_options value already exists..."
I then attempted to modify the subscription's agent profile on the Publisher and changed ExchangeType to 2: that has had no effect.
I'm sure I can't be the first one that has a need to send read-only copies to some servers, and read-write to others, but I have not found any information on how to get it going.
Cheers!
November 17, 2008 at 5:54 am
charles (11/14/2008)
I've implemented merge replication (my only choice since I'm using web-synchronization) and would like one subscriber with bidirectional replication and the other with a "download-only to Subscriber, prohibit Subscriber changes".I first tried to create an additional publication, set to download-only, but that fails with adding articles with "An article with a different subscriber_upload_options value already exists..."
I then attempted to modify the subscription's agent profile on the Publisher and changed ExchangeType to 2: that has had no effect.
I'm sure I can't be the first one that has a need to send read-only copies to some servers, and read-write to others, but I have not found any information on how to get it going.
Cheers!
If you're using push subscriptions you should have on the publisher a job for each subscriber. Edit the jobstep for the subscriber in question by adding the parameter -ExchangeType 2. If the subscription is scheduled to run continously you need to stop the job and restart before the change becomes active.
In case of pull subscription the job will be at the subscriber.
[font="Verdana"]Markus Bohse[/font]
November 17, 2008 at 9:38 am
Thanks for your reply. I don't think web synchronization will work for push subscriptions. In my mind, one huge advantage of web sync is that you don't have to setup a VPN or open port 1433 to the outside world.
But if it doesn't support bidirectional and download-only (per subscriber) at the same time, I may be stuck with VPN and push.
BTW, I did try putting -ExchangeType 2 on the subscriber's merge agent when it was a pull subscription. Wasn't a continuous job but still didn't work for me. Academic, since allowing a subscriber the ability to change ExchangeType isn't an option for me anyway.
Cheers!
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply