About table triggers

Table-based replication is driven by table triggers. Mongoose tables included in the category for a replication rule have special auto-generated replication triggers in addition to their standard application triggers.

After you configure replication operations, you must regenerate the table triggers. This causes the toolset to regenerate the replication triggers associated with the tables to be replicated. It first drops all existing replication trigger code for the local database, and then recreates the replication triggers based on the updated information in the Replication Categories and Replication Rules forms.

Note: Regenerating the triggers should be done at each database. System administrators should do this only when no other users are connected to the database.

Trigger code is not generated for table replication objects that are actually views in this local source site, or in the target site. For more information, see the topics concerned with shared tables.

Replication triggers are created only for tables associated with replication categories that use them and where rules exist that contain those categories. (Triggers are generated even if the rules are currently disabled.) These are the replication triggers for each table:

  • TableNameIupReplicate: This trigger handles INSERT and UPDATE operations.
  • TableNameInsert: This trigger handles INSERTs into other sites in the same database.
  • TableNameDelReplicate: This trigger handles DELETE operations.