I was asked this question at an interview and had no answer. Can anyone here explain?


4 Answers 4


Locks can exist on rows, pages, partitions, or whole tables and indexes. When a transaction is in progress, the locks held by the transaction take up resources.

Lock escalation is where the system consolidates multiple locks into a higher level one (for example consolidating multiple row locks to a partition or the whole table) typically to recover resources taken up by large numbers of fine-grained locks.

It will do this automatically, although you can set flags on the tables (see ALTER TABLE in the documentation) to control the policy for lock escalation on that particular table.

In particular, premature or overly eager lock escalation used to be a problem on older versions of Sybase and SQL Server when you had two processes writing separate rows into the same page concurrently. If you go back far enough (IIRC SQL Server 6.5) SQL Server didn't have row locking but could only lock tables or pages.

Where this happened, you could get contention between inserts of records in the same page; often you would put a clustered index on the table so new inserts went to different pages.


It's a method for reducing system overhead, by converting many fine grained locks to fewer coarse grained ones. More detailed information can be found here and here.

For example, if you have many (usually hundreds or more) locks on specific rows in a table, once you exceed your maximum allowed number of locks, these might be exchanged for a lock on the whole table.


SQL Server does Lock Escalation in order to reduce memory overhead, by converting several fine-grained low level locks to coarse-grained high level locks.

  • Row Locks are always escalated to Table Locks, and
  • Page Locks are also escalated to Table Locks.

It is a myth that Row locks are escalated to Page locks.

If a table having very few row-updates, SQL engine will try to take of Row-Locks on those rows or Page-Lock on those Pages. Let's say it has taken Row-Lock. But if the row-updates increases the threshold (~5k locks) then instead of taking several Row-Locks it takes a single Table-Lock. Thus, this reduces memory overhead by releasing several Row-Locks and taking a single Table-Lock, but increases concurrency. Same happens with the Page lock.

The Lock Escalation threshold is at-least 5000 locks, and depends on several factors, a detailed explanation of Lock Escalation has been mentioned here in MSDN BoL: https://technet.microsoft.com/en-us/library/ms184286(v=sql.105).aspx

  • 4
    Doesn’t escalating a lock reduce concurrency rather than increase it?
    – binki
    Commented Jul 27, 2020 at 18:18

Lock escalation means the conversion of a lock to a more restrictive mode. This is most often seen in databases. A query might have a resource locked for "shared" and escalate it to "exclusive" to perform an update.