December 12, 2014 at 1:29 am
hi team..
i have created triggers in publisher database for one table...the triggers are showing under table--trigger folder..but these are not in subscriber.....under table--trigger folder
but the trigger actions are propagating to the subscriber...
I thought the triggers should not placed in subscriber ?? is it right
My thoughts...
..if triggers are placed in subscriber..if any insert/delete/update
operation happens the trigger will again fire in subscriber..so it should not be in subscriber ?
\Please advice....my thoughts are correct or not
December 12, 2014 at 2:39 am
Which flavour of replication? Merge? Transactional? Snapshot? P2P?
Also, if Merge or Transactional, is subscriber updateable (two-way or one-way replication)?
-- Gianluca Sartori
December 12, 2014 at 6:56 am
It is for Transactional Replication( wihtout updatable subscription)
December 18, 2014 at 1:07 am
Why do you need Triggers on the Subscriber database. It can cause Violation of Primary Key constraint error message while replicating the Data and the Replication procedure can halt.
With Thanks,
Satnam
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy