Skip to main content

Relation between Triggers and sp_dbcmptlevel

SQL Server 2000 allows multiple triggers to be created for each data modification event (Delete, Insert or Update). If we create a Insert trigger to a table which already has an insert trigger then both Insert triggers would be created.

The same doesn't hold good for SQL Server 6.5. In version 6.5 a table can have only one trigger for each data modification event. i.e., if we try to create an Insert trigger for a table which already has an Insert trigger then the latest trigger would replace the earlier created trigger.

Lets test and check that for ourself. Use the below code snippet to create a sample table for the purpose of understanding this artcile.

Table Structure:

Create Table testTrigger
(
Sno int Identity (1,1),
FirstName Varchar(25),
Age int
)

Create Insert triggers for this table:

Create Trigger trgTriggerOne on testTrigger
for Insert
As
Print 'Trigger trgTriggerOne is fired ...'
Go

Create Trigger trgTriggerTwo on testTrigger
for Insert
as
Print 'Trigger trgTriggerTwo is fired'
Go

Now let us insert a sample record and see what happens.

Insert into testTrigger values ('vadivel',29)

Both 'Trigger trgTriggerOne is fired ...' and 'Trigger trgTriggerTwo is fired' would be displayed. Before testing the same stuff in SQL Server 6.5 let us drop both the trigger here.

Drop trigger trgTriggerOne
Drop trigger trgTriggerTwo

Run the below code snippet to change the compatibility level to SQL Server 6.5

sp_dbcmptlevel testdb, 65

Now try and create two Insert trigger for the same table and see what happens.

Create Trigger trgTriggerOne65 on testTrigger
for Insert
As
Print 'Trigger trgTriggerOne65 is fired ...'
Go

Create Trigger trgTriggerTwo65 on testTrigger
for Insert
as
Print 'Trigger trgTriggerTwo65 is fired'
Go

No errors trigger has been created. Now let us try and insert a sample record to see what happens.

Insert into testTrigger values ('Vadivel', 29)

Only the message 'Trigger trgTriggerTwo65 is fired' would be displayed. Its because that trigger has overwritten the trigger trgTriggerOne65 while creation itself.

Clean Up:

Drop trigger trgTriggerTwo65
Drop table testTrigger

Change the compatibility level again to SQL Server 2000:

sp_dbcmptlevel testdb, 80

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