Do not use sql triggers with Microsoft Dynamics NAV

I recentrly had a strange problem in Microsoft Dynamics Nav 5.0 sp1 (detailed problem is described in this post). I finally I managed to find the real cause of problem. There were some sql triggers in database tables. Those triggers were there for the perpose of a custom case. As Navision Client made an update in Purchase Header the trigger was run and make an insertion in another Navision table and in Purchase Header. All of this was in a BEGIN-COMMIT TRANSACTION statement, so the second statement of trigger was locked by the transaction of client. The client was unaware of this so although the client was returning from the post, the actual transaction in database did not commit, not to mention the unexeptable performance. So from all of this we make a new rule for our implementations: NEVER use sql triggers in a Microsoft Dynamic NAV Database