Manualshelf

Data Transformation Engine Database Interface Designer Reference Guide

ManualsBrandsHP ManualsServerHP NonStop G-Series
131132133134135136137138139140
Chapter 9 - Database Triggers Database Triggers Overview
Database Interface Designer Reference Guide
136
Issues for Both Row- and Table-Based Triggering
The following list represents what is and is not supported in row- or table-based
triggering:
♦ The appropriate database must be used (Oracle 8 client or above and Oracle 8
server or above [for Windows and UNIX] or Microsoft SQL Server 7.0 and above
[for Windows only]).
♦ The respective SQL file (refer back to Installation Requirements) must be
installed and executed by your system administrator.
♦ SELECT statements containing Union or Intersect clauses are not supported.
♦ Case sensitivity for either column or table names is not supported.
♦ Only one Event Server per machine is supported.
Issues for Row-Based Triggering Only
The following list represents what is and is not supported in row-based triggering
only:
♦ For Microsoft SQL Server, each table defined in the query must contain either
an identity column or one numeric primary key.
♦ Queries that reference views or public synonyms are not supported.
Defining a Trigger Using a Database Source
Specify that you want a database source to be a trigger for a map when using a
database adapter that supports triggering and an Event Server.
To define a trigger
1 Use the Database Interface Designer to create an .mdq file containing the
desired query.
2 From the Trigger Specification dialog box in the Database Interface Designer,
define the conditions under which changes in database tables will trigger a map.
The trigger you define is associated with a query and is saved in the .mdq file.
For more information about this, refer to Defining a Trigger for a Query.
3 Use the Map Designer to create an executable map with an input card that uses
the .mdq file containing the trigger specification. For more information, refer to
the Map Designer Reference Guide.
Note Make sure that the input card corresponding to the database trigger is
set to integral mode, not burst.