AFTER trigger execution in SQL

Introduction

An AFTER trigger runs right after a change happens in the database. It helps you do extra work automatically once data is added, changed, or removed.

You want to log changes after someone updates a record.

You need to update related tables after inserting new data.

You want to send notifications after deleting a record.

You want to check or enforce rules after data changes.

You want to keep audit trails automatically after data updates.

Syntax

SQL

CREATE TRIGGER trigger_name
AFTER INSERT OR UPDATE OR DELETE ON table_name
FOR EACH ROW
BEGIN
  -- SQL statements here
END;

AFTER triggers run only after the main action (insert, update, delete) completes successfully.

You can create separate triggers for INSERT, UPDATE, or DELETE events.

Examples

This trigger adds a log entry after a new customer is inserted.

SQL

CREATE TRIGGER after_insert_customer
AFTER INSERT ON customers
FOR EACH ROW
BEGIN
  INSERT INTO audit_log(action, description) VALUES ('INSERT', 'New customer added');
END;

This trigger logs when an order is deleted.

SQL

CREATE TRIGGER after_delete_order
AFTER DELETE ON orders
FOR EACH ROW
BEGIN
  INSERT INTO audit_log(action, description) VALUES ('DELETE', 'Order removed');
END;

Sample Program

This example creates two tables: employees and salary_changes. The AFTER UPDATE trigger records every salary change in salary_changes. When Alice's salary is updated, the trigger saves the old and new salary.

SQL

CREATE TABLE employees (
  id INT PRIMARY KEY,
  name VARCHAR(50),
  salary INT
);

CREATE TABLE salary_changes (
  emp_id INT,
  old_salary INT,
  new_salary INT,
  change_date DATETIME DEFAULT CURRENT_TIMESTAMP
);

CREATE TRIGGER after_salary_update
AFTER UPDATE ON employees
FOR EACH ROW
BEGIN
  INSERT INTO salary_changes(emp_id, old_salary, new_salary)
  VALUES (OLD.id, OLD.salary, NEW.salary);
END;

INSERT INTO employees VALUES (1, 'Alice', 5000);
UPDATE employees SET salary = 5500 WHERE id = 1;

SELECT * FROM salary_changes;

Important Notes

AFTER triggers cannot modify the table that fired them directly to avoid recursion.

Use AFTER triggers to ensure the main data change is successful before running extra actions.

Summary

AFTER triggers run after data changes like insert, update, or delete.

They help automate tasks like logging, notifications, or updating related data.

They only run if the main action succeeds, so they keep data consistent.

Practice

1. What is the main purpose of an AFTER trigger in SQL?

easy

A. To execute actions only after a successful data change like insert, update, or delete

B. To prevent data changes before they happen

C. To rollback transactions automatically

D. To create new tables after data insertion

Solution

1. Step 1: Understand the timing of AFTER triggers

   AFTER triggers run only after the main data change operation completes successfully.

2. Step 2: Identify the purpose of AFTER triggers

   They automate tasks like logging or updating related data after changes, ensuring consistency.

3. Final Answer:

   To execute actions only after a successful data change like insert, update, or delete -> Option A

4. Quick Check:

   AFTER trigger = post-change action [OK]

Hint: AFTER triggers run only after successful data changes [OK]

Common Mistakes:

• Confusing BEFORE and AFTER triggers
• Thinking AFTER triggers run before data changes
• Assuming AFTER triggers rollback transactions

2. Which of the following is the correct syntax to create an AFTER INSERT trigger in SQL?

easy

A. CREATE TRIGGER trg ON table_name AFTER DELETE BEGIN ... END;

B. CREATE TRIGGER trg AFTER INSERT ON table_name BEGIN ... END;

C. CREATE TRIGGER trg BEFORE INSERT ON table_name BEGIN ... END;

D. CREATE AFTER TRIGGER trg ON table_name INSERT BEGIN ... END;

Solution

1. Step 1: Recall standard AFTER trigger syntax

   The correct syntax starts with CREATE TRIGGER, followed by trigger name, timing (AFTER), event (INSERT), and table name.

2. Step 2: Check each option

   CREATE TRIGGER trg AFTER INSERT ON table_name BEGIN ... END; matches the correct syntax. Options A, B, and C have wrong order, timing, or event.

3. Final Answer:

   CREATE TRIGGER trg AFTER INSERT ON table_name BEGIN ... END; -> Option B

4. Quick Check:

   CREATE TRIGGER + AFTER + INSERT = correct syntax [OK]

Hint: AFTER triggers syntax: CREATE TRIGGER name AFTER event ON table [OK]

Common Mistakes:

• Mixing BEFORE and AFTER keywords
• Placing AFTER in wrong position
• Using DELETE event instead of INSERT

3. Given this trigger and table:

CREATE TABLE sales (id INT, amount INT);
CREATE TRIGGER trg AFTER INSERT ON sales
BEGIN
  INSERT INTO audit_log VALUES ('insert', NEW.id, NEW.amount);
END;

What happens when you run INSERT INTO sales VALUES (1, 100);?

medium

A. New rows are added to both sales and audit_log

B. A new row is added to audit_log only

C. A new row is added to sales only

D. No rows are added due to trigger error

Solution

1. Step 1: Understand the trigger action

   The AFTER INSERT trigger inserts a row into audit_log using the new sales row data.

2. Step 2: Analyze the insert command effect

   Inserting into sales triggers the AFTER INSERT, so both sales and audit_log get new rows.

3. Final Answer:

   New rows are added to both sales and audit_log -> Option A

4. Quick Check:

   AFTER INSERT triggers run after insert, adding audit_log row [OK]

Hint: AFTER INSERT triggers run after insert, affecting related tables [OK]

Common Mistakes:

• Thinking trigger replaces original insert
• Assuming trigger runs before insert
• Ignoring NEW keyword usage

4. You wrote this AFTER UPDATE trigger:

CREATE TRIGGER trg AFTER UPDATE ON employees
BEGIN
  UPDATE employees SET salary = salary * 1.1 WHERE id = NEW.id;
END;

What problem will occur when you update an employee's salary?

medium

A. Salary will not change

B. Trigger will not run at all

C. Syntax error prevents trigger creation

D. Infinite loop causing stack overflow

Solution

1. Step 1: Analyze trigger logic

   The trigger updates the same table it is triggered on, causing the trigger to fire again.

2. Step 2: Identify the effect of recursive updates

   This causes an infinite loop of updates, eventually causing stack overflow or error.

3. Final Answer:

   Infinite loop causing stack overflow -> Option D

4. Quick Check:

   Trigger updating same table without stop = infinite loop [OK]

Hint: Avoid triggers updating same table without condition to stop recursion [OK]

Common Mistakes:

• Not realizing trigger recursion
• Expecting trigger to run once only
• Ignoring NEW and OLD references

5. You want to log every DELETE from the orders table into orders_log only if the delete succeeds. Which is the best way to do this using an AFTER trigger?

hard

A. Create an AFTER INSERT trigger on orders_log that deletes from orders

B. Create a BEFORE DELETE trigger that inserts into orders_log before deletion

C. Create an AFTER DELETE trigger on orders that inserts deleted row info into orders_log

D. Create a trigger that deletes from orders_log after orders delete

Solution

1. Step 1: Understand timing for logging deletes

   AFTER DELETE triggers run only after the delete succeeds, ensuring accurate logging.

2. Step 2: Choose correct trigger type

   Creating an AFTER DELETE trigger on orders to insert into orders_log captures deleted data reliably.

3. Final Answer:

   Create an AFTER DELETE trigger on orders that inserts deleted row info into orders_log -> Option C

4. Quick Check:

   AFTER DELETE trigger logs only successful deletions [OK]

Hint: Use AFTER DELETE triggers to log only successful deletions [OK]

Common Mistakes:

• Using BEFORE DELETE triggers which may log failed deletes
• Confusing INSERT triggers with DELETE triggers
• Trying to delete from log table after orders delete