Insert Notifications, Update Notifications, and Delete Notifications use a combination of triggers and buffer tables to capture events that happen on specific tables in a database. You configure the triggers and buffer tables when you configure the notifications.

These types of notifications operate similarly, with the exception of the type of SQL operation (insert, update, or delete) that they monitor. The adapter creates the trigger and buffer table when you enable a notification. The buffer table, which you specified when you configured the notification, holds the data selected by the trigger. There are no special size constraints for the buffer tables. The trigger monitors the database table you specified when you configured the notification and inserts data into the buffer table. When you disable a notification, the adapter drops the trigger and buffer table.

When you enable a notification, the database trigger monitors the table and inserts the data into the buffer table. When Integration Server invokes the notification, it retrieves the rows of data from the buffer table, publishes each row in the notification's publishable document, and then removes this row from the buffer table.

After you enable these types of notifications, the trigger and buffer table remain in the database table when you:

In the meantime, the trigger continues to monitor the table and to insert data into the buffer table. Integration Server invokes the enabled notification when it restarts, or when it enables or reloads the package that contains this notification. For more information about how these types of notifications work, see Insert, Update, and Delete Notifications Transaction Processing.

For instructions for configuring this type of adapter notification, see Configuring InsertNotifications, Configuring UpdateNotifications, or Configuring DeleteNotifications.

For more details about the Integration Server publishable documents, see the Publish-Subscribe Developer’s Guide for your release.