Disallow results from triggers?

re: Disallow results from triggers?

James Luetkehoelter — Thu, 05 Feb 2009 13:25:55 GMT

I'm really opposed to this for one simple reason - it's playing to the lowest common denominator. My guess is the reason that this is being enforced is because they've had too many support calls or have had people complain with people writing triggers that are intended to return a result set to be used elsewhere. Personally I can't conceive of using a trigger that way, and I avoid them like the plague in the first place. But again MS is instead focus not on education but hard-coding into SQL what should be the "proper usage". Which again makes SQL seem like anyone can use it ("It won't let you do the wrong thing!" - I can see the marketing now). Wake up - this is as complex a DBMS as Oracle is now - take the knowledge of the engine seriously.

re: Disallow results from triggers?

Adam Machanic — Thu, 05 Feb 2009 16:40:10 GMT

I used to use rowsets coming back from triggers quite often before the OUTPUT clause was added... I haven't had any reason to use it since then, but I am also not sure that there is no possible use case. I'm curious as to the reason they want to disable this functionality. Yes, it may be a bit confusing in some cases, but it's been around for quite some time and as far as I know hasn't caused anyone major issues; it actually seems like something not many people know about. Seems a tiny issue to focus on when there are so many other important areas that could be addressed...

re: Disallow results from triggers?

John Paul — Sat, 25 Dec 2010 15:46:02 GMT

@Adam

Yes I also agree with you. Microsoft has 1000 things to resolve other than disabling a feature that can be very helpfull sometimes.