|
 |
 |
 |
|
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
FIX: When you use SQL Native Client to retrieve data from a column of the sql_variant data type in SQL Server 2005, an incorrect data type is returned| Article ID | : | 953946 | | Last Review | : | June 30, 2008 | | Revision | : | 1.0 |
Bug #: 50002687 (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. On This PageSUMMARYThis 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 |
 Back to the top
SYMPTOMS Consider the following scenario. An application uses SQL
Native Client to connect to an instance of Microsoft SQL Server 2005. In the
application, you retrieve data from a column of the sql_variant data type.
You call the SQLColAttribute function to determine the data type for the data. In this scenario, an
incorrect data type is returned. Note This problem does not occur
if you use
the ODBC driver to retrieve data from the column of
the sql_variant data type. Back to the top RESOLUTIONHotfix 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 To apply this hotfix, you must have SQL Server 2005 Service Pack
2 (SP2) installed.
For more information about how to obtain SQL Server 2005 Service Pack
2, click the following article number to view the article in the Microsoft Knowledge Base:
913089 (http://kbalertz.com/Feedback.aspx?kbNumber=913089/)
How to obtain the latest service
pack for SQL Server 2005
Restart informationYou do not have to restart the computer after you apply this hotfix. Registry informationYou do not have to change the registry. Hotfix file information
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 Native Client, 32-bit version| File name | File version | File
size | Date | Time | Platform |
|---|
| Msvcm80.dll | 8.0.50727.42 | 479,232 | 22-Sep-2005 | 15:48 | x86 | | Msvcp80.dll | 8.0.50727.42 | 548,864 | 22-Sep-2005 | 15:48 | x86 | | Msvcr80.dll | 8.0.50727.42 | 626,688 | 22-Sep-2005 | 15:48 | x86 | | Msvcm80.dll | 8.0.50727.42 | 479,232 | 22-Sep-2005 | 15:48 | x86 | | Msvcp80.dll | 8.0.50727.42 | 548,864 | 22-Sep-2005 | 15:48 | x86 | | Msvcr80.dll | 8.0.50727.42 | 626,688 | 22-Sep-2005 | 15:48 | x86 | | Msvcm80.dll | 8.0.50727.42 | 479,232 | 22-Sep-2005 | 15:48 | x86 | | Msvcp80.dll | 8.0.50727.42 | 548,864 | 22-Sep-2005 | 15:48 | x86 | | Msvcr80.dll | 8.0.50727.42 | 626,688 | 22-Sep-2005 | 15:48 | x86 | | Sqlncli.dll | 2005.90.3257.0 | 2,242,584 | 12-Jun-2008 | 17:07 | x86 | | Sqlnclir.rll | 2005.90.1399.0 | 205,528 | 13-Oct-2005 | 19:48 | Not
applicable |
SQL Native Client, x64-based version| File name | File version | File
size | Date | Time | Platform |
|---|
| Msvcm80.dll | 8.0.50727.42 | 479,232 | 22-Sep-2005 | 15:48 | x86 | | Msvcp80.dll | 8.0.50727.42 | 548,864 | 22-Sep-2005 | 15:48 | x86 | | Msvcr80.dll | 8.0.50727.42 | 626,688 | 22-Sep-2005 | 15:48 | x86 | | Msvcm80.dll | 8.0.50727.42 | 479,232 | 22-Sep-2005 | 15:48 | x86 | | Msvcp80.dll | 8.0.50727.42 | 548,864 | 22-Sep-2005 | 15:48 | x86 | | Msvcr80.dll | 8.0.50727.42 | 626,688 | 22-Sep-2005 | 15:48 | x86 | | Msvcm80.dll | 8.0.50727.42 | 479,232 | 22-Sep-2005 | 15:48 | x86 | | Msvcp80.dll | 8.0.50727.42 | 548,864 | 22-Sep-2005 | 15:48 | x86 | | Msvcr80.dll | 8.0.50727.42 | 626,688 | 22-Sep-2005 | 15:48 | x86 | | Msvcm80.dll | 8.0.50727.42 | 516,096 | 22-Sep-2005 | 15:27 | x64 | | Msvcp80.dll | 8.0.50727.42 | 1,097,728 | 22-Sep-2005 | 15:28 | x64 | | Msvcr80.dll | 8.0.50727.42 | 822,784 | 22-Sep-2005 | 15:26 | x64 | | Msvcm80.dll | 8.0.50727.42 | 516,096 | 22-Sep-2005 | 15:27 | x64 | | Msvcp80.dll | 8.0.50727.42 | 1,097,728 | 22-Sep-2005 | 15:28 | x64 | | Msvcr80.dll | 8.0.50727.42 | 822,784 | 22-Sep-2005 | 15:26 | x64 | | Sqlncli.dll | 2005.90.3257.0 | 2,763,288 | 12-Jun-2008 | 16:18 | x64 | | Sqlnclir.rll | 2005.90.1399.0 | 206,040 | 14-Oct-2005 | 06:31 | Not
applicable | | Sqlncli.dll | 2005.90.3257.0 | 2,242,584 | 12-Jun-2008 | 17:07 | x86 | | Sqlnclir.rll | 2005.90.1399.0 | 205,528 | 13-Oct-2005 | 19:48 | Not
applicable |
SQL Native Client, Itanium-architecture version| File name | File version | File
size | Date | Time | Platform |
|---|
| Msvcm80.dll | 8.0.50727.42 | 479,232 | 22-Sep-2005 | 15:48 | x86 | | Msvcp80.dll | 8.0.50727.42 | 548,864 | 22-Sep-2005 | 15:48 | x86 | | Msvcr80.dll | 8.0.50727.42 | 626,688 | 22-Sep-2005 | 15:48 | x86 | | Msvcm80.dll | 8.0.50727.42 | 479,232 | 22-Sep-2005 | 15:48 | x86 | | Msvcp80.dll | 8.0.50727.42 | 548,864 | 22-Sep-2005 | 15:48 | x86 | | Msvcr80.dll | 8.0.50727.42 | 626,688 | 22-Sep-2005 | 15:48 | x86 | | Msvcm80.dll | 8.0.50727.42 | 479,232 | 22-Sep-2005 | 15:48 | x86 | | Msvcp80.dll | 8.0.50727.42 | 548,864 | 22-Sep-2005 | 15:48 | x86 | | Msvcr80.dll | 8.0.50727.42 | 626,688 | 22-Sep-2005 | 15:48 | x86 | | Msvcm80.dll | 8.0.50727.42 | 572,416 | 22-Sep-2005 | 15:29 | IA-64 | | Msvcp80.dll | 8.0.50727.42 | 1,385,472 | 22-Sep-2005 | 15:31 | IA-64 | | Msvcr80.dll | 8.0.50727.42 | 1,484,800 | 22-Sep-2005 | 15:28 | IA-64 | | Msvcm80.dll | 8.0.50727.42 | 572,416 | 22-Sep-2005 | 15:29 | IA-64 | | Msvcp80.dll | 8.0.50727.42 | 1,385,472 | 22-Sep-2005 | 15:31 | IA-64 | | Msvcr80.dll | 8.0.50727.42 | 1,484,800 | 22-Sep-2005 | 15:28 | IA-64 | | Sqlncli.dll | 2005.90.3257.0 | 5,443,608 | 12-Jun-2008 | 19:47 | IA-64 | | Sqlnclir.rll | 2005.90.1399.0 | 205,016 | 14-Oct-2005 | 06:39 | Not
applicable | | Sqlncli.dll | 2005.90.3257.0 | 2,242,584 | 12-Jun-2008 | 17:07 | x86 | | Sqlnclir.rll | 2005.90.1399.0 | 205,528 | 13-Oct-2005 | 19:48 | Not
applicable |
Back to the top STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. Back to the top MORE INFORMATIONSteps to reproduce this problem| 1. | In an application, use SQL Native Client to connect to an
instance of SQL Server 2005. | | 2. | Call the SQLColAttribute function to determine the real
data type for the data that is returned by the following statement. SELECT DATABASEPROPERTYEX(name, 'status') AS [Status] FROM master..sysdatabases |
The return type of the DATABASEPROPERTYEX function is
sql_variant. The real data type is nvarchar(128). However, when you call the
SQLColAttribute function to determine the real data type of the data that is
returned by the DATABASEPROPERTYEX function, the function returns SQL_BINARY
instead of SQL_CHAR. 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 (http://kbalertz.com/Feedback.aspx?kbNumber=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 (http://kbalertz.com/Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates Back to the top
APPLIES TO| • | Microsoft SQL Server 2005 Standard Edition | | • | Microsoft SQL Server 2005 Developer Edition | | • | Microsoft SQL Server 2005 Enterprise Edition | | • | Microsoft SQL Server 2005 Standard X64 Edition | | • | Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems | | • | Microsoft SQL Server 2005 Enterprise X64 Edition | | • | Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems | | • | Microsoft SQL Server 2005 Workgroup Edition |
Back to the top | kbsql2005connect kbautohotfix kbhotfixrollup kbfix kbpubtypekc kbqfe kbexpertiseadvanced kbhotfixserver KB953946 |
Back to the top 
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please
|
|
 |
|
 |
|
|
|
| |