Re: A conflict issue, or something else...?
From: Paul Ibison (Paul.Ibison_at_Pygmalion.Com)
Date: 11/17/04
- Next message: Paul Ibison: "Re: SQL Failover Error Message"
- Previous message: Rand Boyd [MSFT]: "Re: A red X appears over the 'replicator monitor'"
- In reply to: Tony Toker: "Re: A conflict issue, or something else...?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 17 Nov 2004 19:45:25 -0000
Tony,
'Treat changes to the same column as a conflict is selected' shouldn't make
any difference as it appears as though you don't have a conflict. However
you do have filters. If the record change violates the filter, it'll get
overwritten. If this is not the case I can't see how this is possible :)
Merge has no sense of the interim values - just the guid of the changes row
is of relevance, so the latest value at the time of running the merge agent
is used. Have you checked the conflict table just in case?
I'd guess it's either a filter issue or a conflict, although with your
selected resolver and one subscriber it's difficult to see.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
- Next message: Paul Ibison: "Re: SQL Failover Error Message"
- Previous message: Rand Boyd [MSFT]: "Re: A red X appears over the 'replicator monitor'"
- In reply to: Tony Toker: "Re: A conflict issue, or something else...?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|