January 17, 2006 at 7:08 pm
I have a rather convoluted question regarding whether subscriptions in Merge replication are Pull or Push by definition.
I am trouble-shooting an issue we are having with subscriptions disappearing. I am fairly confident it is due to the subscription expiration value. However this article on it says the clean up job only drops subscriptions that are push subscriptions (http://msdn2.microsoft.com/en-us/library/ms151778.aspx)
That would make sense in a Transactional repl setup. The publisher is either pushing to the subscriber or the subscriber is pulling form the publisher. But Merge repl is by definition bi-directional. In a push/pull set up the publisher is pushing changes at the publisher to the subscriber and pulling changes at the subscriber to the publisher. In pull/push it is oppsite. To my knowledge one server is always passive in either one of these config scenarios. So, every subscription is both pushing and pulling.
Can anyone offer any insight as to how to figure out if a subscription is push or pull in merge repl as far as SQL is concerned?
Thanks,
Chris
January 17, 2006 at 11:35 pm
The link to the article you specified does state that the meta data for both push and pull subscriptions are removed at the publisher by the 'Expired Subscription Clean-up Job'. This effectively removes the expired subscriptions (pull or pull)! The one thing that the 'Clean-up Job' cannot do is to clean up the pull subscriptions meta-data on the subscriber. you should do this by executing the appropriate drop stored proc.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply