The script sp_add_trigger.sql (located in proddir/util directory, where proddir denotes SharePlex Product Directory) is used to modify triggers on the target database so that they do not fire on actions of the SharePlex user. The script will operate on all the triggers on the target database. At times, it may be necessary to undo the actions of the script. Some of the common scenario include:
Wrong Shareplex user specified when running the script
There is a role reversal and the target now acts as a source.
SharePlex schema has changed.
There may be many other scenarios that are not covered above.
There is a script sp_remove_trigger.sql also located in /proddir/util) which can be run to undo or nullify the changes made by the script sp_add_trigger.sql. The procedure for running sp_remove_trigger.sql is similar to that for running sp_add_trigger.sql. Please refer to SharePlex Reference Guide for details on running the script sp_add_trigger.sql. Essentially the script removes the "when" clause created with sp_add_trigger for the SharePlex user in question. However,the script should only be used if one is not going to replicate to those tables via the SharePlex user in question. If you do continue to replicate to those tables when the SharePlex user do not change, the triggers will fire when SharePlex posts data and this will result in out of sync.
