Lock Escalation settings

Question

Hi All,
In one of my production server Deadlock issue happened, for that issue we are planning to change lock escalation  to table.
Will it make any impact to other tables or objects in database apart from a single table.
Please suggest anyone it would be great helpful for me.
Thanks in Advance...

Answer 1

Hi Srinivas,
Below is snippet from
Paul's Article
In SQL Server 2005 (and 2008) you can change the behavior of lock escalation (if you really know what you're doing) using these trace flags:
1211 – disables lock escalation totally and will allow lock memory to grow to 60% of dynamically allocated memory (non-AWE memory for 32-bit and regullar memory for 64-bit) and will then further locking will fail with an out-of-memory
error
1224 – disables lock escalation until 40% of memory is used and then re-enables escalation
1211 takes precedence over 1224 if they're both set – so be doubly careful. You can find more info on these trace flags in
Books Online.
In SQL Server 2008, you can change the behavior of lock escalation per table using the
ALTER TABLE blah SET (LOCK_ESCALATION = XXX) where XXX is one of:
TABLE: always escalate directly to a table lock.
AUTO: if the table is partitioned, escalate to a partition-level lock, but then don't escalate any further.
DISABLE: disable lock escalation. This doesn't disable table locks – as the
Books Online entry says, a table lock may be required under some circumstances,
like a table scan of a heap under the SERIALIZABLE isolation level.
If you are changing lock escalation for particular table using alter table set lock escalation command it will change behavior for that table only
You should also read How to determine blocking is caused by Lock escalation
If you have partitioned tables please read
partition Level Lock escalation
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP