Note This build number of this cumulative update package is 10.50.4270.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 SP2 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 SP2 hotfixes are now multilingual. 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.
How to obtain Cumulative Update 4 for SQL Server 2008 R2 SP2A 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:
Hotfixes that are included in this cumulative update package
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|
|1043439||2731068||FIX: "An unexpected error occurred" when you query some calculation data of an SSAS tabular model by using SQL Server 2008 R2 PowerPivot for Excel 2010 or SQL Server 2008 R2 PowerPivot for SharePoint 2010|
|1049062||2755192||FIX: SSMS freezes when you perform management operations that relate to roles to an SSRS 2008 R2 database|
|1061516||2715512||FIX: Error messages when you use dtexec to execute packages in SSIS 2008, in SSIS 2012 or in SSIS 2008 R2|
|1072675||2765785||FIX: Access violation when you execute an SSIS 2008 R2 package that contains a Sort transformation on a computer that has multiple CPUs|
|1076490||2770630||FIX: Error message when you run UPDATE CUBE and SELECT MDX statements at the same time in SSAS 2008 R2|
|1077962||2770258||FIX: You receive an incorrect result when you run a query against a partitioned table in SQL Server 2008 R2|
|1079200||2770635||FIX: Incorrect result when you run an MDX query against an SSAS 2008 R2 database that has multiple data sources|
|1080450||2708012||FIX: Event ID 833 if I/O write operation occurs during a VSS snapshot backup in SQL Server 2008 R2|
|1080453||2744760||FIX: Empty or incomplete tree view is shown in the Process Progress window when you process an SSAS object in SSMS or BIDS in SQL Server 2008 R2|
|1080456||2761600||FIX: Text is truncated in a Tablix control in an report of SSRS 2008 R2 or SQL Server 2012 after you export the report as a PDF or image file|
|1080459||2749560||FIX: "SQL Server Assertion: File: <bcmdsink.cpp>, line=<n> Failed Assertion = 'src'" error message when you update BLOB data in SQL Server 2008 R2 or in SQL Server 2012|
|1080462||2749913||FIX: Unhandled exception when you use a marked transaction that spans multiple databases in SQL Server 2008 R2 or in SQL Server 2012|
|1080465||2754301||FIX: Large queries that modify data run slower than expected when many locks accumulate in a SQL Server 2008 R2 or in SQL Server 2012|
|1080468||2754800||FIX: Error 17066 when you replicate a table article that contains an ntext data type column in SQL Server 2008 R2 or in SQL Server 2012|
|1080471||2757344||FIX: Business Intelligence Development Studio (BIDS) crashes when you select a WSDL file in SQL Server 2008 R2|
|1080474||2757356||FIX: "The component is waiting for a notification" error message and SSIS 2012 or SSIS 2008 R2 package stops responding when you use Microsoft Connector 1.1 for SAP BI to extract data from SAP BW|
|1090691||2776344||FIX: Deadlock when you execute a stored procedure to alter a temporary table if lock partitioning is enabled in SQL Server 2008 R2|
|1101721||2778479||FIX: 17066 and 3624 errors when you run the sp_refreshview stored procedure in a large batch that performs binary large object-related operations in SQL Server 2008 R2|
|1113309||2780146||FIX: "Incorrect syntax near 'IDENTITY_VALUE'" error when you try to decrypt data that is migrated from another database in SQL Server 2008 R2|
|1121899||2781008||FIX: "User cannot be found" error message in SSRS 2008 R2 after the logon name is changed in Active Directory|
|1122011||2777963||FIX: Installation fails when you try to install a cumulative update to an instance of SQL Server 2008 R2|
|1125937||2787595||FIX: An error occurs when you load a thesaurus file in SQL Server 2008 R2 that uses DBCS collation|
|1131076||819546||SQL Server support for mounted volumes|
|1131695||2785079||FIX: A "non-yielding" error occurs on a server for Service Broker Message Forwarding in SQL Server 2008 R2|
|1132143||2784686||FIX: An access violation occurs when you query the missing indexes DMVs in SQL Server 2008 R2|
|1133922||2696161||FIX: Error message when you try to view a report in SSRS 2012, in SSRS 2008 R2 or in SSRS 2008: "Different query parameters resulted in a same hash"|
|1133927||2756471||FIX: Incorrect result is returned when you query an indexed view by using the NOEXPAND hint in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012|
|1133935||2770891||FIX: "Non-yielding Scheduler" error message when you insert a record that contains large object (LOB) data into a snapshot database in SQL Server 2008 or in SQL Server 2008 R2|
|1133939||2761934||Support for the varchar(max), nvarchar(max), and varbinary(max) data types is added in most OLE DB providers in SQL Server 2012 or in SQL Server 2008 or in SQL Server 2008 R2|
|1133943||2509302||A database transaction log continues to grow after you upgrade to SQL Server 2012, SQL Server 2008 R2 SP1, SQL Server 2008 SP2 or SQL Server 2008 SP3|
|1133947||2770837||FIX: "Windows NT user or group 'Domain_name\User_name' not found" error message when you add a login to a case-sensitive SQL Server 2008 instance or SQL Server 2008 R2 instance|
|1133952||2778088||FIX: Memory leak if you enable the AUTO_UPDATE_STATISTICS_ASYNC statistics option in SQL Server 2008, in SQL Server 2012 or in SQL Server 2008 R2|
|1140412||2788362||FIX: Error 28921 and error 18054 when you start an instance of SQL Server 2008 R2 that is upgraded from SQL Server 7.0|
|1113033||An access violation may occur in SQL Server when a thread that is waiting on NETWORKIO is chosen as a deadlock error.|
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 this cumulative update packageTo uninstall this cumulative update package, follow these steps:
- In Control Panel, open the Add or Remove Programs
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 then 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:
Naming schema for Microsoft SQL Server software update packages
Description of the standard terminology that is used to describe Microsoft software updates