FIX: Optimized Lock Manager Lookup on SMP Systems

If a connection requests a lock, the lock manager searches a list of owners already granted the lock and then determines if the current lock request mode is compatible with the existing granted mode.

In tests where there are many different users who are all granted the lock (for example, an intent shared table lock), the list of granted owners can be long, and a search of the list can be resource intensive, resulting in higher CPU utilization than necessary.

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix should have the following file attributes or later: NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

With this fix, a performance enhancement was added to the lock manager to make these lock lookups more efficient.