Re: SQL 2000 Stored Procedure Problem



Richard (rich@xxxxxxxxxxxxxxxx) writes:
sp_configure 'user options' reports the same on both :
minimum=0, Maximum=32767, config_value=0, run_value=0

I added SET NOCOUNT ON as the first line in spTestTempTable - same
results. I had tried that yesterday while searching the groups for ideas
for 5 hours.

Any other suggestions are welcome.

What does your VB code looks like?



--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.



Relevant Pages

  • Re: Thesaurus Problem
    ... you are searching in British or International English its tsENG.xml. ... Looking for a SQL Server replication book? ... FROM FullDocuments ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Item Cannot be Found in Collection
    ... The "SET NOCOUNT ON" suggestion is not relevant for Access databases. ... setting that can only be performed in SQL Server. ... > I tried Set NOCOUNT = ON and I got a syntax error. ...
    (microsoft.public.scripting.vbscript)
  • Re: Query training -- Complex queries
    ... > Update PositionsEOM ... Here you don't have a derived table, but a correlated subquery. ... UPDATE in Books Online. ... is not written for SQL Server. ...
    (microsoft.public.sqlserver.server)
  • Re: Hashtable faster than SQL ?!!
    ... The Hashtable is in the RAM, and its searching algorithm is optimized for performance. ... The SQL Server keeps indexes on disk, so even if the algorithm is similar, loading the indexes from disk takes time. ... i made my own O/R mapping with an "entity cache" (caching all mapped ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: SQL 2000 Stored Procedure Problem
    ... ReturnValue varchar ... Try adding SET NOCOUNT ON in the beginning of the procedure. ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ... Books Online for SQL Server 2005 at ...
    (microsoft.public.sqlserver.security)