NO COUNT
From: Stephen Howe (stephenPOINThoweATtns-globalPOINTcom)
Date: 10/22/04
- Next message: TimBlume: "Transponding a table for getting specific result"
- Previous message: JXStern: "alter procedure while it's running"
- Next in thread: Aaron [SQL Server MVP]: "Re: NO COUNT"
- Reply: Aaron [SQL Server MVP]: "Re: NO COUNT"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 22 Oct 2004 17:00:35 +0100
Hi,
I have some import programs that are written in C++ and use ADO to import
into a SQL Server 7 database. At the start of the process I issue
SET NOCOUNT ON
just after starting a transaction and
SET NOCOUNT OFF
just before committing/aborting a transaction
All of this is so that SP's (including temporary SP's setup by ADO's Command
objects) execute a tad faster.
Does anyone want to comment whether this is good, bad or "makes no
difference" practice?
Thanks
Stephen Howe
- Next message: TimBlume: "Transponding a table for getting specific result"
- Previous message: JXStern: "alter procedure while it's running"
- Next in thread: Aaron [SQL Server MVP]: "Re: NO COUNT"
- Reply: Aaron [SQL Server MVP]: "Re: NO COUNT"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|