In a rare case when you need to control the execution sequence of database triggers, you can use the sp_settriggerorder statement to do so. However, the recommended best practice always remains that you should have business logic dependent upon execution sequence within stored procedures.

The following script shows how to set the hypothetical trigger - "dbo.trig_UpdateTrig01" - to fire after all other triggers on the table are executed.

--Change the trigger order
USE tempdb;
GO
sp_settriggerorder @triggername= 'dbo.trig_UpdateTrig01', @order='Last', @stmttype = 'INSERT';
GO

Please refer my post: http://beyondrelational.com/modules/2/blogs/77/posts/15588/0177-sql-server-control-the-trigger-execution-order.aspx for more details.