pull subscription

Hello,

i have one publisher with one pull subscription. when i make any change in publisher, that change is propegated to subscriber, but when i make any change in subscription, the change is not reflected. i have tried a lot of options but no one worked. please help me.

Regards,can you give us more information? what happens to the data at hte subscriber, does it just sit there? In replication monitor, does it show any rows/changes being uploaded? Is this sql 2000 or 2005?|||Gregg,

Actually i am using MSDE 2000. I have one Global publication and one site publication. i have a database called Temp. Temp is subscriber of both publications. Keep in mind that Temp is pull subscriber of Global and push subscriber of Site. Now problem is all data updates in the global server are propegated to Temp and finally Site but any changes in Temp are not reflected throught Pull subscription to Global.

I hope now you can help me in what is the problem.

Regards,|||

So it looks like this is a republishing scenario. Can you tell me exactly, and in what order, the publications and subscriptions were created? It should have been created in the following order:

1. create publication Global

2. create subscription Temp

3. apply Global snapshot to Temp

4. create re-publishing publication Temp

5. create subscription Site

6. apply Temp publication to Site

If it wasn't created in this order, applying snapshot out of order can overwrite merge metadata used to sync with other publication. Is there a reason you're using a republishing scenario, as opposed to having just one publisher and two subscribers?

Regardless, let me know if this isn't the case.

|||Dear Greg,

i have tried a lot of combinitions and what you noted is one of them. with no one of combinitions i could not succeed. The thing which i need to have a system with syncronized data and the only thing that came in my mind was this model to make data syncronized between nodes.|||One more thing that i forgot to remind you is that, my system does not have 2 subscribers. my system has 2 publishers. ( Site is a publisher not subscriber )|||What is the reason for a republishing scenario? Is there a reason why Site cannot be a subscriber to Global?|||Greg,

Yes, Site has a lots of work stations that are connected to it through push replication and they don't have internet connectivity.

That is why i need to maintain a site with syncronized data and timely syncronization with global server.|||

Unless you have some filtering that's set up incorrectly, tearing down the topology and starting from scratch is the only way to get this to work, this means removing all of replication. Replication has to be set up in a cascading or top-down method.

- remove all subscriptions and publications from the DB

- disable publishing on the published databases and remove the DBs or tables from subscriber DBs (if possible)

- create publication at Global, create subscription at Temp (make sure this is a global subscriber). Set priority for this subscription to be 99

- synchronize the subscriptions

- create publication on Temp, create subscriptions at Site, and synchronize.

IF there's any other caveat that's missing, or if there's some non-default publication/article property that you're setting, then let me know if this still doesn't work.