Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


This article lists the bugs that are fixed in Microsoft SQL Server 2008 R2 Service Pack 2 (SP2).


  • Other fixes that are not documented may also be included in the service pack.

  • This list will be updated when more articles are released.

For more information about how to obtain SQL Server 2008 R2 service packs, click the following article number to view the article in the Microsoft Knowledge Base:

2527041 How to obtain the latest service pack for SQL Server 2008 R2

More Information

In addition to the fixes that are listed in this article, SQL Server 2008 R2 SP2 contains the hotfixes that were included in Cumulative Update 1 through Cumulative Update 5 for SQL Server 2008 R2 Service Pack 1 (SP1).

Note If you are upgrading from SQL Server 2008 R2 SP1 Cumulative Update 6, you must apply a post-SQL Server 2008 R2 SP2 cumulative update after you upgrade to SQL Server 2008 R2 SP2 to obtain all the fixes.

For more information about the cumulative update packages that are available for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

The issues that are fixed in this service pack

For more information about the bugs that are fixed in SQL Server 2008 R2 SP2, click the following article numbers to view the articles in the Microsoft Knowledge Base.

VSTS bug number

KB article number




FIX: Lots of messages that have message ID 19030 and message ID 19031 are logged in SQL Server 2005, SQL Server 2008 or SQL Server 2008 R2 Errorlog file when you use SQL Server Profile in SQL Server 2005, in SQL Server 2008 or in SQL Server 2008 R2



SQL Server 2008 Service Pack 2 and SQL Server 2008 R2 Service Pack 2 enhancements to the "Operation has been cancelled" error message text in Analysis Services



FIX: Deadlock might occur in sys.dm_database_encryption_keys DMV in SQL Server 2008 R2 when you run log shipping from many databases to one secondary server



FIX: You may receive incorrect results when you run a complex query that contains aggregates functions, join functions, and distinct functions in subqueries in a SQL Server 2008 or SQL Server 2008 R2 environment



FIX: Slipstream installation of a SQL Server 2008 or SQL Server 2008 R2 service pack fails when you add new features to the SQL instance if database engine is installed



FIX: You cannot connect to SQL Server by using JDBC Driver for SQL Server after you upgrade to JRE 6 update 29 or a later version



FIX: Backup operation fails in a SQL Server 2008, in a SQL Server 2008 R2 or in a SQL Server 2012 database after you enable change tracking



FIX: Latch time-out error when you have heap tables and when data compression is enabled in SQL Server 2008 R2 or in SQL Server 2012


Additional issues that are fixed in this CTP version of the service pack

Resolutions to the following issues are also included in SQL Server 2008 R2 SP2. 

VSTS bug number



elated to usage of the BindParameter method and the reference of long type parameters that are used by this method.


Updates UpgradeIncompleteFeatureConfigEventHandler.cs to include RebuildDatabase scenario when you reset ConfigurationState.


For document libraries with the "Opening Documents in the Browser" setting set to "Open in the client application," GetSnapshot.exe ignores the configuration and always displays the workbook by using Excel Services as if the setting was "Open in the browser."


FIX: On a Russian localized build of the Reporting Services Configuration Manager, Execution Account information contains clipped strings.


The ExpectedCount and ExpectedElapsedMs usage counts are updated to reflect the actual counts.


Fixes an issue in which SQL Server 2008 R2 Analysis Services crashes during database synchronization.


Trace flag 1264 is removed so that the process name is collected by default in non-yielding scenario dumps. The number of thread records in non-yielding scenario dump files is increased from 1K to 16K.


SQL Server 2008 R2 changes the FireAgain parameter to True if an event should be logged. However, after some codes are removed by mistake, some logs are missing because the FireAgain parameter is determined only by the external event listener. After you apply this hotfix, the issue is resolved.


Consider the following scenario. You have indexed view projects columns from base and non-base tables in SQL Server 2008 R2. A column from the non-base table has the same order ID and type as a column of the base table. In this scenario, SQL Server 2008 R2 switches the partitions. After you apply the hotfix, SQL Server 2008 R2 experiences an error instead of switching the partitions.


Fixes an issue in which an object that is allocated on a SOS_Task PMO could be also used by another TASK that has a different life span. This service pack uses the correct PMO for allocating the object.


After you apply the hotfix, the optimizer understands that CRYPT_GEN_RANDOM can return different outputs for the same input.


Fixes an issue in which an incorrect value is returned when you run SCOPE_IDENTITY().


Fixes an issue in which the SQL Server 2008 R2 setup crashes when you install SxS with Shiloh OLAP SP3a. This issue occurs because Shiloh OLAP SP3a incorrectly writes the version registry key as "Service Pack 3.0."


Fixes an issue in which an incorrect CPU time is reported by sys.dm_exec_query_stats when parallel query plans are involved.


Fixes an issue that occurs when internal asynchronous file-reading buffers are splitting the multi-character column delimiter in two parts. The fix is to correctly reset the current parsing pointer after buffers are switched.


Uses the synchronization only if the SQLWixCompilerExtension operation runs in candle.


Changes the HierarchyGet operation to avoid a certain code path for the explicit cap that applies only to the derived part of the hierarchy. The update is a one-line update that is low risk.


Fixes an issue in which you receive errors in a statement when you purge from snapshots.notable_query_text.


Bad GUID values that are parsed from flat files could cause errors. The fix is to fall back into a truncation mode if the source buffer is larger than the maximum size of a GUID string.


Recalculates latch promotion threshold periodically to avoid variation because of a calculation error at startup.


The suggested fix is matching calling conventions between caller and the person who is called.


Fixes a crash during startup when the computer has an empty processor slots or the restart option /setgroupsize is used.


Reduces the time during which the latch backs off when it experiences spinlock. This helps improve performance


Fixes a race condition during XE session startup that could cause SQL Server crashes.


For more information about how to determine the current SQL Server version and edition, click the following article number to view the article in the Microsoft Knowledge Base:

How to identify your SQL Server version and edition
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!