FIX: Bcp_batch Stops Responding After Interleaved Bcp_sendrow

Last reviewed: June 27, 1997
Article ID: Q164178
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 15926 (6.5)

SYMPTOMS

When you use two dbprocesses in one program to insert image/text data with the Bulk Copy Program (BCP) functions of DB-Library in two different tables, the program may stop responding on bcp_batch if you call bcp_sendrow and bcp_batch in the following order:

   for a = 1 to m
   {
      for i=1 to n
      {
         bcp_sendrow(process A)
         bcp_sendrow(process B)
      }

   bcp_batch(process A)
   bcp_batch(process B)
   }

This problem only happens when the 'select into/bulkcopy' option is set in the database and BCP contains image/text data.

WORKAROUND

To work around this problem, do any of the following:

  • First call the BCP functions bcp_sendrow, bcp_batch, and bcp_done for process A, and then again for process B.
  • Call the BCP functions for process A in one program and the ones for process B in another program.
  • Set 'select into/bulkcopy' to false.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.


Additional query words: DEADLOCK
Keywords : kbbug6.50 kbprg SSrvBCP SSrvDB_Lib
Version : 6.5
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.