Re: Buffering

Hi Sam,

Thanks for taking the time to reply.

To be honest, I'm pretty happy now that I've eliminated my first guess that
buffering could be causing this issue.

There are 4 or 5 other joins that could potentially cause the SQL to select
no rows.
The process is event-driven and at the time it is triggered I would expect
rows to be selected, and as I said above - re-running very shortly after
the fail does actually find rows.

There are another 4 or 5 inner joins involved, at first glance they look
like they should always find rows to join on but with legacy applications
things often surprise you. There are a couple of other background server
jobs running at the same time which access some of the involved tables for
update so next time it happens I'll trawl through the journals again to see
if something unexpected is going on - like a process re-numbering lines
numbers on an order detail file - or some such thing. I'm pretty sure now
it's probably something mundane like that. The infrequency with which I'm
seeing this issue lends more credence to the idea that it is an occasional
collision between two processes as opposed to a bug in a single process.

best regards,
Craig