Note The build number of this cumulative update package is 10.50.4260.0.
We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 update release. We recommend that you consider applying the most recent update 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 this cumulative update package
- SQL Server 2008 R2 hotfixes are now multilingual. Therefore, the cumulative update package is not specific to one language and applies to all supported 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 this cumulative update packageA 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, go to the following Microsoft website:
Hotfixes that are included in this cumulative update packageMicrosoft 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|
|956228||2543687||FIX: Errors when a client application sends an attention signal to SQL Server 2008 or SQL Server 2008 R2|
|956225||2554905||FIX: "File error: Data may have been lost" error message when you use Excel 2010 to open an Excel report file that was exported from SSRS 2008, from SSRS 2008 R2 or from SSRS 2012|
|969181||2618676||FIX: Transaction log backup is created even though the full backup is canceled in SQL Server 2008 or in SQL Server 2008 R2|
|980532||2625768||FIX: A database page is copied into a database snapshot even though the page is not updated when you perform a read operation in SQL Server 2008 or in SQL Server 2008 R2|
|956212||2637802||FIX: Pages of an SSRS 2008 R2 or an SSRS 2012 report are delivered incorrectly if you use the ReportExecutionService.Render method to render the report in image format or in EMF format|
|980515||2658474||FIX: Incorrect results when the SqlConnection.GetSchema method retrieves a table's schema information in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012|
|969183||2661644||FIX: Access violation in the sqlservr!ReplicaToPrimaryPageCopier::ReadIoCompletionRoutine function in SQL Server 2008 R2|
|956226||2665649||FIX: "bufferLen >= colLen" assertion when you run a parallel query in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012|
|969185||2667037||FIX: "The connection string format is not valid" error when you try to create a maintenance plan for a SQL Server 2008 R2 server|
|980534||2673997||FIX: "The index data is damaged" error message when you run an MDX query against a dimension or partition in SSAS 2008, in SSAS 2008 R2 or in SSAS 2012|
|980525||2674636||FIX: The size of a database file is not reduced when you use the DBCC SHRINKFILE command in SQL Server 2008 R2|
|956218||2675233||FIX: Slow performance when you run an MDX query that uses some sub queries in SSAS 2008 R2 or in SSAS 2012|
|956213||2675522||FIX: Access violation when you run DML statements against a table that has partitioned indexes in SQL Server 2008 R2 or in SQL Server 2012|
|956224||2678796||FIX: You cannot search a Word document or an Excel workbook that is exported from an SSRS 2008 R2 or an SSRS 2012 report by using a keyword in the content of the document or of the workbook in SharePoint 2010|
|956221||2679342||FIX: The field list of the dataset disappears unexpectedly when a report uses a query as a dataset that includes named parameters in SQL Server 2008 R2 or in SQL Server 2012|
|956229||2682819||FIX: SQL Server 2008 R2 may stop responding when you perform many Update Cube writeback transactions on multiple cubes that belong to different SSAS 2008 R2 or SSAS 2012 databases|
|956204||2685132||FIX: The log shipping restore job restores a corrupted transaction log backup to a secondary database when you run a log shipping backup job on an instance of SQL Server 2008 R2 or an instance of SQL Server 2012|
|956230||2689903||FIX: A non-convergence occurs when you run a merge replication publication that uses web synchronization if the value of a column is NULL in SQL Server 2008 R2 or in SQL Server 2012|
|980517||2696161||FIX: Error message when you try to view a report in SSRS 2008 R2: "Different query parameters resulted in a same hash"|
|969189||2697983||FIX: An incorrect value is stored in the TIME_ZONE column of the BACKUPSET table in SQL Server 2008 R2|
|956215||2698639||FIX: Performance of a SELECT statement that contains a LIKE operator and an ESCAPE clause is low in SQL Server 2008 R2|
|969191||2699013||FIX: SQL Server 2008 R2 or SQL Server 2008 stops responding and a "Non-yielding Scheduler" error is logged|
|956206||2700227||FIX: Error message when you try to create a data service document in a data feed library from a sub-site collection in SharePoint 2010 to publish Atom feeds: "There is no file with URL"|
|980529||2703152||FIX: Access violation when you call a CLR stored procedure that references a user-defined table type parameter in SQL Server 2012 or in SQL Server 2008 R2|
|969193||2703214||FIX: SQL Server 2008 R2 may not accept the client connection request when you perform a bulk insert and an OS error occurs|
|969195||2706519||FIX: An exception occurs when the SqlCommandBuilder.DeriveParameters method is used to retrieve parameter information from a CLR stored procedure in SQL Server 2008 R2|
|969197||2706601||FIX: Series groups in a report are missing when you render the report in SQL Server 2008 Reporting Services or in later versions of Reporting Services|
|969199||2707015||FIX: rsInternalError error when you export a report that contains a Tablix control in SSRS 2008 R2|
|969201||2708027||FIX: "An error has occurred during report processing" error message when you try to preview an SSRS 2008 R2 report after you set the dataset collation to Greek or Greek_100|
|969203||2708726||FIX: Performance Monitor .dll files in the system32 folder are not updated after you apply updates to SQL Server 2008 R2|
|969207||2713501||FIX: A deadlock occurs when you alter a partition and run a statement against the partition at the same time in SQL Server 2008 R2|
|969209||2714634||FIX: SQL Server 2008 R2 takes a long time to generate scripts for a partitioned table that uses the data compression feature|
|969213||2715289||FIX: Incorrect results when you convert a datetimeoffset column to a smalldatetime column in SQL Server 2008 R2 when there is an index on the datetimeoffset column|
|969211||2715312||FIX: Errors when you run a query that uses the FOR XML clause in the PATH mode in SQL Server 2008 R2|
Cumulative update package information
You might have to restart the computer after you apply this cumulative update package.
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
How to uninstall this cumulative update packageTo uninstall this cumulative update package, follow these steps:
- In Control Panel, open the Add or Remove Programs item.
Note If you are running Windows 7, open the Programs and Features item in Control Panel.
- Locate the entry that was installed by this cumulative update package.
- Right-click the entry and select Uninstall to remove 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: 2720425 - Last Review: Aug 6, 2013 - Revision: 1