BUG: Shared Intent Lock Acquired by READTEXT Are Not Released

• Microsoft SQL Server, version 6.5 Service Pack 3

SYMPTOMS

Shared intent locks taken during a READTEXT operation are not released, even after the READTEXT completes. A process that tries to get an exclusive table lock may be blocked by this sh_intent lock.

WORKAROUND

To avoid blocking, minimize requests for exclusive table locks on this table. Testing has shown that any command issued after the READTEXT will cause the sh_intent lock to be released.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5 Service Pack 3. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Trace flag 1200 shows that the sh_intent is acquired but is not being released. Only processes requesting an exclusive table lock will be blocked. This problem occurs only on SQL Server build 6.5.252 and Service Pack 3. In testing, a SELECT @@spid was issued following the READTEXT operation from the same connection. This seemed to clear the sh_intent lock, and was also verified with trace flag 1200.