Skip to main content

List all triggers in a database with its source code

Yesterday I saw a question in a forum asking for help in writing a script to list out all Triggers within a database. They also wanted to see the source code of each trigger.

Method 1: Which works in SQL Server 2000, SQL Server 2005 and SQL Server 2008.

But the problem with SYSCOMMENTS is it would truncate any text beyond 4000 characters. As the "Text" column which preserves the source code is declared as NVARCHAR(8000).

/*
Written By: Vadivel Mohanakrishnan
Date: Oct 10, 2011
URL: http://vadivel.blogspot.com
Purpose:  To list all triggers in the current database along with the actual text/source code. It also lists what of type of trigger it is. 


But for all future development we should avoid using SYSOBJECTS, SYSCOMMENTS as it might be removed in the future versions.
*/
SELECT
  SO2.Name AS [Table Name],
    SO1.name AS [Trigger Name],
  OBJECTPROPERTY( [so1].[id], 'ExecIsUpdateTrigger') AS [isUpdate],
    OBJECTPROPERTY( [so1].[id], 'ExecIsDeleteTrigger') AS [isDelete],
    OBJECTPROPERTY( [so1].[id], 'ExecIsInsertTrigger') AS [isInsert],
    OBJECTPROPERTY( [so1].[id], 'ExecIsAfterTrigger') AS [isAfter],
    OBJECTPROPERTY( [so1].[id], 'ExecIsInsteadOfTrigger') AS [isInsteadOf],
    OBJECTPROPERTY([so1].[id], 'ExecIsTriggerDisabled') AS [isDisabled],
    SC.Text AS [Source Code]
FROM
SYSOBJECTS SO1 
    Inner Join SYSOBJECTS SO2 On SO1.parent_obj = SO2.id
    Inner Join SYSCOMMENTS SC On SO1.id = SC.id
WHERE      
SO1.xtype = 'TR' And SO2.xtype = 'U'
ORDER BY 
SO2.Name, SO1.name
GO

Method 2: Works with SQL Server 2005 and above.

This method doesn't have the problem of text getting truncated beyond 4000 characters because the column "definition" of SYS.SQL_MODULES is declared as NVARCHAR(MAX).

/*
Written By: Vadivel Mohanakrishnan
Date: Oct 11, 2011
URL: http://vadivel.blogspot.com
Purpose: To list all triggers in the current database along with the actual text/source code. It also lists what of type of trigger it is.
*/
SELECT 
Object_name( TR.parent_id) AS [Table Name],
TR.[Name] AS [Trigger Name],
TR.is_disabled AS [isDisabled],
TR.is_Instead_of_trigger AS [isInsteadOfTrigger],
MO.definition AS [Source Code], 
TR.create_date AS [Created Date],
TR.modify_date AS [Modified Date]
FROM 
SYS.TRIGGERS TR INNER JOIN SYS.SQL_MODULES MO 
ON TR.Object_id = MO.Object_ID
WHERE 
TR.[Type] = 'TR' AND
TR.is_ms_shipped = 0 AND
TR.[parent_id] > 0
ORDER BY 
Object_name( TR.parent_id), TR.[Name]
GO

Labels:

Comments

George said…
You don't need to join to sql_modules because you can use the object_definition function instead.

Select *, object_definition(object_id) from sys.triggers
11:44 PM, October 19, 2011
Post a Comment

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...
2 comments
Read more

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
Post a Comment
Read more

[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 ...
8 comments
Read more