This is a similar to a problem that I reported about four weeks ago.
Under SQL Server 6.5/SP5a on an Alpha running NT 4.0 Service Pack 4. If I
execute two instances of a MS C console program at the same time, which
data from complex read only SQL Server Stored Procedure Cursors via ODBC 3,
the data is the same, sometimes not :-(
It also cannot be predicted when the data will not match. If the program is
executed, multiple times in a sequential fashion, this is not a problem, the
output always matches. Note, that when the outputs do not match, neither
match the output that comes from any of the good concurrent or sequential
Coming from a mainframe environment, is there something obvious that I'm
missing here ? Is their some extra locking that I have to control. My only
hint so far,
is that the fields that appear to differ are subject to the CONVERT
of a DECIMAL field to a SMALLINT field egCONVERT(SMALLINT, weight * 100).
Does SQL Server 6.5 have some thread safety problems ?