June 15, 2006 at 9:02 am
I have three mssql 2000 servers; the publisher locally, the distributor in the DMZ and the subscriber at another office outside our firewall. So:-
Publisher -> ||firewall1|| -> DMZ: Distributor -> || real world ||firewall2|| -> Subscriber
I have a snapshot publication working in this setup. I now want to create a merge publication for the part of the database updated by both offices. The snapshot files and pre/port scripts sit in an ftp site on the distributor.
Publisher and Subscriber have no contact whatsoever, totally blocked, zip nowt. Because of that I have to script the subscriptions manual, as opposed to using nice gui's in Enterprise Manager.
The problem I'm having is the merge Subscriber is failing as it is trying to contact the publisher. How should I be setting this up, so it just contacts the distribution server?
Arthur
June 19, 2006 at 5:23 am
Ok overcome this problem now. I was trying to use Pull Subscriptions before, so the agent was running on the subscriber. This is no good as the subscriber can't connect to the publisher.
For merge replication the distributor doesn't really do a great deal other than handle the initial snapshot files. Its the merge agent that get the subscriber and publisher talking that does all the hard work.
I solved this problem by opting for push subscriptions. Here the merge agent runs on the distrbutor, which of course is allowed access to the publisher (the only trusted box outside the firewall) and it can access the subscriber.
Don't know why I didn't consider push subscriptions before, I can now manage all the subscription from a single place and some of the merge processing if offloaded to the distribution server.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply