Microsoft KB Archive/312091

= FIX: Optimized Lock Manager Lookup on SMP Systems =

Article ID: 312091

Article Last Modified on 9/26/2005

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q312091



BUG #: 356045 (SHILOH_BUGS)



SYMPTOMS
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.



RESOLUTION
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:

290211 INF: How To Obtain the Latest SQL Server 2000 Service Pack

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:   Version      File name --

8.00.0563   Sqlservr.exe NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.



STATUS
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.



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

Keywords: kbbug kbfix kbsqlserv2000presp3fix kbqfe kbsqlserv2000sp3fix kbhotfixserver KB312091

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.