FIX: The BULK INSERT statement may not return any errors when you try to import data from a text file to a table by using the BULK INSERT statement in Microsoft SQL Server 2005

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for applying the hotfix package
• Whether you must restart the computer after you apply the hotfix package
• Whether the hotfix package is replaced by any other hotfix package
• Whether you must make any registry changes after you apply the hotfix package
• The files that are contained in the hotfix package

When you try to import data from a text file to a table by using the BULK INSERT statement in Microsoft SQL Server 2005, the BULK INSERT statement may not report any errors. This problem occurs even if the length of the numeric data in the text file is larger than the length of numeric column in the table. This problem occurs when the following conditions are true:

• The data file uses the text file format, not the native file format.
• The length of the data in the data file for the NUMERIC column is longer than the length of the definition for the NUMERIC column in the table.

Note In SQL Server 2000, this problem causes the 4867 error.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have SQL Server 2005 Service Pack 1 (SP1) installed on the computer before you apply this hotfix. For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
SQL Server 2005, x86 versionsSQL Server 2005, x64 versionsSQL Server 2005 Itanium architecture versions

To work around this problem, use one of the following methods:

• Use an error file by specifying the ERRORFILE parameter of the BULK INSERT statement, and then check if the error file contains rows after the BULK INSERT statement is finished.
• Set the MAXERROR parameter of the BULK INSERT statement to 0. The BULK INSERT statement ends when any errors occur.
• Use the native file format instead of the text file format for the import file.
• Use the Bcp.exe utility instead of the BULK INSERT statement.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: