Efficient trigger type

May be I am wrong but the difference is that (from BOL) "AFTER triggers are never executed if a constraint violation occurs" and FOR trigger doesn't care. But, probably, from effeciency point of view there is no difference. Thanks

AFTER and FOR are synonyms of each other. They create the same trigger. The only types of triggers available in SQL 2000 are AFTER and INSTEAD OF

You can use the FOR clause to specify when a trigger is executed:

• AFTER

  The trigger executes after the statement that triggered it completes. If the statement fails with an error, such as a constraint violation or syntax error, the trigger is not executed. AFTER triggers cannot be specified for views, they can only be specified for tables. You can specify multiple AFTER triggers for each triggering action (INSERT, UPDATE, or DELETE). If you have multiple AFTER triggers for a table, you can use sp_settriggerorder to define which AFTER trigger fires first and which fires last. All other AFTER triggers besides the first and last fire in an undefined order which you cannot control.

  AFTER is the default in SQL Server 2000. You could not specify AFTER or INSTEAD OF in SQL Server version 7.0 or earlier, all triggers in those versions operated as AFTER triggers.

• INSTEAD OF

  The trigger executes in place of the triggering action. INSTEAD OF triggers can be specified on both tables and views. You can define only one INSTEAD OF trigger for each triggering action (INSERT, UPDATE, and DELETE). INSTEAD OF triggers can be used to perform enhance integrity checks on the data values supplied in INSERT and UPDATE statements. INSTEAD OF triggers also let you specify actions that allow views, which would normally not support updates, to be updatable.