[Solved] Why is it important to use FOR EACH ROW instead of FOR EACH STATEMENT in audit logging triggers? — Ans: FOR EACH ROW logs every individual row change, ensuring detailed audit records | SQL

SQL - Triggers

Why is it important to use FOR EACH ROW instead of FOR EACH STATEMENT in audit logging triggers?

AFOR EACH STATEMENT runs the trigger multiple times per row, causing duplicates

BFOR EACH ROW triggers cannot access OLD or NEW values

CFOR EACH ROW logs every individual row change, ensuring detailed audit records

DFOR EACH STATEMENT triggers are faster and preferred for audit logging

Step-by-Step Solution

Solution:

Step 1: Understand difference between FOR EACH ROW and FOR EACH STATEMENT
FOR EACH ROW runs once per affected row; FOR EACH STATEMENT runs once per SQL statement.
Step 2: Identify audit logging needs
Audit logging requires detailed info per row change, so FOR EACH ROW is necessary.
Final Answer:
FOR EACH ROW logs every individual row change, ensuring detailed audit records -> Option C
Quick Check:
Detailed audit needs FOR EACH ROW triggers = FOR EACH ROW logs every individual row change, ensuring detailed audit records [OK]

Quick Trick: Use FOR EACH ROW for detailed audit logs per row change [OK]

Common Mistakes:

Master "Triggers" in SQL

9 interactive learning modes - each teaches the same concept differently

More SQL Quizzes

Why is it important to use FOR EACH ROW instead of FOR EACH STATEMENT in audit logging triggers?