MS SQL Training (32 Blogs) Become a Certified Professional
AWS Global Infrastructure


Topics Covered
  • Cassandra (14 Blogs)
  • MongoDB Dev and Admin (15 Blogs)
  • MySQL (30 Blogs)
  • SQL Essentials Training and Certification (4 Blogs)

Triggers in SQL – Learn With Examples

Last updated on Jun 26,2024 120.2K Views

In the process of learning and sharing knowledge of new technology. In the process of learning and sharing knowledge of new technology.
17 / 37 Blog from Introduction to SQL

A trigger in SQL is a procedural code that is automatically executed in response to certain events on a specified table. It is important to understand how these small codes make such a huge difference in database performance.  In this article, you will learn how to implement triggers along with examples.

The following topics will be covered in this article:

What is a Trigger?

Triggers in SQL are concise snippets of code that automatically execute when specific events occur on a table. These triggers play a vital role in maintaining data integrity, ensuring the accuracy and consistency of information. Similar to their real-world counterparts, SQL triggers act as a safeguard, responding to events and safeguarding data integrity. For example, when the gun trigger is pulled a bullet is fired. We all know this, but how this is related to Triggers in SQL? To understand this let’s consider a hypothetical situation.

Trigger - Triggers in SQL - Edureka

John is the marketing officer in a company. When a new customer data is entered into the company’s database he has to send the welcome message to each new customer. If it is one or two customers John can do it manually, but what if the count is more than a thousand? Well in such scenario triggers come in handy. 

Thus, now John can easily create a trigger which will automatically send a welcome email to the new customers once their data is entered into the database. So I hope you are clear with the introduction of Triggers in SQL.

Always remember that there cannot be two triggers with similar action time and event for one table. For example, we cannot have two BEFORE UPDATE triggers for a table. But we can have a BEFORE UPDATE and a BEFORE INSERT trigger, or a BEFORE UPDATE and an AFTER UPDATE trigger.


Before we dive further into the fundamentals of triggers I would suggest you to understand the concepts of  SQL Basics and Normalization so that you get a better grip on Triggers in SQL.

Syntax of Trigger

Lets now look at the syntax of a trigger.

Create Trigger Trigger_Name
(Before | After)  [ Insert | Update | Delete]
on [Table_Name]
[ for each row | for each column ]
[ trigger_body ]

Now let me break down this syntax and explain each and every part in detail.

  • Create Trigger
    These two keywords are used to specify that a trigger block is going to be declared. 
  • Trigger_Name
    It specifies the name of the trigger. Trigger name has to be unique and shouldn’t repeat.
  • ( Before | After )
    This specifies when the trigger will be executed. It tells us the time at which the trigger is initiated, i.e, either before the ongoing event or after.
  • Before Triggers are used to update or validate record values before they’re saved to the database. 
  • After Triggers are used to access field values that are set by the system and to effect changes in other records. The records that activate the after trigger are read-only. We cannot use After trigger if we want to update a record because it will lead to read-only error.
  •  [ Insert | Update | Delete ]
    These are the DML operations and we can use either of them in a given trigger.
  • on [ Table_Name ]
     We need to mention the table name on which the trigger is being applied. Don’t forget to use
    on keyword and also make sure the selected table is present in the database.
  • [ for each row | for each column ] 
    1.   Row-level trigger gets executed before or after any column value of a row changes
    2.   Column Level Trigger gets executed before or after the specified column changes
  • [ trigger_body]
     It consists of queries that need to be executed when the trigger is called.

So this was all about a simple trigger. But we can also create a nested trigger that can do multi-process. Also handling it and terminating it at the right time is very important. If we don’t end the trigger properly it may lead to an infinite loop.

You might be wondering in which scenario we can use the nested trigger. Rather than giving you a tailored answer let me share a scenario with you, which will help you in understanding the nested trigger in a better way. Continuing from the earlier scenario, John sent an email for every new customer that was added to the company’s database. Now, what if he wishes to keep track of the number of customers to whom the email was sent? Now John needs to create a nested trigger to keep the track of the count along with sending an email.

So that was all about the syntax of triggers, lets now try to implement an example of triggers in SQL.

Examples of Triggers in SQL

In the below trigger, we are trying to calculate the percentage of the student as soon as his details are updated to the database.

CREATE TRIGGER sample_trigger
before INSERT
ON student
SET = new.marks/6;

Here the “NEW” keyword refers to the row that is getting affected.

Operations in Triggers

We can perform many operations using triggers. Some may be simple and some may be a little complex, but once if we go through the query its easy to understand.

  • DROP A Trigger
DROP TRIGGER trigger name;
  • Display A Trigger 

The below code will display all the triggers that are present.


The below code will display all the triggers that are present in a particular database.

IN database_name;



In the above example, all the triggers that are present in the database named Edureka will be displayed.

We also look at some major variants of the triggers that is Before insert and After insert. We have already seen a trigger in the example. But with the help of the table lets see how exactly this works.

As we have already understood how to create a trigger, now let’s understand the two variants of the trigger those are Before insert and After insert. in order to implement them, let’s create a student table with various columns as shown below:

FName VARCHAR(20),
LName VARCHAR(20),
Address VARCHAR(30),
City VARCHAR(15),
Marks INT,

Now if we execute this query we get the following table.

Tables - Triggers in SQL - Edureka

Let’s try to use the first variant i.e, Before Insert

before INSERT 
ON student
SET new.marks = new.marks+100;

Here when we insert data into the student table automatically the trigger will be invoked. The trigger will add 100 to the marks column into the student column.

Now let’s use the second variant i.e, After Insert

To use this variant we need one more table i.e, Percentage where the trigger will store the results. Use the below code to create the Percentage Table.

create table Final_mark(
per int );

Now let us use the after insert trigger

after insert 
ON student
insert into Final_mark values(new.marks);

Here when we insert data to the table, total_mark trigger will store the result in the Final_mark table.

Find out our MS SQL Course in Top Cities

SQL Training in BangaloreSQL Course in Pune
SQL Training in ChennaiSQL Course in Mumbai
SQL Training in hyderabadSQL Course in Kolkata

That was all about the operation on triggers, lets now move ahead and look at its advantages and disadvantages.

Advantages and Disadvantages of Triggers


  • Forcing security approvals on the table that are present in the database
  • Triggers provide another way to check the integrity of data
  • Counteracting invalid exchanges
  • Triggers handle errors from the database layer
  • Normally triggers can be useful for inspecting the data changes in tables
  • Triggers give an alternative way to run scheduled tasks. Using triggers, we don’t have to wait for the scheduled events to run because the triggers are invoked automatically before or after a change is made to the data in a table


  • Triggers can only provide extended validations, i.e,  not all kind validations. For simple validations, you can use the NOT NULL, UNIQUE, CHECK and FOREIGN KEY constraints
  • Triggers may increase the overhead of the database
  • Triggers can be difficult to troubleshoot because they execute automatically in the database, which may not invisible to the client applications

This brings us to the end of this Triggers in SQL article. I hope you understood the concepts of Triggers.

Learn about

How to insert date in SQL

How to Change Column Name in SQL?

If you wish to learn more about MySQL and get to know this open-source relational database, then check out our MySQL DBA Certification Training which comes with instructor-led live training and real-life project experience. This SQL Course will help you understand MySQL in-depth and help you achieve mastery over the subject.

Got a question for us? Please mention it in the comments section of this Triggers in SQL and we will get back to you.

Upcoming Batches For Microsoft SQL Server Certification Training Course
Course NameDateDetails
Microsoft SQL Server Certification Training Course

Class Starts on 3rd August,2024

3rd August

SAT&SUN (Weekend Batch)
View Details

Join the discussion

Browse Categories

webinar_success Thank you for registering Join Edureka Meetup community for 100+ Free Webinars each month JOIN MEETUP GROUP

Subscribe to our Newsletter, and get personalized recommendations.

image not found!
image not found!

Triggers in SQL – Learn With Examples