NOCOUNT ON in Stored procedures

Jon Galloway blogs about the use of SET NOCOUNT ON here.

While I appreciate the reduction in network traffic using SET NOCOUNT ON, the main reason I use SET NOCOUNT ON is that in some cases, and I cannot explicitly enumerate which cases, lack of SET NOCOUNT ON causes the stored procedure as called from ADO.NET.

So, the rule should be: SET NOCOUNT ON Always!

Posted by Douglas Reilly at 09:08 PM  Permalink