I have a multi-user transaction oriented app that requires a status to be updated in one of the records. The correct update requires data from several other records in order to make a determination. Right now, both the data updates and a status update are being performed in one transaction. This makes sense but is also not working correctly as some of the data required to make the status update is not properly on the disk because it is only in buffers from the transaction and not yet committed.

I need a good solution; two transactions? One for data and another for the status update? Or a better method of obtaining the data that may not yet be on the disk? Several SELECT statements are processed which last I knew will be drawing the data from disk and not from any potentially uncommitted transactions.

Thanks,
Steve