If your DBMS supports
triggers, you can use them to enforce security authorizations or business-specific
security considerations. When and how triggers are executed is determined
by when the SQL statement is executed and how often the trigger is
executed. Triggers can be executed before an SQL statement is executed,
after an SQL statement is executed, or for each row of an SQL statement.
Also, triggers can be defined for DELETE, INSERT, and UPDATE statement
execution.
Enabling triggers can
provide more specific security for Delete, Insert, and Update operations.
SAS/ACCESS abides by all constraints and actions that are specified
by a trigger. For more information, see the documentation for your
DBMS.