BUG: BCP Import with Extended Character as a Column Delimiter Fails

ID: Q225705

The information in this article applies to:

Microsoft SQL Server version 7.0

BUG #: 54077 (SQLBUG_70)

SYMPTOMS

Importing data into SQL Server using the bulk copy program (BCP) may fail if the field terminator is an extended character (that is, ASCII values 128-255). The problem only happens with import files that are over 32 MB in size.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

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


   Version        File name      Platform
   --------------------------------------

   3.70.0653      Odbcbcp.dll    (x86)
   3.70.0653      Sqlsrv32.dll   (x86)
   3.70.0653      Odbcbcp.dll    (Alpha)
   3.70.0653      Sqlsrv32.dll   (Alpha)

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

WORKAROUND

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

Do not use extended characters as field terminators in the import file.

Keep the import file size below 32 MB in size.

Split the import file into several files, each of these being less than 32 MB in size.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 7.0.

MORE INFORMATION

This problem has been observed with command line BCP and SQL-DMO BulkCopy.

For example, suppose you have a file called Myfile.txt that is over 32 MB in size. You will encounter this problem if you use the following command-line BCP operation:

bcp pubs.dbo.mytable in myfile.txt -c -tÿ -Usa -P

No data will be imported to pubs.dbo.mytable and results similar to the following will be displayed after a short pause:

0 rows copied.
Network packet size (bytes): 4096
Clock Time (ms.): total 13079

Furthermore, specifying a value for the FirstRow and LastRow properties (-F and -L with command-line BCP) will not avoid this problem.

Additional query words: ext char chars


Keywords          : SSrvBCP SSrvDMO kbbug7.00 
Version           : winnt:7.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: July 2, 1999