Conflits with transactional replication -- sql server replication

manuel ralha
11/27/2006 3:14:01 AM

hello,
i need your help.
i have a transactional plublisher database, with updatable subscribers, and
used a queued update.
i have a lot of problems, first i need to use triggers in both siders, to
update 2 replicates tables, and now i have many conflicts, because they
update both records.
my first question is, i need to change my transactional replication, to
remove tow tables for replication, if i remove that, the transactional
replication reinitialize?
second question is, i need that a replicated table use triggers in both side
(publisher and subscriber), but not "not for replication" can i do this?

thanks,

Hilary Cotter
11/27/2006 10:38:25 AM

I think the majority of your problems can be solved by using the Not For
Replication attribute on your triggers.

Dropping articles will require a new snapshot to be generated or a
reinitailzation.

If you really need the triggers to fire on both side and to be fired by a
replication process you must make sure they do not modify the same data, or
if so, do an existence check to see if they really need to update/insert/ or
delete rows. I don't know what your trigger logic is, but to avoid the
conflicts it sounds like you need to re-write your trigger.

--
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

[quoted text, click to view]

sql server replication : Conflits with transactional replication