---
title: "Monitor and recreate SQL triggers"
slug: "monitor-and-recreate-sql-triggers"
description: "Learn to monitor and recreate SQL triggers in Connectivity Studio for effective data synchronization and event detection across your database tables."
tags: ["Connectivity Studio", "CS", "Task"]
status: "update"
updated: 2026-10-05T12:08:31Z
published: 2026-10-05T12:08:31Z
canonical: "docs.staedean.com/monitor-and-recreate-sql-triggers"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](/data-management/docs/set-up-data-synchronization-table-events-message)
- [Set up data synchronization - Table events - Outbound web service action](/data-management/docs/set-up-data-synchronization-table-events-outbound-web-service-action)

This article explains how to monitor existing SQL triggers and how to 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]
> **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 an 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 a data synchronization setup that uses 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 does not affect the triggers of the other tables.

### Steps

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

> [!NOTE]
> 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.
  2. If desired, you can set up a recurrence schedule for the batch job.

Click **Recurrence** and fill in the fields as desired.
  3. Click **OK**.

<style> p[data-block-id] {font-size:1rem;} ul li p[data-block-id] {margin-bottom: 0;} ul[data-type="taskList"] li div p[data-block-id] {margin-bottom: 0;} ol li p[data-block-id] {margin-bottom: 0;} table tbody th p[data-block-id] { margin-bottom: 0;} blockquote p[data-block-id] {margin-bottom: 0 !important;} &nbsp;p[data-block-id]:empty::after {content: "\00A0";} </style>

## Related

- [Set up data synchronization - Table events - Message](/set-up-data-synchronization-table-events-message.md)
- [Set up data synchronization - Table events - Outbound web service action](/set-up-data-synchronization-table-events-outbound-web-service-action.md)
- [Import configuration](/deployment-import-configuration.md)
- [Import configuration](/import-configuration.md)
- [Initialize project in environment](/initialize-project-in-environment.md)
- [Monitor data synchronization log](/monitor-data-synchronization-log-cs.md)
- [Troubleshooting integration](/connectivity-studio-operation-troubleshooting-integration.md)