Interesting read: Time eating bug of the day… – Fabian S. Biehn – Google+.
TL;DR: in SQL Server use SET NOCOUNT ON so tools taking the last modified record count won’t be confused by your trigger.
Source: [WayBack] Time eating bug of the day: I used a TADOQuery.ExecSQL (on Berlin) for an Up…
Related: [WayBack] sql server – ADODB affected rows return trigger’s affected rows – Stack Overflow
–jeroen