Data Transformation Engine Database Interface Designer Reference Guide

Chapter 9 - Database Triggers Database Triggers Overview
Database Interface Designer Reference Guide
131
The Database Interface Designer allows two different triggering actions during
event-based map execution:
♦ Table-based Triggering
♦ Row-based Triggering
Installation Requirements
Before you can take advantage of the database triggering functionality, either one
of two database-specific installation scripts must be run by a system administrator:
Note This is a one-time only operation except for a possible unexpected Event Server
shutdown. For more information about that scenario, refer to Handling Unexpected
Shutdowns.
♦ m4ora8.sql (for Oracle8)
♦ m4sqlsvr.sql (for Microsoft SQL Server 7.0)
Executing the respective script installs the database objects required for database
triggering:
♦ tables that track "watch" events
Four tables are added to your database. These are required for the triggering
functionality. For more information about these tables, refer to Tables Created
for Triggering.
♦ stored procedures that interface to the tables
♦ (for Microsoft SQL Server 7.0 only) extended stored procedures that contain
signaling logic
♦ (for Oracle8 only) public synonyms for tables and stored procedures
♦ (for Oracle8 only) sequences that generate unique trigger IDs
Note Certain privileges must be granted to the user running the database card triggers.
The specific details for this and additional information are presented at the
beginning of each script.