Issue when my Merge Publisher DB is Subscriber for Trans Replicati

Hi,
I have Database which is configured as a Merge Publisher , This database
has 3 Tables Employee,Dept and Country. All these 3 tables are repliated to
another database for high availability purpose using Merger Replication.
The Merge Publisher is also an Subscriber for another Transactional
Publication, where in only Country Table is being pulled.
My issue is When i add a new record in for a new country in the
Transactional Pulisher the data gets populated to my Merge Publisher but it
dosent get pushed to the Merge Subscriber automatically, i have to explisitly
run sp_addtabletocontents for the country table to get the new record pushed
to Merge Subscriber.
This has become an additional overhead , due to this am never sure that both
Merge Publisher and Subscriber have exact data.
Can some one provide the solution for this.
Regards
Pradeep
Please verify if the @.published_in_tran_pub bit is set for the articles
you can take a look at the sysmergearticles table for it
If you can enable it by specifying @.published_in_tran_pub='true' using
sp-addmergeartice or sp_changemergearticle
“This posting is provided "AS IS" with no warranties, and confers no rights.”
"PRADEEP M.M." wrote:

> Hi,
> I have Database which is configured as a Merge Publisher , This database
> has 3 Tables Employee,Dept and Country. All these 3 tables are repliated to
> another database for high availability purpose using Merger Replication.
> The Merge Publisher is also an Subscriber for another Transactional
> Publication, where in only Country Table is being pulled.
> My issue is When i add a new record in for a new country in the
> Transactional Pulisher the data gets populated to my Merge Publisher but it
> dosent get pushed to the Merge Subscriber automatically, i have to explisitly
> run sp_addtabletocontents for the country table to get the new record pushed
> to Merge Subscriber.
> This has become an additional overhead , due to this am never sure that both
> Merge Publisher and Subscriber have exact data.
> Can some one provide the solution for this.
> Regards
> Pradeep

Issue in Merge Replication

Hi Kevin,
I am setting up a SQL Server Database Merge Replication between Publisher
(P) & Subscriber (S) using EXCHANGE_TYPE '1' (Data only needs to be merged
from Subscriber to Publisher - Upload). Publisher priority is maximaum by
default.
However, I am facing this issue:
Under normal scenario, if a row of Data is changed at Subscriber, it is
updated at the Publisher since there is no change at Publisher.
But when same Row of Data in Publication (Table x) is updated at the
Publisher and also at the Subscriber (conflict situation), the row do not
particicipate in Replication when the agent runs and then it never
participates in Replication. Means the Data at Subscriber and Publisher
reamins different for that row. SQL Server do show any conflict that I can
resolve. Kindly help me to find out root cause and how to fix this!
Database : SQL Server 2000 SP3a
OS: Win2003 (No Service Pack)
Hi All,
I found the solution myself . Basically by changing the conflict resolver to
"Subscriber will always win the conflict" resolves the problem.
Cheers!
Vikas
"Vikas Kohli" wrote:

> Hi Kevin,
> I am setting up a SQL Server Database Merge Replication between Publisher
> (P) & Subscriber (S) using EXCHANGE_TYPE '1' (Data only needs to be merged
> from Subscriber to Publisher - Upload). Publisher priority is maximaum by
> default.
> However, I am facing this issue:
> Under normal scenario, if a row of Data is changed at Subscriber, it is
> updated at the Publisher since there is no change at Publisher.
> But when same Row of Data in Publication (Table x) is updated at the
> Publisher and also at the Subscriber (conflict situation), the row do not
> particicipate in Replication when the agent runs and then it never
> participates in Replication. Means the Data at Subscriber and Publisher
> reamins different for that row. SQL Server do show any conflict that I can
> resolve. Kindly help me to find out root cause and how to fix this!
> Database : SQL Server 2000 SP3a
> OS: Win2003 (No Service Pack)