FIX: Incorrect data is inserted unexpectedly when you perform a bulk copy operation by using the DB-Library API in SQL Server 2000 Service Pack 4

This article describes the following about this hotfix release:

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

When you perform a bulk copy operation by using the DB-Library API in Microsoft SQL Server 2000 Service Pack 4 (SP4), incorrect data is inserted unexpectedly.

Note This problem does not occur in Microsoft SQL Server 2000 Service Pack 3 (SP3).

This problem occurs because of a design change in SQL Server 2000 SP4. When you perform a bulk copy operation by using the DB-Library API, the bcp_init function performs the necessary initializations. In SQL Server 2000 SP3, the bcp_init function uses the clustered index that is created on the following columns in the syscolumns table to return the data:

• The id column
• The colid column
• The number column

Therefore, the data is returned in the order of the colid column in the syscolumns table.

In SQL Server 2000 SP4, the bcp_init function uses the nonclustered index that is created on the following columns in the syscolumns table to return the data:

• The id column
• The name column
• The number column

Therefore, the data is returned in the order of the name column in the syscolumns table.

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.

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, submit a request to 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

• Microsoft SQL Server 2000 Service Pack 4 (SP4)
  
  For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:
  290211  (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack

Registry information

You do not have to 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 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.

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

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: