Microsoft KB Archive/171368
Article ID: 171368
Article Last Modified on 2/14/2005
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q171368
BUG #: 16739 (Windows: 6.50)
A bulk copy program (BCP) process may become blocked by a DUMP TRANSACTION statement, while the DUMP TRANSACTION blocked is blocked by the BCP operation.
The block is more common when the database has the Truncate Log On Checkpoint option enabled, but it may occur when the DUMP TRANSACTION statement is used by a user connection.
The sp_who output does NOT show a block in the "Blk" column but the checkpoint spid, generally spid 3, shows a "dump transaction" and the user connection shows a "bulk insert".
To work around this problem, try one of the following:
- Reduce the batch size of the BCP operation, to reduce the frequency of this problem.
- Use fast mode BCP, to reduce the frequency of this problem.
- Stop the BCP operation and allow the DUMP TRANSACTION to complete.
- Try using -F and -L BCP command-line options.
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
Additional query words: hang locked hung dead frozen freeze stop stopped
Keywords: kbbug kbusage KB171368