BUG: BCP from a Table with Defaults May Cause Error

 Last reviewed: April 28, 1997
Article ID: Q93419

The information in this article applies to:
  • Microsoft SQL Server version 4.2a for OS/2
BUG# 7637 (4.2)

SYMPTOMS

When using Bulk Copy utility (BCP) to transfer data from a table with user-defined datatype and defaults are bound to both the datatypes and the column, BCP may generate the following error message: 

   Msg 243, level 16, state 1
   Type "integer" is not a defined system type.
Further research indicates that the error occurs only when the column is defined as INT allowing NULL and the datatype is defined as INT but not allowing NULL. If they are both defined as not allowing nulls, the problem will not occur.

CAUSE

SQL Server incorrectly handles table columns that are defined as an integer allowing nulls and having a default in the Bulk Copy utility.

WORKAROUND

Drop the default from the table before running BCP.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2a for OS/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
Keywords : kbtool SSrvBCP
Version : 4.2a
Platform : OS/2

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.