http://sqlblog.com/blogs/louis_davidson/archive/2009/06/06/disallow-results-from-triggers.aspxA setting that I noticed a while back when looking at sys.configurations was disallow results from triggers. &#160; Triggers are one of my favorite subjects, and you will find a lot of good uses of them in my book (triggers are also well named, as poorenCommunityServer 2.1 SP2 (Build: 61129.1)http://sqlblog.com/blogs/louis_davidson/archive/2009/06/06/disallow-results-from-triggers.aspx#38158Tue, 30 Aug 2011 14:59:58 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:38158Koenraad Dendievel<p>Thanks man, i was searching for this for a long time.</p> <p>I have some exec statements(e.g. starting asynchronous threads) in some of my triggers wich return empty resultsets (no way to suppress them). It messed up loads of things like insert statements from PHP wich don't expect more then 'x row(s) affected' or even certain things in MS-access </p> <p>This should be disabled by default!!!</p>