Latest revision as of 11:07, 21 July 2020

Knowledge Base

FIX: Trace Flag 1211 Does Not Work Properly

Article ID: 175546

Article Last Modified on 10/3/2003

APPLIES TO

Microsoft SQL Server 6.5 Service Pack 3

This article was previously published under Q175546

BUG #: 17001 (NT: 6.5.258)

SYMPTOMS

SQL Server 6.5 Service Pack 3 (build 6.5.258) introduced trace flag 1211 to provide additional lock management functionality, such as enabling retry on allocation lock collision. However, if you enable "lock retries" through this trace flag, either at server startup or with the global TRACEON command, you will not see the enhanced behavior.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5 Service Pack 3. This problem was corrected in the latest Microsoft SQL Server 6.5 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Additional query words: sp sp3

Keywords: kbbug kbfix kbusage KB175546

Revision as of 16:38, 18 July 2020 (view source) 3155ffGd (talk \| contribs) (importing KB archive)		Latest revision as of 11:07, 21 July 2020 (view source) X010 (talk \| contribs) m (Text replacement - """ to """)
Line 49:		Line 49:
	== SYMPTOMS ==		== SYMPTOMS ==

	SQL Server 6.5 Service Pack 3 (build 6.5.258) introduced trace flag 1211 to provide additional lock management functionality, such as enabling retry on allocation lock collision. However, if you enable ~~"~~lock retries~~"~~ through this trace flag, either at server startup or with the global TRACEON command, you will not see the enhanced behavior.<br />		SQL Server 6.5 Service Pack 3 (build 6.5.258) introduced trace flag 1211 to provide additional lock management functionality, such as enabling retry on allocation lock collision. However, if you enable "lock retries" through this trace flag, either at server startup or with the global TRACEON command, you will not see the enhanced behavior.<br />