sql server misc: Got a stored procedure that works fine, but occasionally it begins to
give back odd data, but only to ADO in my VB applications. This only
happens to one database (on a server with over 40 identical schema
databases) and only to one stored procedure in that database. The
problem goes away temporarily when I recompile the procedure, but can
come back in 10 minutes, or a week later.

The data returned has 3 columns: DATETIME, FLOAT, FLOAT
and returns about 12 rows (ie 12 weeks worth of data)

When executed in SQL Query Analyser, the data is fine, however when
read into an ADO Recordset, the first row is correct, but in
subsequent rows, the third column is always 0.0

Any suggestions?

Fred

PS SELECT @@VERSION Gives: Microsoft SQL Server 2000 - 8.00.384
(Intel X86) May 23 2001 00:02:52 Copyright (c) 1988-2000 Microsoft
Corporation Enterprise Edition on Windows NT 4.0 (Build 1381: Service
Pack 6)

Dave Glass (fredfreddy1892@hotmail.com) writes:
[quoted text, click to view]

Not more that since you are on SP1, you should consider to move on SP3.

As for the actual problem, it would help if you included the code of
the procedure and you VB code. Not that I am sure that it would be
sufficient to track down the cause, but with this tiny of bit information,
I am not interested in guessing.


--
Erland Sommarskog, SQL Server MVP, sommar@algonet.se

Books Online for SQL Server SP3 at