In this article, I have depicted the essentials of utilizing “Triggers in SQL Server”. I trust this article has helped you in understanding this theme.


Triggers are unique kinds of stored procedures. which are naturally executes when an occasion happen in database.A trigger can allow the DML explanation against a table as it were.


  • CREATE TRIGGER <Schema_Name, sysname, Schema_Name>.<Trigger_Name, sysname, Trigger_Name>   
  •    ON  <Schema_Name, sysname, Schema_Name>.<Table_Name, sysname, Table_Name>   
  •    AFTER <Data_Modification_Statements, , INSERT,DELETE,UPDATE>  
  • AS   
  • BEGIN  
  •     — SET NOCOUNT ON added to prevent extra result sets from  
  •     — interfering with SELECT statements.  
  •     SET NOCOUNT ON;  
  •     — Insert statements for trigger here  
  • END  

Trigger is utilized to takes a magic tables.

What are Magic Tables?

Enchantment Tables are legitimate tables which are made naturally when DML tasks (“insert/update/delete”) are performed. These tables incidentally hold the information relying on the task and are available in triggers.

Read More

Different Types of SQL Server Triggers. 

  • Data Definition Language (DDL) triggers
  • Data Manipulation Language (DML) triggers
  • CLR triggers
  • Logon triggers

DDL Triggers

DDL Triggers execute on information definition dialect (DDL) occasions like CREATE, ALTER, and DROP articulations and certain framework put away methodology that perform DDL-like tasks.

Points: –

  1. It can beused just FOR/AFTER condition in DDL triggers not INSTEAD OF provision.
  2. It can be utilized to oversee manager undertakings, for example, evaluating and directing database tasks.
  3. It can be utilized to control activities performed on the server, and to review these tasks.

DML Triggers

DML Triggers execute on information control dialect (DML) occasion like INSERT, UPDATE, or DELETE proclamations on a table or view. These triggers fire when any substantial occasion is terminated, paying little heed to regardless of whether any table columns are influenced.

After trigger (utilizing FOR/AFTER CLAUSE)

It is fires after SQL Server complete the execution of the activity effectively that terminated it.

Instead of Trigger (utilizing INSTEAD OF CLAUSE)

It is fires before SQL Server begins the execution of the activity that let go it. This is varying from the AFTER trigger, which fires after the activity that made it fire. We can have an INSTEAD OF insert/update/delete trigger on a table that effectively executed yet does exclude the genuine insert/update/delete to the table.

CLR Triggers

It is exceptional sort of triggers that dependent on the CLR (Common Language Runtime) in .net system. CLR mix of triggers has been presented with SQL Server 2008 and takes into account triggers to be coded in one of .NET dialects like C#, Visual Basic and F#.

We coded the objects(like trigger) in the CLR that have overwhelming calculations or need references to objects outside the SQL Server. We can compose code for both DDL and DML triggers, utilizing an upheld CLR dialect like C#, Visual essential and F#. I will examine CLR trigger later.

Logon Triggers

Logon triggers are unique sort of trigger that fire when LOGON occasion of Sql Server is raised. This occasion is raised when a client session is being built up with Sql Server that is made after the validation stage completes, yet before the client session is really settled. Henceforth, all messages that we characterize in the trigger, for example, mistake messages, will be diverted to the SQL Server blunder log. Logon triggers don’t fire if confirmation comes up short. We can utilize these triggers to review and control server sessions, for example, to follow login movement or limit the quantity of sessions for a particular login.


I trust in the wake of perusing this piece your SQL triggers ideas will be solid. I might want to have criticism from my blog perusers. If it’s not too much trouble post your input, question or remarks about this article.