Authorities and privileges for trigger tasks

Task	Authorities and privileges
To add, change, or delete a comment on a trigger	You must be the creator of the trigger, or you must have one of the following authorizations: SYSADM authority DBADM authority on the database in which the trigger is stored The ALTERIN privilege on the schema to which the trigger belongs
To create a trigger	You need one of the following forms of authorization: SYSADM authority DBADM authority on the database in which the trigger will be created A set of privileges: ALTER privilege on the table on which you're defining the trigger. SELECT privilege on this table, if you define any correlation names or temporary tables. SELECT privilege on any table or view referenced in your coding for the action that you want your trigger to invoke. Necessary privileges on SQL statements specified in this coding. For example, to include an UPDATE statement in the coding, you need SYSADM authority, DBADM authority, or a privilege, such as CONTROL, on each table or view that the statement applies to.
To assign the trigger to an existing schema	You need the CREATEIN privilege on that schema. If you prefer to define a new schema for the trigger in the Create Trigger notebook, and you don't have SYSADM authority or DBADM authority on the database in which the trigger is to reside, you need IMPLICIT_SCHEMA authority on that database.
To drop a trigger	You must be the creator of the trigger, or you must have one of the following authorizations: SYSADM authority DBADM authority on the database in which the trigger is stored The DROPIN privilege on the trigger's schema