FIX: Bulk Insert Operation May Cause Blocking (322379)

SYMPTOMS

While a Bulk Import operation (Bulk Copy or Bulk Insert) is executing, SQL Server may stop responding to new connections, and some existing connections may stop progressing. While these behaviors occur, Latch Timeout errors may appear in the SQL Server error log:

2002-04-04 05:18:01.96 spid72 WARNING: EC 32c14090, 12 waited 300 sec. on latch 819f1a34. Not a BUF latch.
2002-04-04 05:30:01.76 spid81 Time out occurred while waiting for buffer latch type 4,bp 0x348ac40, page 1:319119), stat 0xb, object ID 2:1:0, EC 0xA5E994D8 : 0, waittime 300. Not continuing to wait.

CAUSE

This problem occurs because the Bulk Insert operation has entered a non-yielding state and it is monopolizing the scheduler to which it is assigned. You can assign connections that are not responding to the same scheduler as the Bulk Insert operation.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix should have the following file attributes or later:

   Date         Time         Version    Size              File name
   ------------------------------------------------------------------
   05-MAY-2002  14:39:56 PM  8.00.623   7,454,801 bytes   Sqlservr.exe

NOTE: Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.