Note This build of this cumulative update package is also known as build 10.50.1797.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:
Important notes about the cumulative update package
- SQL Server 2008 R2 hotfixes are now multilingual. Therefore, there is only one cumulative update package for all languages.
- One cumulative update package includes all the component packages. However, the cumulative update package updates only those components that are installed on the system.
How to obtain cumulative update 8 for SQL Server 2008 R2A 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:
SQL Server 2008 hotfixes that are included in cumulative update 8 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 issues, click the following article numbers to view the articles in the Microsoft Knowledge Base:
|VSTS bug number||KB article number||Description|
|730658||2525665||FIX: SQL Server 2008 BIDS stops responding when you stop debugging a SSIS 2008 or a SSIS 2008 R2 package|
|639374||2525665||FIX: SQL Server 2008 BIDS stops responding when you stop debugging a SSIS 2008 or a SSIS 2008 R2 package|
|701471||2530913||FIX: "Error: 17066" occurs when you create a partitioned nonclustered index in SQL Server 2008 R2 if a parallel execution plan is used|
|708511||2535660||FIX: Role membership is synchronized even if the SynchronizeSecurity element is set to the SkipMembership value in SSAS 2008 or in SSAS 2008 R2|
|711297||2537467||FIX: You cannot use SQL Server Management Objects (SMO) to transfer data from a table in SQL Server 2008 or in SQL Server 2008 R2|
|713677||2539098||FIX: "Runtime error: the property DBPROP_MSMD_UPDATE_ISOLATION_LEVEL cannot be found" error when an application tries to create a connection to SSAS 2008 R2|
|702342||2539378||FIX: Replmerg.exe crashes when it enumerates changes to a statement in SQL Server if the stored procedure contains more than 4,000 characters|
|720633||2545989||FIX: "A time-out occurred while waiting for buffer latch" error when many transactions concurrently update a database in SQL Server 2008 R2 if the database uses the snapshot isolation level|
|721958||2547017||FIX: Instances of DAX functions that have no names incorrectly appear when you add a calculated member to a report that uses an SSAS 2008 R2 database as a data source|
|737837||2559662||FIX: Slow performance when you render a report that returns a long string of text in SSRS 2008 R2 if the text contains no carriage return characters|
|738049||2562753||FIX: Slow performance when an MDX query uses unary operators on parent/child hierarchy members in SSAS 2008 R2 if you define a scope calculation on these members and if the query accesses multiple dates in a time dimension|
|722165||2563216||FIX: Dynamic image does not work in a page header or footer in SSRS 2008 R2 if the value expression uses the Global!PageNumber variable|
|704879||2563924||FIX: "The incoming tabular data stream (TDS) protocol stream is incorrect" error when the SQLPutData function inserts the SQL_NULL_DATA value in a TVP in SQL Server 2008 R2|
|709576||2536225||FIX: CLR stored procedure incorrectly returns NULL after it is recompiled in SQL Server 2008 R2|
|721415||2550552||FIX: SQL Server command stops responding when it uses a nonbuffered access path to access a FILESTREAM file in SQL Server 2008 R2|
Cumulative update package information
You may have to restart the computer after you apply this cumulative update.
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
Change or Remove Programs.
- To see all the updates for the SQL Server 2008 R2 installation, click to select the
- Uninstall the cumulative update package.
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:
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:
New naming schema for Microsoft SQL Server software update packages
Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 2534352 - Last Review: May 22, 2012 - Revision: 1