Select the product you need help with
FIX: The SQLGetData function may return zero for the actual size of the data that is to be copied when you use the function to retrieve data for a binary column in SQL Server 2005Article ID: 950189 - View products that this article applies to. Bug #: 50002580 (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:
SYMPTOMSConsider the following scenario. On an instance of Microsoft SQL Server 2005, you install Cumulative Update 6 for SQL Server 2005 Service Pack 2 (SP2). You create a table that contains a binary type column, such as an image column. You have an application that uses the SQL Native client ODBC driver to connect to the instance of SQL Server. In the application, you use the SQLGetData function to retrieve the data of the column. In this scenario, the function may return zero for the actual size of the data that is to be copied. This problem occurs when the following conditions are true:
CAUSEThe SQLGetData function lets an application query the size of the data that is to be copied before the application provides a buffer to copy the data. This problem occurs when a user requests the data size of a binary type column by using a buffer size of 0 specified in the SQLGetData function. The function incorrectly returns zero instead of returning the actual size of the data that is to be copied. RESOLUTIONHotfix informationA 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: http://support.microsoft.com/contactus/?ws=support 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesNo prerequisites are required.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 informationThis 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 Native Client, 32-bit versionCollapse this table
SQL Native Client, x64-based versionCollapse this table
SQL Native Client, Itanium-based versionCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONThis issue occurs if the build of the Sqlncli.dll file is 2005.90.3228.0. You can find the Sqlncli.dll file in the %Windir%\System32 directory. Steps to reproduce the problem
822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updatesImportant information for SQL Server 2005 Analysis ServicesA known issue exists in Cumulative Update 7 for SQL Server 2005 Analysis Services. Consider the following scenario. You install Cumulative Update 7 for SQL Server 2005 SP2. In SQL Server Profiler, you start a trace or stop a trace. Then, you run a query. The execution time of the query exceeds the value of the ForceCommitTimeout server setting. In this scenario, all the queries that are running on the server are canceled. To work around this issue, do not run MDX queries before you start a trace or stop a trace.PropertiesArticle ID: 950189 - Last Review: May 6, 2008 - Revision: 3.1 APPLIES TO
|



Back to the top








