sql server replication: Hi,

I keep reading that transactional replication doesn't handle conflicts. I
have also read that transactional replication with updatable subscriptions
does handls conflicts and that this resolution is configurable. Which is the
right answer? I am thinking of setting up replication to use transactional
between our 6 servers and merge between the Express clients (where all of the
updates occur and may well occur to the same data at the same time) and the
servers. I know that the data will be merged back to the servers with any
conflicts resolved but then what happens when that data is replicated between
the servers and a conflict arises?

Regards,

Transactional replication handles conflicts by stopping the distribution
agent and then you have to figure out what happened, go in and fix it and
then restart the agent.

Updateable subscriptions will log the conflict so you can view it in the
conflict viewer, but by default the publisher's change will win, or a
snapshot will be regenerated and redistributed.

With merge replication you have rich control over how the conflicts are
handled and you can roll them back and forth using the conflict viewer.

HTH

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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



[quoted text, click to view]