BUG: BCP May Fail to Import All Rows When You Use a Multi-character Row Delimiter (303515)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
- Microsoft SQL Server 7.0
This article was previously published under Q303515
BUG #: 354786 (SHILOH_BUGS)
BUG #: 101877 (SQLBUG_70)
SYMPTOMS
The bcp command prompt utility may fail to import all the rows of an input file if:
- The last column of the input file contains the first character of a multi-character row delimiter.
-and-
- You use a format file to skip importing the last column.
No errors are reported during the import.
WORKAROUND
Modify the input file and change the last column to a value other than the first character of the row delimiter.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 2000.
MORE INFORMATION
For example, the import can fail when you use an input file that has a single character field in the last column. The last column does not match any columns in the SQL Server table; therefore, a format file is used to skip importing the last column of the text file. If the row delimiter is "++%%" (without the quotes) and the last column in the input file is "+", the row may fail to import. Additionally, the row may successfully be imported depending upon the file size. If the row is copied to a smaller file, the row may import correctly.
| Modification Type: | Major | Last Reviewed: | 10/17/2003 |
|---|
| Keywords: | kbBug kbpending KB303515 |
|---|
|