Performance Issues and Guidelines with Using Triggers | Teradata Vantage - Performance Issues for Triggers - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-07-11
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1184
lifecycle
latest
Product Category
Teradata Vantage™

Triggers are active database objects. The actions of creating triggers on tables and then executing them involve several system resource issues.

Application designers must evaluate the relative advantages of triggers and the possible performance impact while defining them. For example, a row trigger can complete a much larger amount of work than is done in the triggering statement, which is an SQL DML statement.

There is no limit on the number of rows that can be changed by row triggers or statement triggers. For example:

THIS type of triggered action … RESULTS in …
INSERT adding one row to a table.
INSERT... SELECT adding many rows to a table.
UPDATE updating one or multiple rows.

In many instances, the actions carried out by triggers are sufficiently useful that their use is justified even after the resulting impact on system performance is taken into consideration.