Triggered Action Statements - Teradata Vantage

Triggered action statements can be one or more of the SQL statements summarized in the following table:

Trigger Type	Valid Statements
AFTER	ABORT CALL DELETE INSERT INSERT … SELECT This applies only to standard INSERT … SELECT statements. INSERT … SELECT AND CONSUME statements are not valid as triggered action statements.	ROLLBACK Atomic Upsert UPDATE EXEC of macros containing any of the valid statements
BEFORE	ABORT EXEC of macros containing no data-changing statements	ROLLBACK SET clause (INSERT and UPDATE row triggers only).

You can also run UDFs and call stored procedures from within triggered action statements.

The general rules for the use of these statements in SQL also apply to their use as triggered action statements, with the following differences:

No CLIv2 response parcels are generated by the database after execution of the triggered action statements.
The triggered action statements report messages to the requesting user only for aborts and failures.
The execution of the triggered action statements is atomic, meaning that the SQL transaction cannot be explicitly terminated.
If the execution of such atomic SQL statement is unsuccessful, then the system cancels all the data or structural changes made by the statement.

The action of the triggering statement returns a single response, with the following information:

Statement	Rule
INSERT… SELECT	Direct references by this statement to the triggering table are treated as outer references.
Atomic Upsert	The condition must be on a primary index, whether unique or nonunique.