Monitor and recreate SQL triggers

Connectivity Studio can use SQL triggers in the database to detect table events for data synchronization. See also:

• Set up data synchronization - Table events - Message

• Set up data synchronization - Table events - Outbound web service action

This article explains how to monitor existing SQL triggers and how the recreate SQL triggers.

Monitor SQL triggers

For each table that uses SQL trigger-based data synchronization, on the SQL trigger page, a separate entry is shown per event type: Insert, Update, and Delete. You can review these entries, view the technical details of each trigger, and see where each trigger is used.

Steps

1. Click Connectivity studio > Setup > SQL trigger.

   Note

   You can also open the SQL trigger page from the Message page header or the Web service action page, in the Set up data synchronization section.

2. On the SQL trigger page, view each table and event type combination that has an SQL trigger defined.

3. Sub-task: View SQL trigger details.

   1. For a selected table and event type combination, you can view the details of the database trigger.
      Select a record, and click SQL triggers.

   2. Close the page.

4. Sub-task: View where a SQL trigger is used.

   1. For each SQL trigger, you can view which messages and web service actions use it.

      On the SQL trigger page, select a record.

   2. Click Where-used.

   3. Close the page.

Recreate SQL triggers

You can recreate SQL triggers to repair or refresh the triggers that Connectivity Studio uses to detect table events. Reasons to recreate SQL triggers can be:

• You get a new or changed project from version control or you import a project into a new or existing environment. The project can have a message or web service action with data synchronization setup, using table events of type SQL trigger.

• One or more SQL triggers are missing or orphaned, for example because a message or web service action was changed or deleted.

• You want SQL trigger maintenance to run unattended on a recurring schedule, for example on a large installation with many projects and triggers.

SQL triggers are recreated table by table. Each table is checked and processed independently, so an interruption or failure on one table doesn't affect the triggers of the other tables.

Steps

1. Click Connectivity studio > Periodic > Recreate all triggers.

   Note

   You can also recreate triggers from the SQL trigger page. In this case, you can recreate the SQL triggers for one or more selected table and event type records, instead of all triggers. If you do not select specific records, triggers are recreated for all records.

2. Sub-task: Decide whether to run the recreation directly or in the background.

   1. In the Batch processing field, select an option:

      • No: The triggers are recreated immediately.

      • Yes: The recreation is queued as a batch job. Also fill in the other fields. If Yes, also fill in the other fields.

   2. If desired, you can set up the recurrence for the batch job.

      Click Recurrence and fill in the fields as desired.

   3. Click OK.