Article ID: 904244
Article Last Modified on 11/2/2007
APPLIES TO
- Microsoft SQL Server 2000 Standard Edition
- Microsoft SQL Server 2000 Workgroup Edition
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft SQL Server 2000 Personal Edition
Bug #: 1833 (WebData QFE)
Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.
SUMMARY
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
SYMPTOMS
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).
CAUSE
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.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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 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.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Spupdsvc.exe | 6.1.22.5 | 22,752 | 01-Jun-2005 | 02:22 | x86 |
| Tempcatsign.cdf | Not Applicable | 953 | 02-Aug-2005 | 08:50 | Not Applicable |
| Mssdi98.dll | 8.11.50523.0 | 239,104 | 06-Jun-2005 | 07:46 | x86 |
| Ntwdblib.dll | 2000.80.2151.0 | 290,816 | 28-Jul-2005 | 00:25 | x86 |
| Pfclnt80.dll | 2000.80.2151.0 | 430,080 | 28-Jul-2005 | 00:25 | x86 |
| Procsyst.sql | Not Applicable | 552,068 | 16-Jun-2005 | 09:15 | Not Applicable |
| Sp4_serv_qfe.sql | Not Applicable | 18,810 | 16-Jun-2005 | 09:15 | Not Applicable |
| Sqlagent.exe | 2000.80.2151.0 | 323,584 | 27-Jul-2005 | 10:57 | x86 |
| Sqldiag.exe | 2000.80.2151.0 | 118,784 | 27-Jul-2005 | 12:01 | x86 |
| Sqlfth75.dll | 2000.80.2151.0 | 102,400 | 27-Jul-2005 | 11:06 | x86 |
| Sqlservr.exe | 2000.80.2151.0 | 9,154,560 | 27-Jul-2005 | 12:59 | x86 |
| Stardds.dll | 2000.80.2151.0 | 176,128 | 28-Jul-2005 | 00:25 | x86 |
| Ums.dll | 2000.80.2151.0 | 35,328 | 28-Jul-2005 | 00:25 | x86 |
| Osql.exe | 2000.80.2039.0 | 57,344 | 03-May-2005 | 13:32 | x86 |
| Sqlstpcustomdll.dll | 1.0.128.0 | 943,104 | 01-Aug-2005 | 07:55 | x86 |
| Sqlstpcustomdll.rll | Not Applicable | 24,576 | 01-Aug-2005 | 07:55 | Not Applicable |
| Updspapi.dll | 6.1.22.5 | 371,936 | 01-Jun-2005 | 02:25 | x86 |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
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:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbpubtypekc kbqfe kbhotfixserver KB904244
