Re: NO COUNT

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Zach Wells (zwells_at_remove_ain1.com)
Date: 10/22/04 

Date: Fri, 22 Oct 2004 12:25:19 -0500

Stephen Howe wrote:
> I mean why bother doing "SET NOCOUNT ON" at the top of every SP if you can
> issue it at the start of getting a connection and from then on, all SP's are
> affected? Or are they not?
>

Because that would mean it is up to the ADO programmer to know that it
is necessary to turn on NOCOUNT. If you put it in each SP then you know
it well be set correctly.

Zach

Relevant Pages

  • Re: NO COUNT
    ... > The setting is connection based. ... seen in the documentation is oriented round the fact that you can set ... NOCOUNT ON at the top of a SP. ... our processes by ADO and torn down only at the end. ...
    (microsoft.public.sqlserver.programming)
  • Re: Connection performance issue
    ... > Zach Wells wrote: ... connection pooling on the client can mitigate this somewhat. ... recommends that practice. ...
    (microsoft.public.sqlserver.programming)
  • Re: ADO Broken Connection
    ... > a way to programmatically determine a network connection loss in the ... Stephen Howe ... Prev by Date: ...
    (microsoft.public.data.ado)
  • Re: Connection Collection
    ... And a Connection objection does have a collection - 2 in fact - the Errors ... and Properties collection. ... Stephen Howe ...
    (microsoft.public.data.ado)
  • Re: DB Connection ID
    ... The ID that the DB holds for this connection. ... Iterating through the Connection Properties with a valid connection might ... Stephen Howe ...
    (microsoft.public.data.ado)