Speak To Our Experts

How to work with Triggers and its Types in SQL?

Triggers

A trigger is a special method of stored procedure and it invokes automatically when an event starts in the database server. DML triggers execute when a user tries to modify data through a data manipulation language (DML) event. DML events are INSERT, UPDATE, or DELETE statements on a table or view.

After triggers

After triggers get fired after only with a condition when a modification action occurs. The INSERT, UPDATE and DELETE commands because of an after trigger gets fired after the execution of a complete statement.

Therefore, we need to use tblEmployee and tblEmployeeAudit tables for further examples as follows;

SQL Script to create tblEmployee table:

Finally, the table will look like as below;

SQL Script to create tblEmployeeAudit table:

Once a new Employee is added to the table in the database. Now, I want to retrieve the ID, date and time, the new employee is added to the tblEmployeeAudit table. The easiest way to get the same result by using an AFTER TRIGGER for INSERT event.

After Trigger for Insertion

Example for AFTER TRIGGER for INSERT event on the tblEmployee table as follows;

After this, we will get the id from inserted table name. So, the question arises, what is the role of an inserted table? An Inserted table defines a table which is mainly used by DML triggers. Once a time, you add a new row to the tblEmployee table, similarly, a row will generate the same copy in the inserted table, where only a trigger can access through the function. Further, you will not be able to access this table outside the context of the trigger function. The structure of the inserted table must be identical to the structure of the tblEmployee table.

So, if we execute the following INSERT command on tblEmployee. Simultaneously, after inserting the row data into the tblEmployee table, then the trigger gets fired as it gets invoked automatically, and the same row inserted into the tblEmployeeAudit table.

Insert into tblEmployee values (7,’Tan’, 2300, ‘Female’, 3)

when a row deletes records from the table tblEmployee.
Example for AFTER TRIGGER for DELETE event a tblEmployee table:

After Update Trigger

Triggers work with two organized tables, INSERTED and DELETED. Newly updated data stored in the inserted table and old specific data stored in the deleted table. After triggering for UPDATE event makes use of both inserted and deleted tables.

Furthermore, after the UPDATE command execution, the AFTER UPDATE trigger gets fired, and you see the contents of INSERTED and DELETED tables and stores the audit data in tblEmployeeAudit table.

Instead of Insert Trigger

As we well know that AFTER triggers get fired after the triggering action (INSERT, UPDATE or DELETE events), whereas, INSTEAD OF triggers get fired instead of the triggering action (INSERT, UPDATE or DELETE events). In addition, INSTEAD OF Insert triggers makes use for correctly update views that are based on multiple tables.

So, we start with the base demo on Employee and Department tables. So, first, let’s create these 2 tables.

SQL Script to create tblDepartment table:

So, we have our two required tables, let’s create a view which is based on these two tables, it will fetch the records of Employee Id, Name, Gender and DepartmentName columns. Therefore, the view is based on multiple tables.

Script to create a view:

Once you execute this line, Select * from vWEmployeeDetails, It will retrieve all the records from the table as follows;

So, let’s insert a single row into the view function, vWEmployeeDetails, by running the following query. At this moment, it will throw an error like “View or function vWEmployeeDetails is not updatable because the modification affects multiple base tables.”

Insert into vWEmployeeDetails values (7, ‘Valarie’, ‘Female’, ‘IT’)

Finally, we inserted a row above into a view which is based on multiple tables, it gives an error by default. Now, let’s have a look into this, how INSTEAD OF TRIGGERS give us help in this condition. Since we are facing an error, when we try to insert a single row into the view function, let’s make an INSTEAD OF INSERT trigger on the view vWEmployeeDetails.

Script to create INSTEAD OF INSERT trigger:

So, let’s execute the insertion query as follows:

Insert into vWEmployeeDetails values (7, ‘Valarie’, ‘Female’, ‘IT’)

The instead of trigger inserts records wisely, the data records into the tblEmployee table. Since we are inserting the data records into the inserted table, which contains the newly added row data, whereas the deleted table contains empty.

In the trigger action, we used Raiserror() function to show a custom error, once the DepartmentName provides in the insert query, that does not exist. It passes three parameters to the Raiserror() method. The first one parameter shows the error message, and the second parameter shows severity level. Severity level 16, which indicates general errors that only accessible for user correction. The final parameter shows the state parameter.

Instead of Update Trigger

An INSTEAD OF UPDATE triggers gets fired instead of an update event, that can be on a table or a view function. For example, let’s understand, an INSTEAD OF UPDATE trigger, and then when you try to make the update into the row within that view function or table, instead of the UPDATE, in this situation, the trigger get invoked automatically. Instead of update trigger based on multiple tables.

SQL Script to create tblDepartment table

So, we have our required two tables, let’s create a view which is based on these two tables, it will fetch the records of Employee Id, Name, Gender and DepartmentName columns which are based on multiple tables.

Script to create the view:

Once you execute this line, Select * from vWEmployeeDetails, It will retrieve all the records from the table as follows;

In above example, when we inserted a single row into the view table and got an error statement like- ‘View or function vWEmployeeDetails is not updatable because the modification affects multiple base tables.‘

So, let’s quickly update the view function, in addition, it affects both the tables, and if we face the same error statement. Then, the UPDATE command changes its column “Name” from the table tblEmployee and column “DeptName” from the table tblDepartment. So, when we run this query, we face the same error.

So, let’s do some change in the department of John from HR to IT. The UPDATE query runs only one table and that is the tblDepartment table. So, the query may succeed. But, there is a condition before executing the query, please make note that employees name JOHN and BEN both are in HR department.

Update vWEmployeeDetails
set DeptName = ‘IT’
where Id = 1

After execution of the query, now select all data records from the view function, and note that BEN’sDeptName has also changed to IT. We also change JOHN’s DeptName. So, the UPDATE command did not work as we expected. Why it happened, because of the UPDATE query command, updated column name DeptName from HR to the IT, in the tblDepartment table. For an update, we need to change the DeptId of JOHN from 3 to 1.

Incorrectly Updated View

In conclusion, if a view function is based on multiple tables, and if you ever update the view function in triggers, the UPDATE command may not always work as we expect. To resolve this situation, use Instead of Update trigger with a view function.

Before we create the trigger, let’s update the DeptName to HR for record with Id = 3.

Script to create INSTEAD OF UPDATE trigger:

The UPDATE query works as expected. The INSTEAD OF UPDATE trigger works correctly, and it changes john’s DepartmentId to 1 in the tblEmployee table.

So, let’s try to update in columns Name, Gender, and DeptName. An Update query works properly but it will not give you an error like – ‘View or function vWEmployeeDetails is not updatable because the modification affects multiple base tables.’

Hence, Update() function used in above example, which gives the result as “True”. It does not matter if you even update with the same value. This is why, I recommend the comparison of values with inserted and deleted tables, instead of using Update() function.

Instead of Delete Trigger

An INSTEAD OF DELETE trigger gets fired in the state of the DELETE event on a table or a view. Let’s understand with an example. Let’s assume, an INSTEAD OF DELETE trigger on a view or a table, and when you try to update a single row from that view or table, in the state of a real DELETE event, then the trigger automatically gets fired. INSTEAD OF DELETE TRIGGERS only used to delete data in terms of records from a view or a table, which is based on multiple tables.

SQL Script to create tblDepartment table

Since we now have the required tables, let’s create a view based on these tables. And, this view will return Employee Id, Name, Gender and DepartmentName columns. So, the view is based on multiple tables.

Script to create the view:

Once you execute this line, Select * from vWEmployeeDetails, It will retrieve all the records from the table as follows;

In above example, when we inserted a single row into the view table and got an error statement like- ‘View or function vWEmployeeDetails is not updatable because the modification affects multiple base tables.‘

Although, when we tried to update a view which is based on multiple tables, we faced the same error. To get the error, it will affect both the base tables. If the update query affects only one base table, we do not get the error, but the UPDATE query does not work properly if the “DeptName” column gets updated.

Now, let’s try to delete a row from the view, and we get the same error.

Note: The trigger tr_vWEmployeeDetails_InsteadOfDelete applicable in DELETED table. But Deleted table contains all the rows that we tried to DELETE from the view. So, we join the DELETED table with table tblEmployee to delete the unwanted rows. In such cases, Joins are much faster than the subqueries.

When you execute the following DELETE command, the row gets DELETED as expected from tblEmployee table

Delete from vWEmployeeDetails where Id = 1

A small difference among the triggers as given below;

DDL Triggers

DDL triggers is an operation that only gets fired in response to DDL events – CREATE, ALTER, and DROP (Table, Function, Index, Stored Procedure) these are the DDL triggers commands or we can say only DDL commands in SQL. System stored procedures, that perform DDL operations can also fire DDL triggers in the SQL commands.

Example – sp_rename system stored procedure.

Why the use of DDL Triggers.

Triggers used for improvement in data integrity and liability of the database.

Triggers maintain Audit file and table structure in the database.

Syntax for creating DDL trigger as follows;

CREATE TRIGGER [Trigger_Name]

ON [Scope (Server|Database)]

FOR [EventType1, EventType2, EventType3, …],

AS

BEGIN

— Trigger Body

END

DDL triggers can be created in a database server.

The following trigger will fire in response to CREATE_TABLE DDL event.

CREATE TRIGGER trMyFirstTrigger

ON Database

FOR CREATE_TABLE

AS

BEGIN

Print ‘New table created’

END

How To check trigger has been created or not?

Open your “Object Explorer window”, then further expand the “SampleDB” database by click on the plus symbol in near the folder name of SampleDB.

Then, expand Programmability folder.

Finally, expand Database Triggers folder. Please have a look at given image for reference as follows;

Please note: If you do not find the trigger that you just created, I suggest you refresh the Database Triggers folder.

When you execute the given code to just create the table, then the trigger automatically get fired and in return, it prints the message – New table created

Create Table Test (Id int)

The above trigger gets fired only for one DDL event which is “Create Table”. Furthermore, if you want that trigger to get fired with multiple events, let’s understand an example when you ever make your table in alter or drop commands, then separate the events by using a comma as follows.

ALTER TRIGGER trMyFirstTrigger

ON Database

FOR CREATE_TABLE, ALTER_TABLE, DROP_TABLE

AS

BEGIN

Print ‘A table has just been created, modified or deleted‘

END

So, now if you want to create, alter or drop a table, the trigger automatically gets fired and then you get the message like as – “A table has just been created, modified or deleted”.

The second DDL triggers perform some code to DDL events. So, let’s look at an example of how to save users from creating, altering or dropping tables. To get this you need to modify the trigger as given below.

To create, alter or drop a table, you either have to disable or delete the trigger. How do we get this, let’s understand the following checkpoints for disabling and enabling it.

How To disable trigger?

First, Open your object explorer window on the left corner of your window screen, then do Right-click on the trigger and select option “Disable” from the context menu folder.

Further, you can also disable the trigger by using the T-SQL commands like as follows DISABLE TRIGGER trMyFirstTrigger ON DATABASE

How To enable trigger?

First, Open your object explorer window on the left corner of your window screen, then do Right-click on the trigger and select option “Enable” from the context menu folder.

Further, you can also enable the trigger by using the T-SQL commands like as follows ENABLE TRIGGER trMyFirstTrigger ON DATABASE

How To Delete trigger?

First, Open your object explorer window on the left corner of your window screen, then do Right-click on the trigger and select option “Delete” from the context menu folder.

Further, you can also delete the trigger by using the T-SQL commands like as follows DROP TRIGGER trMyFirstTrigger ON DATABASE

System stored procedures that perform DDL operations can also fire DDL triggers. A given trigger gets fired once you rename a database object using “sp_rename” system stored procedure name. You can get your output by using this query.

In the given above code, that completely changes the name of the TestTable to NewTestTable. When you run this code, it will execute and it will get fire the trigger trRenameTable. For this reason, let’s have a look at given code as follows;

sp_rename ‘TestTable’, ‘NewTestTable’

In the given above code, that completely changes the name of the “Id” column in NewTestTable to NewId.When you run this code, it will execute and it will get fire the trigger trRenameTable. For this reason, let’s have a look at given code as follows;

sp_rename ‘NewTestTable.Id’ , ‘NewId’, ‘column’

Logon Triggers

Logon triggers is an operation that only gets executed automatically in response to a LOGON event. These triggers get fired only after the log finishes in the authentication phase but user session must be established before. Moreover, you will learn about why we use logon triggers.

Why we use for Logon triggers

Below are some meaningful cases in logon triggers

For tracking login activity in the database.

To restrict logins authority to SQL Server programs.

To restrict the number of sessions for a specific login.

Let’s understand with a Logon trigger example: Trigger sets limits of the maximum number of open connections with a user to 3.

As a result, trigger error message gets straight to the error log window. Then, execute the given command to read the error log.

Execute sp_readerrorlog

Conclusion

In this article, I described all the various types of Triggers like DDL, DML, and Logon. It is very useful to maintain the data integrity constraints in the database in the absence of SQL constraints keys (primary key and foreign key). Triggers is much useful feature of SQL/T-SQL and you can also use it in Oracle.

Moreover, Triggers control update format on which update allows the database. Triggers play a vital role in calling stored procedures. It is useful in the corporate sector to maintain the track of all the employees’ record which need to be changed like (update, deletion, and insertion) in the tables.

Faisal Malik is a professional Data Analyst and a true 'Entrepreneur'. He is working with Loginworks Softwares. He is a great follower and a huge fan of big "Entrepreneurs". Passionate about social network marketing business.

POPULAR CATEGORIES

Loginworks blogs and Insights provide cutting-edge perspectives on Big Data and analytics. Our ability to focus on business problems enables us to provide insights that are highly relevant to each industry.