FIX: Bulk Insert Does Not Insert Next Row When a Truncate Error Occurs

Article translations Article translations
Article ID: 275614 - View products that this article applies to.
This article was previously published under Q275614
BUG #: 57299 (SQLBUG_70)
Expand all | Collapse all


When you use a BULK INSERT statement the data may be truncated if the source data is longer than the destination. You expect this error message to occur:
MSG 4863 Bulk insert data conversion error (truncation) for row %d, column %d (%ls).
However, the next row in the file is not inserted. A BCP IN statement works as expected, and omits the row that should not be inserted and then inserts the rest of the data.


SQL Server is skipping rows because the routine that skips the remainder of the row always begins counting from zero instead of counting from the current position.


Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.


Article ID: 275614 - Last Review: March 14, 2006 - Revision: 2.1
  • Microsoft SQL Server 7.0 Standard Edition
kbbug kbfix KB275614

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from