Home/ Questions/Q 503197
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T06:22:10+00:00

In this article , the author suggests that there is material overhead associated with

  • 0

In this article, the author suggests that there is material overhead associated with SET NOCOUNT ON and that “By removing this extra overhead from the network it can greatly improve overall performance for your database and application”

The author references a change in the default stored procedure template from 2000 to 2005 and suggests that “Microsoft even realized the issue ” which prompted the change in this template.

Does somebody have hard evidence that either supports or refutes the claimed performance gain with setting NOCOUNT ON.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The last link in my question here: “SET NOCOUNT ON usage” refers to an article on it.

    Given how trivial it is, why not leave it in and stop the client processing another resultset?

    And without SET NOCOUNT ON, nHibernate can break too (mentioned in question)

    • 0