List of the bugs that are fixed in SQL Server 2008 R2 Service Pack 2 CTP

Article ID: 2630455
Expand all | Collapse all

On This Page

INTRODUCTION

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

Notes
  • This is a CTP version of SQL Server 2008 R2 SP2. This version is not supported by Microsoft Customer Support Services. For more information about how to submit feedback, visit the following Microsoft Connect website:
    Microsoft SQL Server Connect website
  • 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 CTP version of the 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.
Collapse this tableExpand this table
VSTS bug number KB article number Description
820875 922578 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
728527 2216456 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
820858 2550375 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
820878 2565683 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
820756 2588050 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
901689 2653857 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

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 CTP.
Collapse this tableExpand this table
VSTS bug numberDescription
820845 The fix is related to usage of BindParameter method and the reference of long type parameters that are used by this method.
852397 The fix is to update UpgradeIncompleteFeatureConfigEventHandler.cs to include RebuildDatabase scenario when you reset ConfigurationState.
887672 For document libraries with the “Opening Documents in the Browser” setting set to “Open in the client application” GetSnapshot.exe ignore the configuration and always displays the workbook by using Excel Services as if the setting was “Open in the browser”.
820805 FIX: On a Russian Localized build of the Reporting Services Configuration Manager, Execution Account information that is contained clipped strings.
718430 The ExpectedCount and ExpectedElapsedMs usage counts are updated to reflect the actual counts respectively.
737914 Fixes an issue in which SQL Server 2008 R2 Analysis Services crashes during the database synchronization.
788389 Trace flag 1264 is removed and 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.
820762 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 of the FireAgain parameter is only determined by the external event listener. After you apply this hotfix, the issue is resolved.
820764 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 switches the partitions.
820792 Fixes an issue in which an object that is allocated on a SOS_Task PMO could be also used by other TASK which has a different life span. This service pack uses the correct PMO for allocating the object.
820796 After you apply the hotfix, the optimizer understands that CRYPT_GEN_RANDOM can return different outputs for the same input.
820859 Fixes an issue in which an incorrect value is returned when you run the SCOPE_IDENTITY().
820864 Fixes an issue in which the SQL Server 2008 R2 setup crashes when you install SxS with Shiloh OLAP SP3a. This issue occurs because the Shiloh OLAP SP3a incorrectly writes the version registry key as "Service Pack 3.0."
820873 Fixes an issue in which an incorrect CPU time is reported by sys.dm_exec_query_stats when parallel query plans are involved.
820880 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.
847805 The fix will only use the synchronization if the SQLWixCompilerExtension operation runs in candle.
890643 This fix changes the HierarchyGet operation to avoid a certain code path for the explicit cap that only applies to the derived part of the hierarchy. The update is a one-line update that is low risk.
731796Fixes an issue in which you receive errors in a statement when purging from snapshots.notable_query_text.
820829Bad GUID values parsed from flat files could cause errors. The fix is to fall back into a truncation mode if the source buffer is bigger than max size of a GUID string.

REFERENCES

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:
321185 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.

Properties

Article ID: 2630455 - Last Review: May 14, 2012 - Revision: 1.0
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2630455

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com