FIX: Clients Hang Issuing Concurrent WRITETEXTs
  
PSS ID Number: Q104113
Article last modified on 10-31-1994
 
4.20
 
OS/2
 

----------------------------------------------------------------------
The information in this article applies to:
 
  - Microsoft SQL Server version 4.2 for OS/2
----------------------------------------------------------------------
 
BUG# OS/2: 1711 (4.2)
 
SYMPTOMS
========
 
When multiple clients are inserting or updating text and/or image
data in a table via WRITETEXT, as well as selecting from that
table, one or more of the clients may hang. Issuing an sp_who
shows the hung client(s) having a state of Awaiting Command, and
sp_lock shows that no locks are preventing the client(s) from
continuing. New connections can be established to SQL Server,
indicating SQL Server itself is not hung.
 
CAUSE
=====
 
Under certain conditions, depending on where in the table the
concurrent clients are updating and selecting data, SQL Server may
cause the client application to hang indefinitely. This can happen
with both the logged and non-logged syntax of WRITETEXT.
 
STATUS
======
 
Microsoft has confirmed this to be a problem in SQL Server version
4.2 for OS/2. This problem was corrected in SQL Server version
4.2b. For more information, contact your primary support provider.
 
Additional reference words: 4.20
KBCategory: kbprg
KBSubcategory: SSrvServer
 
=============================================================================
 
Copyright Microsoft Corporation 1994.
