Sorts, Purposes, How They Work, and Extra

June 1, 2025

2

SQL triggers are like automated routines in a database that execute predefined actions when particular occasions like INSERT, UPDATE, or DELETE happen in a desk. This helps in automating knowledge updation and setting some guidelines in place. It retains the info clear and constant with out you having to jot down further code each single time. On this article, we’ll look into what precisely an SQL set off is and the way it works. We can even discover various kinds of SQL triggers by some examples and perceive how they’re used otherwise in MySQL, PostgreSQL, and SQL Server. By the tip, you’ll have a good suggestion about how and when to truly use triggers in a database setup.

What’s an SQL Set off?

A set off is like an computerized program that’s tied to a database desk, and it runs the SQL code mechanically when a selected occasion occurs, like inserting, updating or deleting a row. For instance, you need to use a set off to mechanically set a timestamp on when a brand new row is created, added or deleted, or new knowledge guidelines are utilized with out further code in your software. In easy phrases, we will say {that a} set off is a saved set of SQL statements that “fires” in response to desk occasions.

How Triggers Work in SQL

In MySQL, triggers are outlined with the CREATE TRIGGER assertion and are hooked up to a selected desk and occasion. Every set off is row-level, which means it runs as soon as for every row affected by the occasion. If you create a set off, you specify:

Timing: BEFORE or AFTER – whether or not the set off fires earlier than or after the occasion.
Occasion: INSERT, UPDATE, or DELETE -the operation that prompts the set off.
Desk: the identify of the desk it’s hooked up to.
Set off Physique: the SQL statements to execute, enclosed in BEGIN … END.

For instance, a BEFORE INSERT set off runs simply earlier than a brand new row is added to the desk, and an AFTER UPDATE set off runs proper after an present row is modified. MySQL requires the key phrase FOR EACH ROW in a set off, which makes it execute the set off physique for each row affected by the operation.

Inside a set off, you seek advice from the row knowledge utilizing the NEW and OLD aliases. In an INSERT set off, solely NEW.column is out there (the incoming knowledge). Equally, in a DELETE set off, solely OLD.column is out there (the info in regards to the row being deleted). Nonetheless, in an UPDATE set off, you need to use each: OLD.column refers back to the row’s values earlier than the replace, and NEW.column refers back to the values after the replace.

Let’s see set off SQL syntax:

CREATE TRIGGER trigger_name
BEFORE|AFTER DELETE ON table_name
FOR EACH ROW
BEGIN
-- SQL statements right here --
END;

That is the usual SQL kind. One factor which must be famous is that the set off our bodies usually embody a number of statements with semicolons; you need to normally change the SQL delimiter first, for instance to //, so the entire CREATE TRIGGER block is parsed appropriately.

Step-by-Step Instance of Creating Triggers

Now let’s see how we will create triggers in SQL.

Step 1: Put together a Desk

For this, let’s simply create a easy customers desk:

CREATE TABLE customers (
id INT AUTO_INCREMENT PRIMARY KEY,
username VARCHAR(50),
created_at DATETIME,
updated_at DATETIME
);

Step 2: Change the Delimiter

In SQL, you’ll be able to change the assertion delimiter so you’ll be able to write multi-statement triggers. For instance:

DELIMITER //

Step 3: Write the CREATE TRIGGER Assertion

As an example, we will create a set off that units the created_at column to the present time on insertion:

CREATE TRIGGER before_users_insert
BEFORE INSERT ON customers
FOR EACH ROW
BEGIN
IF NEW.created_at IS NULL THEN
SET NEW.created_at = NOW();
END IF;
END;
//

So, within the above code, the BEFORE INSERT ON customers means the set off fires earlier than every new row is inserted. The set off physique checks if NEW.created_at is null, and in that case, fills it with NOW(). This automates setting a timestamp.

After writing the set off, you’ll be able to restore the delimiter if desired in order that different codes can execute with none points.

DELIMITER ;

Step 4: Check the Set off

Now, whenever you insert with out specifying created_at, the set off will probably be set mechanically.

INSERT INTO customers (username) VALUES ('Alice');
SELECT * FROM customers;

And the created_at will probably be crammed mechanically with the present date/time. A set off can automate duties by organising default values.

Completely different Forms of Triggers

There are six kinds of SQL triggers for every desk:

BEFORE INSERT set off
BEFORE UPDATE Set off
BEFORE DELETE Set off
AFTER INSERT Set off
AFTER UPDATE Set off
AFTER DELETE Set off

Let’s find out about every of them by examples.

1. BEFORE INSERT Set off

This set off is activated earlier than a brand new row is inserted right into a desk. It’s generally used to validate or modify the info earlier than it’s saved.

Instance of set off SQL syntax for BEFORE INSERT:

DELIMITER //

CREATE TRIGGER before_insert_user
BEFORE INSERT ON customers
FOR EACH ROW
BEGIN
  SET NEW.created_at = NOW();
END;
// 

DELIMITER ;

This set off is mechanically set on the created_at timestamp to the present time earlier than a brand new consumer file is inserted.

2. BEFORE UPDATE Set off

This set off is executed earlier than an present row is up to date. This enables for validation or modification of information earlier than the replace happens.

Instance of set off SQL syntax for BEFORE UPDATE:

DELIMITER //

CREATE TRIGGER before_update_user
BEFORE UPDATE ON customers
FOR EACH ROW
BEGIN
  IF NEW.e-mail NOT LIKE '%@%' THEN
    SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = 'Invalid e-mail tackle';
  END IF;
END;
//
 
DELIMITER ;

This set off checks if the brand new e-mail tackle is legitimate earlier than updating the consumer file. If not, then it raises an error.

3. BEFORE DELETE Set off

That is executed earlier than a row is deleted. And will also be used for imposing referential integrity or stopping deletion underneath sure situations.

Instance of set off SQL syntax for BEFORE DELETE:

DELIMITER //

CREATE TRIGGER before_delete_order
BEFORE DELETE ON orders
FOR EACH ROW
BEGIN
  IF OLD.standing="Shipped" THEN
    SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = 'Can't delete shipped orders';
  END IF;
END;
//
 
DELIMITER ;

This set off prevents deletion of orders which have already been shipped.

4. AFTER INSERT Set off

This set off is executed after a brand new row is inserted and is commonly used for logging or updating associated tables.

Instance of set off SQL syntax for AFTER INSERT

DELIMITER //

CREATE TRIGGER after_insert_user
AFTER INSERT ON customers
FOR EACH ROW
BEGIN
  INSERT INTO user_logs(user_id, motion, log_time
  VALUES (NEW.id, 'Person created', NOW());
END;
//
 
DELIMITER ;

This set off logs the creation of a brand new consumer within the user_logs desk.

5. AFTER UPDATE Set off

This set off is executed after a row is up to date. And is helpful for auditing modifications or updating associated knowledge.

Instance of set off SQL syntax for AFTER UPDATE

DELIMITER //

CREATE TRIGGER after_update_user
AFTER UPDATE ON customers
FOR EACH ROW
BEGIN
  INSERT INTO user_logs(user_id, motion, log_time)
  VALUES (NEW.id, CONCAT('Person up to date: ', OLD.identify, ' to ', NEW.identify), NOW());
END;
//
 
DELIMITER ;

This set off logs the change in a consumer’s identify after an replace.

6. AFTER DELETE Set off

This set off is executed after a row is deleted. And is usually used for logging deletions or cleansing up associated knowledge.

Instance of set off SQL syntax for AFTER DELETE

DELIMITER //

CREATE TRIGGER after_delete_user
AFTER DELETE ON customers
FOR EACH ROW
BEGIN
  INSERT INTO user_logs(user_id, motion, log_time)
  VALUES (OLD.id, 'Person deleted', NOW());
END;
//
 
DELIMITER ;

This set off logs the deletion of a consumer within the user_log desk.

When and Why to Use Triggers

Triggers are highly effective whenever you need to automate issues that occur when the info modifications. Beneath are some use instances and benefits highlighting when and why you need to use SQL triggers.

Automation of Routine Duties: You possibly can automate or auto-fill or replace columns like timestamps, counters, or some calculated values with out writing any further code in your app. Like within the above instance, we’ve got used the created_at and updated_at fields mechanically.
Imposing Knowledge Integrity and Guidelines: Triggers may help you verify situations and even forestall invalid operations. As an example, a BEFORE_INSERT set off can cease a row if it breaks some guidelines by elevating an error. This makes positive that the info stays clear even when an error occurs.
Audit Logs and Monitoring: They will additionally assist you to file modifications mechanically. An AFTER DELETE set off can insert a file right into a log desk each time a row is deleted. This provides an audit path with out having to jot down separate scripts.
Sustaining Consistency Throughout A number of Tables: Generally, you need to have a scenario the place, when one desk is modified, you need the opposite desk to replace mechanically. Triggers can deal with these linked updates behind the scenes.

Efficiency Concerns and Limitations

You will need to run triggers with care. As triggers run quietly each time knowledge modifications, they could generally sluggish issues down or make debugging difficult, you probably have too many. Nonetheless, for issues like setting timestamps, checking inputs, or syncing different knowledge, triggers are actually helpful. They save time and likewise scale back foolish errors from writing the identical code time and again.

Listed below are some factors to think about earlier than deciding to make use of SQL triggers:

Hidden Logic: set off code is saved within the databases and runs mechanically, which might make the system’s behaviour much less clear. So, Builders would possibly neglect that the set off is altering knowledge behind the scenes. Due to this fact, it needs to be documented effectively.
No Transaction Management: You can not begin, commit or roll again a transaction inside a SQL set off. All set off actions happen inside the context of the unique assertion’s transaction. In different phrases, you’ll be able to’t commit a partial change in a set off and proceed the primary assertion.
Non-transactional Tables: Should you use a non-transactional engine and a set off error might happen. SQL can’t absolutely roll again. So some elements of the info would possibly change, and a few elements won’t, and this may make the info inconsistent.
Restricted Knowledge Operations: SQL limits triggers from executing sure statements. For instance, you can not carry out DDL or name a saved routine that returns a consequence set. Additionally, there are not any triggers on views in SQL.
No Recursion: SQL doesn’t permit recursion; it may’t carry on modifying the identical desk on which it’s outlined in a method that will trigger itself to fireplace once more instantly. So it’s advisable to keep away from designing triggers that loop by repeatedly updating the identical rows.

Comparability Desk for MySQL vs PostgreSQL vs SQL Server Triggers

Let’s now take a look at how triggers differ on completely different databases reminiscent of MySQL, PostgreSQL, and SQL Server.

Function	MySQL	PostgreSQL	SQL Server
Set off Syntax	Outlined inline in CREATE TRIGGER, written in SQL. All the time contains FOR EACH ROW.	CREATE TRIGGER … EXECUTE FUNCTION function_name(). Permits FOR EACH ROW FOR EACH STATEMENT.	CREATE TRIGGER with AFTER or INSTEAD OF. All the time statement-level. Makes use of BEGIN … END.
Granularity	Row-level solely (FOR EACH ROW).	Row-level (default) or statement-level.	Assertion-level solely.
Timing Choices	BEFORE, AFTER for INSERT, UPDATE, DELETE. No INSTEAD OF, no triggers on views.	BEFORE, AFTER, INSTEAD OF (on views).	AFTER, INSTEAD OF (views or to override actions).
Set off Firing	Fires as soon as per affected row.	Can hearth as soon as per row or as soon as per assertion.	Fires as soon as per assertion. Makes use of inserted and deleted digital tables.
Referencing Rows	Makes use of NEW.column and OLD.column.	Makes use of NEW and OLD inside set off capabilities.	Makes use of inserted and deleted digital tables. Should be a part of them to entry the modified rows.
Language Assist	Solely SQL (no dynamic SQL in triggers).	PL/pgSQL, PL/Python, others. Helps dynamic SQL, RETURN NEW/OLD.	T-SQL with full language help (transactions, TRY/CATCH, and many others.).
Capabilities	Easy. No dynamic SQL or procedures returning consequence units. BEFORE triggers can modify NEW.	Highly effective. Can abort or modify actions, return values, and use a number of languages.	Built-in with SQL Server options. Permits TRY/CATCH, transactions, and sophisticated logic.
Set off Limits	Earlier than v5.7.2: Only one BEFORE and 1 AFTER set off per desk per occasion (INSERT, UPDATE, DELETE). And after v5.2, you’ll be able to create a number of triggers for a similar occasion and timing. Use FOLLOWS or PRECEDES to regulate the order.	No enforced set off depend limits.	Permits as much as 16 triggers per desk.
Set off Ordering	Managed utilizing FOLLOWS / PRECEDES.	No native ordering of triggers.	No native ordering, however you’ll be able to handle logic inside triggers.
Error Dealing with	No TRY/CATCH. Errors abort the assertion. AFTER runs provided that BEFORE and the row motion succeed.	Makes use of EXCEPTION blocks in capabilities. Errors abort the assertion.	Helps TRY/CATCH. Set off errors abort the assertion.

Conclusion

Though SQL triggers would possibly really feel a bit difficult at first, you’ll absolutely perceive them and get to understand how useful they’re, when you get began. They run on their very own when one thing modifications in your tables, which saves time and makes positive the info continues to observe the foundations you set. Whether or not it’s logging modifications, stopping undesirable updates, or syncing data throughout tables, triggers are actually helpful in SQL. Simply make sure that to not overuse them and make too many triggers, as that may make issues messy and arduous to debug afterward. Maintain it easy, check them correctly, and you’re good to go.

Hello, I’m Janvi, a passionate knowledge science fanatic presently working at Analytics Vidhya. My journey into the world of information started with a deep curiosity about how we will extract significant insights from complicated datasets.