Select the product you need help with
FIX: When you update rows by using a cursor in SQL Server 2008, the update may take a long time to finishArticle ID: 957872 - View products that this article applies to. Bug #: 50003344 (SQL Hotfix) Microsoft distributes Microsoft SQL Server 2008 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 2008 fix release. On This PageSYMPTOMSIn Microsoft SQL Server 2008, you create a cursor. You try to update the cursor by using a statement. The statement includes an ORDER BY clause. When you update rows by using the cursor, the update may take a long time to finish. This problem also occurs in Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 955694
(http://support.microsoft.com/kb/955694/
)
FIX: When you update rows by using a cursor in SQL Server 2005, the update may take a long time to finish
RESOLUTIONThe fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: 956717 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/956717/
)
Cumulative update package 1 for SQL Server 2008956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was releasedAdditional informationThe following sections include important information about the fix.Steps to enable the fixIn SQL Server Configuration Manager, add the -T4128 startup parameter to the instance of SQL Server. To do this, follow these steps:
Issues that the fix addressesThe fix addresses this issue when the following conditions are true:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base: 956717
(http://support.microsoft.com/kb/956717/LN/
)
Cumulative update package 1 for SQL Server 2008REFERENCESFor more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base: 935897
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
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://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 957872 - Last Review: October 15, 2008 - Revision: 1.0
|


Back to the top








