Skip to main content

Creating a DML trigger using CLR in SQL Server 2005

In this article, we will take a look at the new CLR integration feature and learn how to create triggers in SQL Server using a managed code. We would create a simple DML delete trigger for a table and access the deleted value from our C# code.

Visual Studio .NET 2005

1. Open a C# -- Database project
2. Create a new trigger file into it.
3. The .NET class that will implement the functionalities of the trigger is given below just copy-paste it into the new file.

GetTriggerContext() :: Get reference to the current trigger context by invoking this method of the SqlContext class. This help us in fetching the data from the virtual table which would be created during a execution of a trigger.

using System;
using System.Data;
using System.Data.Sql;
using System.Data.SqlServer;
using System.Data.SqlTypes;

public partial class Triggers
{
// Enter existing table or view for the target and uncomment the attribute line
// [SqlTrigger (Name="SampleCLRTrigger", Target="EmployeeInfo", Event="FOR Delete")]
public static void SampleCLRTrigger()
{
SqlTriggerContext triggerContext = SqlContext.GetTriggerContext();
SqlPipe sqlPipe = SqlContext.GetPipe();
SqlCommand command = SqlContext.GetCommand();

if (triggerContext.TriggerAction == TriggerAction.Delete)
{
command.CommandText = "Select * from Deleted";
sqlPipe.Execute(command);
}
}
}

Build and compile the .NET class to create a .NET assembly out of it. In VS.NET 2005 it is as simple as Ctrl+Shift+B. The DLL would have been created in the BIN directory. From the properties of that DLL get to know the path of the created DLL.

SQL Server 2005

Then open SQL Server Management Studio and create a new query. Register the assembly in SQL Server using the below code snippet.

Create Assembly assTestCLRTrig
FROM 'C:\Documents and Settings\Administrator\My Documents\Visual Studio\Projects\SqlServerProject1\SqlServerProject1\bin\Debug\SqlServerProject1.dll'

Script to create a table for demo purpose:

Create table EmployeeInfo
(
EmpId int identity(1,1),
EmpName varchar(50),
EmpAddr varchar(100),
EmpContactNo varchar(20)
)

Insert a sample record

Insert into employeeinfo values ('vadi','address comes here','5201')

Script to create a trigger

Create trigger trgDeleteEmployeeInfo
On
EmployeeInfo
For Delete
As External Name
assTestCLRTrig.Triggers.SampleCLRTrigger

The syntax used above for External Name is "AssemblyName.NameOfTheClass.MethodName"

By default execution of the code in .NET framework is disable ... so just run the below two lines to enable it.

sp_configure 'clr enabled', 1
Reconfigure with override

Lets test our work:

Delete from employeeinfo where empid=1

It would display the record deleted in a tabular fashion. So far, we have seen the steps involved in creating the trigger and executing that trigger from Yukon .. hope it was useful to you!

Comments

Popular posts from this blog

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As"  ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul

AWS fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request

While using AWS and trying to copy a file from a S3 bucket to my EC2 instance ended up with this error message. Command Used: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ Error: fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request The error goes off if we add the region information to the command statement. I am using Asia Pacific (Mumbai) so used ap-south-1 as the region name. Modified Command: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ --region ap-south-1

[Non Tech] Want to know the recipe for Omelette :)

Fed up with Bread - Jam and Curd Rice, today i wanted to eat Omelette. Interesting part is I wanted to cook it myself :) So in the first picture you see all the items which are needed for preparing an Omelette. When I had a closer look at the eggs I see that almost all the eggs are broken. But believe me when I bought it couple of days back it was in perfect condition! I was wondering whether the eggs have become rotten or pretty old to consume! I tried taking an egg and break it but couldn't break it at all :) Since I have kept in the freezer all the eggs have frozen and looked like a iron ball :) After trying for few minutes of trying i removed the shell of the egg and then kept that iron ball :) into a bowl and placed it within Oven. I heated it for 1 minute and checked. It melted only to a limit. So i just set it for another 2 minutes and checked it later. It has melted but the part of the egg white has become a Omelette :( I didn't leave it there. I took the bowl out of