SELECT FOR UPDATE with SQL Server. Revisit all your queries, maybe you have some query that select without ROWLOCKFOR UPDATE hint from the same table you have SELECT FOR UPDATE. MSSQL often escalates those row locks to page level locks even table level locks, if you dont have index on field you are querying, see this explanation. Since you ask for FOR UPDATE, i could assume that you need transacion levele. Since the first version of this article was published in October, 2003, the Spring Framework has steadily grown in popularity. It has progressed through version 1. 0. So the advice on that site is not applicable to your problem. Its just an insight why MSSQL escalates locks. If you are already using MSSQL 2. MVCC based, i think you should have no problem with row level lock using ROWLOCKUPDLOCK hint. But if you are already using MSSQL 2. FOR UPDATE if they escalate locks by checking the fields on their WHERE clause if they have index. Download the free trial version below to get started. Doubleclick the downloaded file to install the software. The question is what is worse a deadlock, or a wrong value For financial databases, deadlocks are far worse than wrong values. I know that sounds backwards, but. C3p0 is an easytouse library for making traditional JDBC drivers enterpriseready by augmenting them with functionality defined by the jdbc3 spec and the optional. Join the NASDAQ Community today and get free, instant access to portfolios, stock ratings, realtime alerts, and more Join Today. P. S. Im using Postgre. SQL, it also uses MVCC have FOR UPDATE, i dont encounter same problem. Lock escalations is what MVCC solves, so i would be surprised if MSSQL 2. WHERE clauses that doesnt have index on its fields. If thatlock escalation is still the case for MSSQL 2. WHERE clauses if they have index. Disclaimer my last use of MSSQL is version 2.