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

Registry manipulation from SQL

Registry Manupulation from SQL Server is pretty easy. There are 4 extended stored procedure in SQL Server 2000 for the purpose of manupulating the server registry. They are: 1) xp_regwrite 2) xp_regread 3) xp_regdeletekey 4) xp_regdeletevalue Let us see each one of them in detail! About xp_regwrite This extended stored procedure helps us to create data item in the (server’s) registry and we could also create a new key. Usage: We must specify the root key with the @rootkey parameter and an individual key with the @key parameter. Please note that if the key doesn’t exist (without any warnnig) it would be created in the registry. The @value_name parameter designates the data item and the @type the type of the data item. Valid data item types include REG_SZ and REG_DWORD . The last parameter is the @value parameter, which assigns a value to the data item. Let us now see an example which would add a new key called " TestKey ", and a new data item under it called TestKeyValue :

Screen scraping using XmlHttp and Vbscript ...

I wrote a small program for screen scraping any sites using XmlHttp object and VBScript. I know I haven't done any rocket science :) still I thought of sharing the code with you all. XmlHttp -- E x tensible M arkup L anguage H ypertext T ransfer P rotocol An advantage is that - the XmlHttp object queries the server and retrieve the latest information without reloading the page. Source code: < html > < head > < script language ="vbscript"> Dim objXmlHttp Set objXmlHttp = CreateObject("Msxml2.XMLHttp") Function ScreenScrapping() URL == "UR site URL comes here" objXmlHttp.Open "POST", url, False objXmlHttp.onreadystatechange = getref("HandleStateChange") objXmlHttp.Send End Function Function HandleStateChange() If (ObjXmlHttp.readyState = 4) Then msgbox "Screenscrapping completed .." divShowContent.innerHtml = objXmlHttp.responseText End If End Function </ script > < head > < body > &l

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