Make %%lockres%% a documented feature - by JR-J

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 458076 Comments
Status Closed Workarounds
Type Suggestion Repros 4
Opened 5/25/2009 3:45:05 PM
Access Restriction Public


We had a serious issue with collisions in the hash values of the lock resource when parallel loading 25 million rows into a 1 billion row table.  We were getting unexplained deadlocks that based on the data being loaded shouldn't have occurred.  

It was confirmed that this was due to the values held in the table for the composite clustered index key and the algorithm used to generate the lock resource hash value meant duplicates were occuring

The undocumented feature %%lockres%% helped us prove that this was the issue. Without it I doubt we could have proven this issue.
Sign in to post a comment.
Posted by Microsoft on 9/2/2009 at 10:29 AM
Hello James,

Thank you for your feedback on the %%lockres%% feature. At present time we do not have the test resources available to allow this to be documented feature. Should this situation change we will reconsider documenting this feature.

Kelly Wilson
SQL Server
Posted by Microsoft on 5/29/2009 at 10:19 AM
Hello James,

Thank you for your feedback on the lockres feature documentation. We will investigate the issue and respond with our finding.

Kelly Wilson
SQL Server
Posted by Microsoft on 5/28/2009 at 1:28 PM
Thanks for reporting it. we will look into it in the next iteration of BOL.