INTRODUCTION
Cumulative Update 3 contains hotfixes for the Microsoft SQL Server 2008 R2 issues that have been fixed since the release of SQL Server 2008 R2.
Note This build of this cumulative update package is also known as build 10.50.1734.0.
We recommend that you test hotfixes before you deploy them in a production environment. 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 R2 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:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Important notes about the cumulative update package
- The hotfixes in this cumulative update package is included in SQL Server 2008 R2 Service Pack 1 (SP1) .
- SQL Server 2008 R2 hotfixes are now multilanguage. Therefore, there is only one cumulative hotfix package for all languages.
- One cumulative hotfix package includes all the component packages. The cumulative update package updates only those components that are installed on the system.
More Information
How to obtain Cumulative Update 3 for SQL Server 2008 R2
A supported cumulative update package is now available from Microsoft. However, it is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems. This cumulative update package may receive additional testing. Therefore, if you are not severely affected by any of these problems, we recommend that you wait for the next SQL Server 2008 R2 service pack that contains the hotfixes in this cumulative update package.
If the cumulative update 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 cumulative update package.
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 cumulative update package. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
SQL Server 2008 hotfixes that are included in Cumulative Update 3 for SQL Server 2008 R2
Microsoft Knowledge Base articles that discuss these hotfixes will be released as they become available.
For more information about the SQL Server bugs, click the following article numbers to view the articles in the Microsoft Knowledge Base:
| VSTS bug number | KB article number | Description |
|---|---|---|
| 458389 | 979212 | FIX: A DateTime value is replaced by a NULL value when a conflict is resolved by using a custom resolver in Microsoft SQL Server 2005, Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2 merge replication |
| 450651 | 980142 | FIX: You receive a "Provider Load Failure" error message or the Wmiprvse.exe process stops responding when you use a SQL Server WMI provider to obtain information about SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 services |
| 459186 | 981811 | FIX: An error occurs when you update the schema of objects that are in a published database in Microsoft SQL Server 2005, Microsoft SQL Server 2008, or Microsoft SQL Server 2008 R2 |
| 459854 | 981814 | FIX: SSMS Object Explorer does not display the correct version number for SSIS or for SSRS |
| 470559 | 981881 | FIX: "The selected data extension <data extension name> cannot be loaded" error message when you use Report Builder 2.0 to run an SSRS 2008 or SSRS 2008 R2 report that uses a custom data processing extension in server mode |
| 459191 | 981888 | FIX: "Deadlock monitor failed to resolve this deadlock. Server may require restart to recover from this condition" error message when a database is being recovered in Microsoft SQL Server 2005, Microsoft SQL Server 2008, or Microsoft SQL Server 2008 R2 |
| 510793 | 982363 | FIX: SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 may require a long time to complete an ALTER TABLE statement that alters an XML data type column from "NOT NULL" to "NULL" in a table |
| 510788 | 982376 | FIX: A non-yielding scheduler error or an error 8623 occurs when you run a query that contains a large IN clause in SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 |
| 510795 | 983429 | FIX: A deadlock occurs when you run a query or a stored procedure that contains an XML column in SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 |
| 510805 | 983480 | FIX: Various issues occur when a database is involved in a database mirroring session and in a transactional replication if trace flag 1448 is enabled |
| 510809 | 983500 | FIX: The role synchronization process is delayed when a mirroring automatic failover occurs in SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 |
| 522809 | 2121407 | FIX: Error message when you use the sqlcmd utility to execute the Transact-SQL query in SQL Server 2008 R2 |
| 501090 | 2142496 | FIX: A SQL Server 2008 R2 Integration Services package does not run in SQL Server Business Intelligence Development Studio when you use a shared SQL configuration table |
| 505486 | 2225696 | FIX: You fail to import data table from SQL Server by using PowerPivot in Excel 2010 |
| 504425 | 2269585 | FIX: SharePoint services and SharePoint Server Enterprise Site Collection features are disabled after you uninstall the PowerPivot for SharePoint component on a computer that is running SQL Server 2008 R2 |
| 517278 | 2270925 | FIX: PowerPivot workbooks are always loaded to the PowerPivot server that is last added to the SharePoint farm despite the use of server health based allocation or round-robin allocation |
| 519523 | 2276203 | FIX: It takes a long time to open a SQL Server 2008 R2 Reporting Services report that contains many parameter values in Internet Explorer |
| 520213 | 2277078 | FIX: The TokenAndPermUserStore cache store size continues to grow when you enable a SQL Server audit in SQL Server 2008 R2 |
| 499445 | 2282505 | FIX: Business Intelligence Development Studio 2008 R2 does not generate an RDL.DATA file when you preview a SQL Server report |
| 524153 | 2283036 | FIX: Forms-based authentication does not work in SQL Server 2008 R2 Reporting Services |
| 524160 | 2283051 | FIX: "The item '/微软丬å½' cannot be found. (rsItemNotFound)" error message when you click the Folder Settings button in Microsoft SQL Server 2008 R2 Reporting Services |
| 524175 | 2283072 | FIX: A hotfix is available that enables SQL Server 2008 R2 Reporting Services to use a 2048-bit RSA key to encrypt a Reporting Services key for FIPS compliancy |
| 524183 | 2283091 | FIX: BIDS crashes when you use the Map Layer wizard to add sptial data in SQL Server 2008 R2 Reporting Services |
| 524211 | 2283186 | FIX: "Requested value 'Unknown' was not found" error message when you update a parameter for a SQL Server 2008 R2 report in SharePoint Server 2010 |
| 503721 | 2285711 | FIX: A fix is available that improves the manageability of SSMS 2008 R2 to support Spatial Types for SQL Azure |
| 503718 | 2285720 | FIX: A fix is available for SQL Server Management Studio 2008 R2 that enables you to rename SQL Azure databases in Object Explorer |
| 499641 | 2290377 | FIX: The Report Definition Customization Extension does not modify the RDL file as expected in SQL Server 2008 R2 |
| 468919 | 2292807 | FIX: "USE statement is not supported to switch between databases" error message when you run a custom report in SQL Server 2008 R2 Management Studio |
| 527837 | 2297903 | FIX: Event ID 322 is logged when a server audit is outputted in SQL Server 2008 R2 |
| 536696 | 2315727 | FIX: You cannot create, add, or edit steps for an SQL Server Agent job in SQL Server Management Studio 2008 R2 |
| 508217 | 2268122 | FIX: "User 'guest' does not have permission to run DBCC checkdb for database 'mssqlsystemresource'" error message when you run the DBCC CHECKDB('master') command on a computer that is running SQL Server 2005 |
Cumulative update package information
Restart information
You may have to restart the computer after you apply this cumulative update.
Registry information
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
How to uninstall the cumulative update package
To uninstall the cumulative update package, follow these steps:
In Control Panel, open the
Add or Remove Programs
item.Click
Change or Remove Programs
.To see all the updates for the SQL Server 2008 R2 installation, click to select the
Show Updates
check box.Uninstall the cumulative hotfix package.
References
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
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
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