BUG: BCP: Err Msg: Attempt to Bulk-copy an Oversized Row

 Last reviewed: April 28, 1997
Article ID: Q99923

The information in this article applies to:
  • Microsoft SQL Server version 4.2 for OS/2
  • Microsoft SQL Server, version 4.2
BUG# OS/2: 8678 (4.2) 
       NT: 8679 (4.2)

SYMPTOMS

When doing a bulk copy from an ASCII data file into SQL Server with a 

char column that does not allow nulls, and where the data file does
not have data for that column (intending to insert default value bound to the column), the rows are copied successfully, but the following message is displayed once for each row: 

   Attempt to bulk-copy an oversized row to the SQL Server.
This happens only if the column is a char datatype and is defined as not null and the data file does not contain any data for that column. This does not happen if the column is of type varchar.

WORKAROUND

You can create a temporary table with the char column defined as allowing nulls, BCP in data into that table and then insert data from the temp table to the actual table with non-null char column using an INSERT statement.

Another workaround is to define the column as varchar instead of char.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available

Additional query words: bcp bulk copy program error err msg errmsg alert
Keywords : kbbug4.20 kbtool SSrvBCP SSrvWinNT
Version : 4.2 | 4.2 | 4.2
Platform : MS-DOS OS/2 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: April 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.