Carlo Romagnano (7/24/2013)
Hugo Kornelis (7/23/2013)
In other words - if the statement causes a trigger to fire, it should have either no OUTPUT clause or an OUTPUT clause with an INTO keyword. Using the OUTPUT clause without INTO (so that the results of the OUTPUT specification go to the client) is not allowed when a trigger fires.
The question is WHY?
Technically, I do not see the connection or the hindrance of TRIGGER -> OUTPUT -> INTO.
OUTPUT without INTO sends data to the client.
A trigger might also send output to the client.
Maybe there were some test cases where the two outputs somehow interfered, and the team decided that fixing it would take too much resources???
Hugo Kornelis, SQL Server/Data Platform MVP (2006-2016)
Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis