Getting Started › Procedures and Triggers › Overview › Summary

Summary

Procedures and triggers can provide a powerful tool for data and database administration and access. However, they should also be used with caution. Replacing a simple call from a CICS transaction with an execute procedure would probably cause a performance degradation. Similarly, using procedures to do simple security checks or to enforce access rules when standard system security products are available may not prove worthwhile. However, triggers and procedures can provide great value when used to enforce complex or highly sensitive business rules.

For detailed information about the SQL statements related to procedures and triggers, see the following:

• CREATE PROCEDURE (see CREATE PROCEDURE)
• CALL/EXECUTE PROCEDURE —without SET processing support (see CALL/EXECUTE PROCEDURE)
• DROP PROCEDURE (see DROP)
• CREATE TRIGGER/RULE—row level only (see CREATE TRIGGER/RULE)
• DROP TRIGGER/RULE (see DROP)

For examples showing the use of procedures and triggers, see Examples: Creating a Procedure and Example: Calling a Procedure.

Note: Some parts of CA Datacom SQL statement syntax are extensions to the ANSI SQL3 standard and are therefore rejected by SQL when used under ANSI and FIPS SQLMODEs.