If you plan to use a custom trigger in any version of Microsoft Dynamics SL 2011, be sure to add "set nocount on" at the beginning. Some of the symptoms of a custom trigger firing without "set nocount on" are SQL Server Message 62, SQL Server Message 63, and SQL Server Message 93 in conjunction with a timeout error.
The “set nocount on” command limits the amount of noise (such as status messages, row counts, etc..) that get returned to SWIMAPI. SWIMAPI has never liked this "noise", but in 7.x and prior it was a bit more tolerant. In 2011, it is far less tolerant. In any version of SL, any custom trigger should start out with a “set nocount on” command or it could cause problems such as the aforementioned error messages
