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)