A
andrew.clifford
Guest
Hello Jorrit, It looks like you're using an OpenEdge database at the backend; during my testing I found that Rollbase creates a VAST number of record locks by accessing records using sharelocks all the time. There are some minor changes you can make such as changing the Transaction Isolation Level to Read Uncommited msdn.microsoft.com/.../ms173763.aspx - but this can trigger other problems. The only real workaround I found was to set the number of lock entries on the database to an equaly large number. If you have access to the OpenEdge Tools you can use promon to easily see just how many locks are created for even the simplest actions. Not an answer just my experience.
Continue reading...
Continue reading...