Skip to main content

Basics of DDL Triggers in SQL Server 2005

This article would explain in detail about the new feature "DDL triggers" in SQL Server 2005. I have explained it with an example whose complete code snippet is also attached below.

Till SQL Server 2000 one can create DML triggers only. i.e., triggers which would fire on Insert, Update or Delete of a table or a view.

In SQL Server 2005 (Yukon) we can create triggers for DDL (Data definition Language) statements. i.e., we can write triggers which would react to CREATE, ALTER & DROP statements as well.

Syntax for creating DDL statements:

Create Trigger trigger_name
ON { ALL SERVER DATABASE }
[ WITH ENCRYPTION ]
{ FOR AFTER } { event_type event_group } [ ,...n ]
AS { sql_statement [ ...n ]
EXTERNAL NAME <> }
[ ; ]
::=
assembly_name.class_name[.method_name]

Major points which I thought might interest you are:

i) The ON clause in a DDL trigger refers to either the scope of the whole database server (ALL SERVER) or the current database (DATABASE).

ii) Event_type argument is used to define the event for which the trigger would fire.

iii) Inside a trigger, you can access information related to the event by calling EventData() function. EventData() function would return a value of type XML. The base XML schema returned by the eventdata() function depends on the scope and event type.

iv) On Database: Applies the scope of a DDL trigger to the current database. If specified, the trigger fires whenever event_type or event_group happens in the current database.

v) All Server : Applies the scope of a DDL trigger to the current server. If specified, the trigger fires whenever event_type or event_group happens anywhere in the current server.

Lets create a sample trigger which would fire when ever an "Alter table" statement is executed in our database.

Script to Create a sample table

Create table test
(
sno int identity,
firstname varchar(25)
)
Go

Code snippet to create a sample DDL trigger

Create trigger trgAlterTableForDatabase
On database
For alter_table As
Select eventdata()
Print 'You are not authorized to execute Alter Table statement in this database.'
Rollback
Go

Try and alter the table structure

Alter table test alter column firstname varchar(50)

Result:

On executing the above "Alter table" statement we would be welcomed with the below error message.

(1 row(s) affected)
You are not authorized to execute Alter Table statement in this database.
Msg 3609, Level 16, State 2, Line 1
Transaction ended in trigger. Batch has been aborted.

As said earlier eventdata() would return a XML string and in our case it would like this:


ALTER_TABLE
2005-08-26T07:46:48.880
58
VadivelDB
VadivelDB\Administrator
dbo
AdventureWorks
dbo
test
TABLE


Alter table test alter column firstname varchar(50)



Clean up

drop trigger trgAlterTableForDatabase on database
drop table test

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