As I discussed in my previous articles, now Microsoft SQL Server 2005 is integrated with Microsoft .Net Framework common language runtime (CLR), so we can use any .Net Framework language to create database objects. The CLR provides the execution environment for all the server side objects that are created using a .NET language. This means the database developers can now perform tasks that were impossible or difficult to achieve with T-SQL alone. Especially when working with large amounts of server code, developers can easily organize and maintain their code investments.

This article covers different types of triggers supported by Microsoft SQL Server 2005 with basic ideas about them with an example. At last describes the step-by-step approach to create a CLR trigger (a DML type).

What is Trigger?

A trigger is a Database object just like a stored procedure, or we can say it is a special kind of Stored procedure which fires after (/before) a specified language event executes. More specifically the object which is attached to a Table or View or Database schemas for tracking the operations on them. The main difference between a trigger and a stored procedure is that the former is attached to a table or view and is fired only when an INSERT, UPDATE, and/or DELETE occurs, while a stored procedure executes at any time when it is called.

For more details please visit : http://aspalliance.com/1273

Thanks,

Soyuj Kumar..

This article is related to my previous article CLR integration in SQL Server 2005. This contains a step-by-step method of using Visual Studio for creating CLR based database objects. This also explains the method for debugging the managed code for CLR integrated objects and explains the CLR integrated functions.

We all know how great T-SQL is for database code, but writing procedural code in T-SQL has always been difficult. It seems impossible when we need a stored procedure or two, requiring some array-operations, text-parsing or complex math operations. However, it is quite easy if our Server allows us to deploy C# or VB.NET code that is used within the Server process. In other words, if we need complex procedural code, we can write it as managed code.

With the Common Language Runtime (CLR) hosted in Microsoft SQL Server 2005(called CLR integration), we can write stored procedures, triggers, user- defined functions, user-defined types, and user-defined aggregates in managed code. Because managed code compiles to native code prior to execution, we can achieve significant performance increases in some scenarios. Thus SQL Server essentially acts as the operating system for the CLR when it is hosted inside SQL Server.........

Please visit for details : http://aspalliance.com/1081

Thanks,

Soyuj Kuamr...