Database Latency on SQL 2000

[ChristineJ]

Has anyone ever experienced a problem where the result of an UPDATE statement is not visible on a SELECT run immediately afterwards? Its a large database, 500 plus users, very occasionally we seem to be getting the SELECT processed before the UPDATE. Statements are not running in a transaction. Any ideas?

[skhanal]

That sounds like a bug, never experienced this. What are the exact conditions when this happens?

Can you reproduce it?, if yes, you should contact Microsoft Product Support.

[ChristineJ]

I can't reproduce consistently, but its the only explanation for a bug we're seeing. We do an UPDATE and then immediately a SELECT which if the the UPDATE has worked, would return zero rows. Looking at the code route, there must have been a row returned, but looking at the database shortly afterwards the update has happened. Its happening in about 1 in 1000 times

[MAK]

are you seeing the results
from the same connetion or from a different connection?

[ChristineJ]

We're seeing the result later through a separate connection, but the code is using the same connection but different statement handle (ODBC connection)