sys.triggers (Transact-SQL)

 

Updated: June 10, 2016

THIS TOPIC APPLIES TO:yesSQL Server (starting with 2008)yesAzure SQL DatabasenoAzure SQL Data Warehouse noParallel Data Warehouse

Contains a row for each object that is a trigger, with a type of TR or TA. DML trigger names are schema-scoped and, therefore, are visible in sys.objects. DDL trigger names are scoped by the parent entity and are only visible in this view.

The parent_class and name columns uniquely identify the trigger in the database.

Column nameData typeDescription
namesysnameTrigger name. DML trigger names are schema-scoped. DDL trigger names are scoped with respect to the parent entity.
object_idintObject identification number. Is unique within a database.
parent_classtinyintClass of the parent of the trigger.

0 = Database, for the DDL triggers.

1 = Object or column for the DML triggers.
parent_class_descnvarchar(60)Description of the parent class of the trigger.

DATABASE

OBJECT_OR_COLUMN
parent_idintID of the parent of the trigger, as follows:

0 = Triggers that are database-parented triggers.

For DML triggers, this is the object_id of the table or view on which the DML trigger is defined.
typechar(2)Object type:

TA = Assembly (CLR) trigger

TR = SQL trigger
type_descnvarchar(60)Description of object type.

CLR_TRIGGER

SQL_TRIGGER
create_datedatetimeDate the trigger was created.
modify_datedatetimeDate the object was last modified by using an ALTER statement.
is_ms_shippedbitTrigger created on behalf of the user by an internal SQL Server component.
is_disabledbitTrigger is disabled.
is_not_for_replicationbitTrigger was created as NOT FOR REPLICATION.
is_instead_of_triggerbit1 = INSTEAD OF triggers

0 = AFTER triggers.

The visibility of the metadata in catalog views is limited to securables that a user either owns or on which the user has been granted some permission. For more information, see Metadata Visibility Configuration.

Security Catalog Views (Transact-SQL)
Catalog Views (Transact-SQL)

Community Additions

ADD
Show: