Microsoft Support KB25596 sp_lock2 have some mistakes in Collation Chinese_Taiwan_Stroke_BIN - by 亂馬客

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
2
Sign in
to vote
ID 727436 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 2/29/2012 9:59:36 PM
Access Restriction Public

Description

Please see [ http://support.microsoft.com/kb/255596/en-us?ln=en-us&sd=gn&fr=0 ].
If we run the sp_lock2 script, will occur errors, below.

Msg 911, Level 16, State 1, Line 1
Database 'MASTER' does not exist. Make sure that the name is entered correctly.
Msg 137, Level 15, State 2, Procedure sp_lock2, Line 125
Must declare the scalar variable "@ObjId".
Msg 137, Level 15, State 2, Procedure sp_lock2, Line 131
Must declare the scalar variable "@objId".
Msg 137, Level 15, State 2, Procedure sp_lock2, Line 135
Must declare the scalar variable "@ObjId".

Please modify the sp_lock2 script, thanks. 
Sign in to post a comment.
Posted by Ramu [MSFT] on 3/8/2013 at 10:00 AM
Thank you for reporting this. We will get the script changed to use 'master' in lower case. sp_lock and sp_lock2 are deprecated in newer versions of SQL server and Microsoft recommends that customers use Pssdiag (KB 830232) and SQLNexus (http://sqlnexus.codeplex.com/) for troubleshooting SQL Server performance issues.

Ramu (SQL Server Support Team)