I am using SQL server 2000 with Uniface (4GL).
I am running a process which commits every 30 seconds or so on one
machine and another user is trying to perform a small update at the
same time on the one of the tables whose data is modified by the first
process.
I accept that the two second process may get blocked at times by the
first but expect that to only happen rarely due to the likelihood of
both processes trying to update the very same row in a large table.
Other users are also on line at the same time performing updates
across the database.
What I have witnessed though was the second process being blocked by
the first (confirmed by looking in enterprise manager) and REMAINING
BLOCKED EVEN AFTER A COMMIT in the first process!!
My big problem is that I have only seen this happen once on a customer
site and have not been able to reproduce it myself to provide any
further information.
The application is set to use row level locking and is also in read
uncommited mode.
Any help or suggestions would be greatly appreciated.
Bob.