لطفا منتظر باشید ...
Execution
Triggers fire just after the work has been completed by the DML statement, but before it has been committed to the database. From the perspective of the trigger, the data changes that fired it appear to have already taken place. For example, within an INSERT trigger, the rows being inserted appear to the trigger to already be in the table.A DML statement's execution plan branches to any triggers it fires just before returning. If the trigger permits the operation to proceed, and if no user transaction is present, any changes made by the DML statement are then committed to the database.
