Merge Replication: prevent CLR triggers from being replicated

• TK-484813

  SSC Journeyman

  Points: 98

  More actions

  January 17, 2014 at 7:40 am

  #302862

  Anyone know how to prevent CLR triggers from being included in replication schema during snapshot generation?

  We are using CLR triggers on our database for before/after auditing (Idera SQL Compliance Manager). Database is published for multiple devices using merge replication. When attempting to replicate, applying schema at the subscriber generates errors due to missing Assemblies.

  Using @Schema_options we can disable all triggers for each published table, but we still need the non-CLR triggers to be included.

  Any advice/assistance would be greatly appreciated.

  Thanks,

• palmeralex

  SSC Rookie

  Points: 46

  More actions

  May 15, 2015 at 3:44 am

  #1798127

  Hi

  We're had the same issue with merge replication and SCM. Did you resolve it?

  I'm thinking of setting the SQM triggers to NOT FOR REPLICATION.

  The current status of the triggers can be seen by SELECT * from sys.triggers against the appropriate database.

  From the you can individually ALTER TRIGGER to change the setting.

  Cheers

  Alex