This method supports multiple granularity lock, automatic lock and automatic lock escalation.
该方法支持多粒度锁、自动加锁特性和自动锁粒度升级特性。
If not, lock escalation continues until the percentage of the lock list held is below the value of MAXLOCKS.
否则，锁升级就会一直进行，直到所持有的锁列表百分比低于MAXLOCKS。
After some small number of row locks are obtained, a lock escalation to a table lock will occur automatically.
当获得少量的行锁时，行锁就会自动地逐渐升级为表锁。
If after replacing these with a single table lock, the MAXLOCKS value is no longer exceeded, lock escalation stops.
如果用一个表锁替换这些行锁，将不再会超出maxlocks值，那么锁升级就会停止。
Using a lock hint such as ROWLOCK only alters the initial lock plan. Lock hints do not prevent lock escalation.
查阅资料显示：使用锁定提示如ROWLOCK只改变初始锁定计划。锁提示不能防止锁升级。
MAXLOCKS defines a percentage of the lock list held by an application that must be filled before the database manager performs lock escalation.
MAXLOCKS定义了应用程序持有的锁列表的百分比，在数据库管理器执行锁升级之前必须填充该锁列表。
And the location of every row is in a fixed location, allowing for techniques such as lock escalation when too many fine-grained locks would otherwise be needed.
并且由于每一行都被存储在固定的位置，使得锁升级这样的技术得以实现，以避免过多细粒度锁。
When the number of locks held by any one application reaches this percentage of the total lock list size, lock escalation occurs for the locks held by that application.
当任何一个应用程序所持有的锁数量达到整个锁列表大小的这个百分比时，对该应用程序所持有的锁进行锁升级。
Lock escalation is the process of converting many fine-grain locks into fewer coarse-grain locks, reducing system overhead while increasing the probability of concurrency contention.
锁升级是将许多较细粒度的锁转换成数量更少的较粗粒度的锁的过程，这样可以减少系统开销，但却增加了并发争用的可能性。
This parameter defines a percentage of the lock list held by an application that must be filled before the database manager performs escalation.
该参数定义数据库管理器执行升级之前必须填入的应用程序所占有锁列表的百分比。
This parameter defines a percentage of the lock list held by an application that must be filled before the database manager performs escalation.
该参数定义数据库管理器执行升级之前必须填入的应用程序所占有锁列表的百分比。
应用推荐