Why can't this stored procedure be called? (Fre eTDS_JDBC and jtds)
Lowden, James K
LowdenJK at bernstein.com
Mon Sep 10 13:22:13 EDT 2001
I think Mr. Lewis is on to something. I happen to have the 6.5 docs here:
"In SQL Server, SET NOCOUNT ON eliminates the sending of DONE_IN_PROC
messages to the client for each statement in a stored procedure. For stored
procedures that contain several statements that do not return much actual
data, this can provide a significant performance boost because network
traffic is greatly reduced."
If you want to set this off permanently, see sp_configure and @@options.
From: brlewis at alum.mit.edu [mailto:brlewis at alum.mit.edu]
Sent: September 10, 2001 12:17 PM
To: TDS Development Group
Subject: [freetds] Re: Why can't this stored procedure be called?
(FreeTDS_JDBC and jtds)
"Anton van Straaten" <anton at appsolutions.com> writes:
> create procedure spTestExec as
> create table #tmp ( Result varchar(50) )
> insert #tmp execute spTestExec2
> select * from #tmp
You're going against 6.5 and still aren't in the habit of putting "set
nocount on" at the beginning of every stored procedure? I can hardly
get anything to work without it.
Bruce R. Lewis http://brl.sourceforge.net/
You are currently subscribed to freetds as: [LowdenJK at bernstein.com]
To unsubscribe, forward this message to
More information about the FreeTDS