Article ID: 924344
Article Last Modified on 11/20/2007
APPLIES TO
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Workgroup Edition
Bug #: 1195 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.
SUMMARY
This article describes the following about this hotfix release:
- The issues that are fixed by this hotfix package
- The prerequisites for applying this hotfix package
- Whether you must restart the computer after you apply this hotfix package
- Whether this hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes after you apply this hotfix package
- The files that are contained in this hotfix package
SYMPTOMS
When you use the bulk copy program (bcp) command-line utility to import data in SQL Server 2005, you may receive incorrect results. This issue occurs if the following conditions are true:
- You import the data to a column of the real data type or of the float data type.
- The numeric data that is imported uses the scientific format.
- The numeric data is not explicitly signed. For example, the data is 3.123456E10 instead of 3.123456E+10.
- The exponent value of the data is divisible by 10. That is, the exponent value ends in zero.
In this case, the trailing zeros in the formatted value are ignored when you import the data. For example, the data 3.123456E10 is incorrectly stored as 31.23456.
CAUSE
This issue occurs because the SQL Native Client provider ignores the trailing zeros in the scientific format.
RESOLUTION
Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
- Microsoft SQL Server 2005 Service Pack 1 (SP1)
For information about how to obtain SQL Server 2005 SP1, see the following article in the Microsoft Knowledge Base:913089 How to obtain the latest service pack for SQL Server 2005
Restart information
You do not have to restart the computer after you apply this hotfix.
Registry information
You do not have to change the registry after you apply this hotfix.
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.
SQL Server 2005, 32-bit versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Msvcm80.dll | 8.0.50727.42 | 479,232 | 23-Sep-2005 | 07:48 | x86 |
| Msvcp80.dll | 8.0.50727.42 | 548,864 | 23-Sep-2005 | 07:48 | x86 |
| Msvcr80.dll | 8.0.50727.42 | 626,688 | 23-Sep-2005 | 07:48 | x86 |
| Sqlncli.dll | 2005.90.2183.0 | 2,222,424 | 18-Aug-2006 | 06:14 | x86 |
SQL Server 2005, 64-bit version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Msvcm80.dll | 8.0.50727.42 | 516,096 | 23-Sep-2005 | 07:27 | x64 |
| Msvcp80.dll | 8.0.50727.42 | 1,097,728 | 23-Sep-2005 | 07:28 | x64 |
| Msvcr80.dll | 8.0.50727.42 | 822,784 | 23-Sep-2005 | 07:26 | x64 |
| Sqlncli.dll | 2005.90.2183.0 | 2,854,744 | 18-Aug-2006 | 12:08 | x64 |
WORKAROUND
To work around this problem, explicitly sign the numeric data that uses the scientific format. To do this, add the plus sign (+) before the exponent value. For example, use "E+10" for the exponent instead of "E10."
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 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: kbqfe kbpubtypekc kbhotfixserver kbsql2005tool KB924344
