Kevin


Not the best approach, but what about using the transaction timeout feature - when a transaction has to drop out because it can't get a lock (ie another transaction is active) report it back to the users. With a bit of immediacy it might be possible to trace what's happening.

Roy Lambert

Roy Lambert wrote:

>Not the best approach, but what about using the transaction timeout feature - when a transaction has to drop out because it can't get a lock (ie another transaction is active) report it back to the users. With a bit of immediacy it might be possible to trace what's happening.
<<

Thanks Roy. That would definitely surface the problem faster.

Kevin,

Just to update this thread:  I've got your database/test setup running and it looks like the issue is the long-running report scripts that you're using.  The queries in one or more of these scripts are taking 60+ seconds total to execute, and that is having detrimental effects upon the ability of the transactions to complete.

I'm working on some optimization fixes for these queries for you, as well as analyzing the queries to see if the engine is holding read locks for too long.

Tim Young
Elevate Software
www.elevatesoft.com