Replication with snap shot problems using triggers

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Sammy (Sammy_at_discussions.microsoft.com)
Date: 02/22/05


Date: Tue, 22 Feb 2005 01:35:05 -0800

Hi we are using transactional replication with the updating from subscriber
option.
So we have triggers on both databases the publisher and subscriber for
referential data Integrety. Now Occasionally we have to do a new snap shot
and we get errors saying cannot drop table as it is referenced by a trigger
on the subscriber DB. So we have to drop all triggers on the subscriber and
reapply them to get the snap shot to work does any one know of an easier way
to do this or is this the only way.

Thanks for any help or suggestions you might have

Sammy



Relevant Pages

  • Re: Transaction Updatable Replication between Servers (sql server 2005)
    ... You need to run sp_link_publication at the subscriber db side to create ... have trigger, but I don't see any for these articles/tables, that ... creating triggers for the related articles/tables. ... btw, none of these conflict ...
    (microsoft.public.sqlserver.replication)
  • Re: Transaction Updatable Replication between Servers (sql server 2005)
    ... You need to run sp_link_publication at the subscriber db side to create ... have trigger, but I don't see any for these articles/tables, that ... creating triggers for the related articles/tables. ...  btw, none of these conflict ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication with Triggers
    ... I have written the following triggers to pouplate the time stamp column.The ... Actually my requirement is pull the diffrential data from the subscriber and ... update to the subscriber database thru the replcation.Do we have any ... > Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: Missing Transactions - REPOSTED.
    ... your app is able to force the replication stored procedures to run ... I'd run profiler on the transactional subscriber to see how this is ... occurring and to confirm that the merge triggers aren't firing. ...
    (microsoft.public.sqlserver.replication)
  • Re: non-updateable merge subscription
    ... How about dropping the replication triggers of table on the subscriber? ... data flow to the publisher, and subscriber database permissions to prevent ... In SQL Server 2005 this is more elegantly ...
    (microsoft.public.sqlserver.replication)