Comments on: SQL SERVER - Disable All the Trigger of Current Database http://blog.sqlauthority.com/2008/08/19/sql-server-disable-all-the-trigger-of-current-database/ Notes of a SQL Server MVP and Database Administrator Wed, 07 Jan 2009 19:37:50 +0000 http://wordpress.org/?v=MU hourly 1 By: rohit http://blog.sqlauthority.com/2008/08/19/sql-server-disable-all-the-trigger-of-current-database/#comment-43181 rohit Tue, 23 Sep 2008 21:29:11 +0000 http://sqlauthority.wordpress.com/?p=854#comment-43181 How about using this sp_msforeachtable "ALTER TABLE ? DISABLE TRIGGER all" sp_msforeachtable "ALTER TABLE ? ENABLE TRIGGER all" How about using this
sp_msforeachtable “ALTER TABLE ? DISABLE TRIGGER all”
sp_msforeachtable “ALTER TABLE ? ENABLE TRIGGER all”

]]> By: Rama Krishna.K.S. http://blog.sqlauthority.com/2008/08/19/sql-server-disable-all-the-trigger-of-current-database/#comment-42849 Rama Krishna.K.S. Tue, 16 Sep 2008 10:08:54 +0000 http://sqlauthority.wordpress.com/?p=854#comment-42849 I think the above(DISABLE ALL TRIGGERS ON THE TABLE) can also be deone with ALTER TABLE statement also. I think the above(DISABLE ALL TRIGGERS ON THE TABLE) can also be deone with ALTER TABLE statement also.

]]> By: Simon Worth http://blog.sqlauthority.com/2008/08/19/sql-server-disable-all-the-trigger-of-current-database/#comment-41785 Simon Worth Tue, 19 Aug 2008 13:37:25 +0000 http://sqlauthority.wordpress.com/?p=854#comment-41785 In the cursor, you may want to use the system view "sys.Triggers" to get a list of triggers in the context of the current database rather than the outdated SQL 2000 style of using sysobjects. sysobjects is only for backward compatibility with 2000 and should be avoided on any new development. At the very least - if you did not want to use sys.triggers then you should be using sys.objects on SQL 2005 and 2008. If development is on a 2000 instance then sysobjects is the way to go in order to get a list of triggers. For 2005 and 2008 you could use SELECT QUOTENAME(OBJECT_NAME(parent_id)) AS tbName from sys.triggers But this does not take into account tables that exist within other schemas other than dbo. You will just receive an error if you run that code on triggers within other schemas. In the cursor, you may want to use the system view “sys.Triggers” to get a list of triggers in the context of the current database rather than the outdated SQL 2000 style of using sysobjects. sysobjects is only for backward compatibility with 2000 and should be avoided on any new development. At the very least - if you did not want to use sys.triggers then you should be using sys.objects on SQL 2005 and 2008.
If development is on a 2000 instance then sysobjects is the way to go in order to get a list of triggers.

For 2005 and 2008 you could use
SELECT QUOTENAME(OBJECT_NAME(parent_id)) AS tbName from sys.triggers

But this does not take into account tables that exist within other schemas other than dbo. You will just receive an error if you run that code on triggers within other schemas.

]]>