SQL Guide : SQL extensions : Triggers : Trigger privileges and security
  
Trigger privileges and security
Because triggers can be activated by a user’s attempt to INSERT, UPDATE, or DELETE data, no privileges are required to execute them.
When a user invokes a trigger, the user assumes the privileges of the owner of the table on which the trigger is defined. The action statements are executed on behalf of the table owner, not the user who activates the trigger. However, to create a trigger which uses a stored procedure requires that the creator of the trigger meet one of the following conditions:
You have DBA privileges.
You are the owner of the table on which the trigger is being defined.
You were granted all privileges on the table.
If the creator has DBA authority and creates a table for another user, a solidDB® server assumes that unqualified names specified in the TRIGGER command belong to the user. For example, the following command is executed under DBA authority: CREATE TRIGGER A.TRIG ON EMP BEFORE UPDATE
Since the EMP table is unqualified, the solidDB® server assumes that the qualified table name is A.EMP, not DBA.EMP.
See also
Triggers