FIX: BCP Format File Field Length Does Not Behave as Documented
This article was previously published under Q201857
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 53018 (SQLBUG_70)
Microsoft SQL Server Books Online states that if a length of zero (0) is specified in the format file for the data field, the zero length is ignored and that the length is read up to the termination character.
In actuality, Bcp.exe ignores the termination character, and depending on the length of zero (0) inserts a NULL value for that column.
Specify a length for the field to be greater than the maximum data length of the real data in that column. Then, the separator is found first and the proper data inserted.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0For more information, contact your primary support provider.
Article ID: 201857 - Last Review: 11/01/2013 21:26:00 - Revision: 3.0
Microsoft SQL Server 7.0 Standard Edition
- kbnosurvey kbarchive kbbug kbfix KB201857