Any DML which you need transferred from table A to B and C should be done
via replication articles as opposed to through a trigger. You will get
better performance that way.
"stephanie" <stephanie@discussions.microsoft.com> wrote in message
news:08EE39A6-D2AC-4248-BF69-535374E1C645@microsoft.com...
> What about if we need the trigger to update the tab B and tab C via
> replication update?
>
> "Hilary Cotter" wrote:
>
>> set the trigger to not for replication. This might fix your problem.
>>
>> --
>> 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 >>
>>
>>
>> "stephanie" <stephanie@discussions.microsoft.com> wrote in message
>> news:DCC4D79F-974B-4C70-9CE6-0E5C4885966D@microsoft.com...
>> >I found a problem in replication which we have 3 tables, namely tab A,
>> >tab
>> >B
>> > and tab C
>> >
>> > replication will apply on tab A and tab B
>> >
>> > and there is a trigger on tab A and tab B, whenever insert/update on
>> > tab A
>> > it fires trigger to update tab b
>> >
>> > whenever insert/update on tab B it fires trigger to update tab C
>> >
>> > And I found the replication error from tab A on updating tab C. If I
>> > manually insert the rowin tab A, it works fine.....
>> >
>> > Any advise? Thanks in advance!
>> >
>>
>>
>>