Replication Chain Problem

Is it possible to setup a merge replication chain where you have a Head
Office (HO) which is a publisher to a Region Office (RO) subscriber which is
a publisher to a Store Office (SO) subscriber where the data travels both
directions fully? eg. HO<->RO<->SO.
From testing, it appears that if data is changed at the SO, then it only
gets merged to the RO, not the HO as well.
Do anyone know what needs to be done to get it also merged to the HO as well?
this should work. As long as all the downstream subscribers have a lower
priority than the upstream publisher/subscriber the data should move as you
desire. You might want to check to make sure that the missing data isn't
logged in the conflict tables.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Cheval" <Cheval@.discussions.microsoft.com> wrote in message
news:8D8A9DE5-B207-4CF2-997C-5BD65A3EDD01@.microsoft.com...
> Is it possible to setup a merge replication chain where you have a Head
> Office (HO) which is a publisher to a Region Office (RO) subscriber which
> is
> a publisher to a Store Office (SO) subscriber where the data travels both
> directions fully? eg. HO<->RO<->SO.
> From testing, it appears that if data is changed at the SO, then it only
> gets merged to the RO, not the HO as well.
> Do anyone know what needs to be done to get it also merged to the HO as
> well?
|||No issues. I've built these as deep as 16 levels with data flowing in both
directions.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Cheval" <Cheval@.discussions.microsoft.com> wrote in message
news:8D8A9DE5-B207-4CF2-997C-5BD65A3EDD01@.microsoft.com...
> Is it possible to setup a merge replication chain where you have a Head
> Office (HO) which is a publisher to a Region Office (RO) subscriber which
> is
> a publisher to a Store Office (SO) subscriber where the data travels both
> directions fully? eg. HO<->RO<->SO.
> From testing, it appears that if data is changed at the SO, then it only
> gets merged to the RO, not the HO as well.
> Do anyone know what needs to be done to get it also merged to the HO as
> well?