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 the Community Technology Preview (CTP) version of Microsoft SQL Server 2008 R2 Service Pack 1 (SP1).


  • This is a CTP release of Microsoft SQL Server 2008 R2 SP1. This version is not supported by Microsoft Customer Support Services. You can submit your feedback from the following Microsoft Connect website:

    Microsoft SQL Server Connect

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

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

For more informationabout 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 SP1 CTP contains the hotfixes that were included in Cumulative Update 1 through Cumulative Update 6 for SQL Server 2008 R2.
For more information about the cumulative update packages that are available for SQL Server 2008 R2 SP1 CTP, click the following article number to view the article in the Microsoft Knowledge Base:

981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

The bugs that are fixed in this service pack

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

Fixes in this service pack

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

VSTS bug number

KB article number




The target server cannot download a multiserver job from the master server if the target server is running a German version or a French version of SQL Server 2005



Error message when you run Get-Command in a PowerShell version 2 environment on a server that is running SQL Server 2008: "Object reference not set to an instance of an object"



FIX: Resource Monitor enters a non-yielding condition on a server that is running SQL Server 2008



Concern for 2008 SP2 [SQL Server Destination [19]] Error: Unable to prepare the SSIS bulk insert for data insertion



FIX: Spatial Storage geometry polygon data types with internal rings return incorrect data through different geometric operations



FIX: Multiserver jobs are not downloaded from SQL Server 2000 in the MSX role to SQL Server 2008 in the TSX role



FIX: The locks of a table are not escalated when you insert many rows into a table in SQL Server 2008



FIX: A database enabled for Transparent Data Encryption may become inaccessible if the Certificate used to encrypt Database Encryption Key is dropped.



FIX: Hidden text box value referenced in the Tablix header is displayed only on the first page after you export a report to a hard page-break renderer



DataSet Filters Applied Durng SharedDataSet or Parameter processing use incorrect collation settings



FIX: A clustering model that uses the K-means algorithm generates different results that are affected by PredictOnly columns in SQL Server 2008 R2 Analysis Services



FIX: Access violation when you insert data into a new partition of a partitioned table after you drop a column of the table in SQL Server 2008 R2



The SQL Dumper utility cannot generate error dump files on a SQL Server 2008 or SQL Server 2008 R2 failover cluster on an Advanced/Enterprise Failover Cluster install



Error message when you try to open a project in SQL Server 2008 or in SQL Server 2008 R2: "The located assembly's manifest definition does not match the assembly reference"



You get "Cannot stop ReportServer service on computer <Computer name>" when switching from Connected mode to Local Mode



You receive an error message when you try to browse directly to the SSRS 2008 R2 report server after you create a SharePoint claim site

Additional fixes in this service pack

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




The HTML renderer no longer throws an ArgumentOutOfRangeException exception if a report has the ConsumeContainerWhitespace property set to TRUE and if there is a horizontal white-space available to fill.


FIX: The "FORCESEEK" index hint syntax now takes optional parameters. A new FORCESCAN query hint is added. For more information, see "Query Hints (Transact-SQL)" (


Connection strings such as 'server="tcp:"' and 'server="np:"' are supported in SQL Server Native Client 2008 to make connections to the local instance. With this fix, these connection strings now work in SQL Server Native Client 2008 R2 and allow for connections to the local instance.


An issue in the logic checking no longer occurs if a partitioned column of an indexed view matches the partitioned column of the base partitioned table. Alter table switching is no longer enabled in non-partition aligned indexed views.


Using SQL 10.5 BIDS to deploy report parts to a SQL Server 2008 R2 (and later versions) Report Server no longer fails or generates a SQL versioning error message.


Timestamps are now correct when Extended Events or SQL Audit files are read on a different computer than the one that produced the file. Timestamps are now also correct after a server restart.


Render report in Synchronous display mode by using Reporting Services 2008 R2 web parts are now viewable if the report contains spaces in the report name. A StreamNotFound error message is no longer generated.


When you display to HTML by having the “StyleStream” DeviceInfo setting set to TRUE, style settings are no longer lost on textboxes or on text if actions are defined.


Two new trace template files are generated for the engine and analysis services. This lets Profiler display all the events and columns for both the engine and the analysis services.


FIX: Incorrect text reporting when the SP 2010 Health Analyzer returns an error message about Analysis Services That Are Running in VertiPaq mode.


In a Tablix report item that has 20 or more rows that contain nested container report items (Rectangle and Tablix), the BIDS shell no longer becomes unresponsive if you insert a new row above or below any tablix member.


The out-of-order message no longer causes an access violation error when the DBM object starts.


The New Server Installation no longer reports that a Secure Store master key does not generate when the BI Appliance is installed. (The message was generated even though the installation was successful.)


Fixed an issue in which you receive an error message when the query optimizer could not produce a plan for some queries against partitioned views. This is described in Microsoft Connect issue 620614. The fix is located under a traceflag (see KB article 974006).


Performance no longer decreases when you use Report Viewer or display to HTML if you have multiple web parts on a single SharePoint page.


You no longer receive an "Error while unloading appdomain" exception when you close a WPF Application that includes the ReportViewer control.


Analysis Services cannot create a local cube from a server cube that has dimension members which are related to the Unknown member.


PowerPivot is now installed successfully to an existing farm if SQL Server shared components are installed to a nondefault location.


BIDS and Report Builder 3 no longer crash when you do the following: drag a cell in a table by the border, enter the "move report item" mode, move the object outside the table, and then press ESC as you click and hold the mouse button.


If Upgrade Advisor cannot scan a trace file, Upgrade Advisor can now provide a meaningful error message to a user.


The Logon dialog box for Report Builder 3.0. This is invoked when Forms Authentication is used for SSRS, is no longer obscured by a "New report Wizard" Modal dialog box. (Because of the problem, users might be unaware that a logon is being requested.)


All specific user account options now work on data source schedules.


An application that is designed in the .NET Framework 4.0 environment no longer fails if RBS cannot find its configuration information. The information is now searched in both the .NET Framework 4.0 and the .NET Framework 3.5 configuration files.


You can now create custom reports by using the .odc file on the IT Management Dashboard.


Parallelism operator transfers rows are now in the correct order. The optimizer can now choose a suboptimal plan. Therefore, this fix requires a traceflag. To use this fix, you must enable traceflag 4134.


Two new trace template files are now generated for the engine service and for the analysis service. You do this to make sure that Profiler can display all the events and columns for both services.


Fixed a minor typo in the Central Admin page.


StringCchPrintf_l expects the size of destination buffer in characters. The size was passed in bytes. Therefore OACR error - BUFFER_OVERFLOW was raised. Fixed the code by passing the correct length.


Collection sets work incorrectly when they collecting performance counters on a cluster if the SQL instance name is the same as the virtual network name.


In a given database, by using a server pointer that is declared for a select statement that contains any system view may give incorrect results after that database is attached and reattached.


DBCC corruption errors occur during SQL Server 2008 R2 collations when strings that have Jamo sequences that follow the Japanese prolonged sign are used.


An incorrect version number is displayed in SQL Server Management Studio and in SQL Server Reporting Services. This causes confusion because the displayed number does not vary from the RTM version number after an upgrade is performed.


FIX: Improved and additional information is logged for InvalidReportParameterException in Verbose output if certain conditions occur during parameter processing.


FIX: An accessibility issue that occurs because the MSAA name of "Symbol" is null. MSAA names are updated and are now discoverable.


ReportBuilder 2.0 ClickOnce displays a blank report at startup if a user edits the report by using ReportBuilder 2.0 from a SharePoint 12 website.


MSAA names for the Radial Scale Properties dialog box are incorrect and are not accessibility compliant.


Using table-valued parameters for LOB columns may cause an access violation on the server.


An access violation error may occur during the execution of Extended Stored Procedures under high stress conditions.


FIX: Improved the performance of index creation by DDL statements for tables that have many partitions and that contain no data. Previously, the time that is required for this process increased in a geometric progression as the number of partitions increased. The time that is required now increases in a linear progression.

649537, 448009

In certain conditions, the partitioned column name in error message 11405 may be wrong. This causes an incorrect column name to be printed.


A secondary exception may occur when Analysis Services generates a Watson dump file. This is true whether the Watson dump file is generated because of an actual exception or because of an explicit request to dump on certain errors. If the secondary exception occurs, the server can experience infinite recursion. This generates many dump files, and then shuts down the server.


If a user creates a user-defined type and a table-valued function in the same transaction, and if the function has a return table that contains a column of the user-defined type, a self-deadlock occurs. Additionally, the connection that tries to perform these operations is stopped.


A spatial index cannot be safely created in a table that uses CELL_ID, CELL_ATTRIBUTES or SRID for column names.


SQL Server sometimes generates a "There is insufficient system memory in resource pool 'internal' to run this query" error message. This situation is frequently preventable.


If parameters that are bound by the SQLBindParameter function specify a length of SQL_DATA_AT_EXEC, the SQL Server 2008 R2 Native Client ODC driver causes an access violation if the SQLPutData function specifies a length of SQL_NULL_DATA when the parameter value is supplied for execution.


If MARS is used, the sys.dm_os_tasks view displays the same value in the request_id column for all tasks instead of reporting the correct value associated with each task.


The sys.dm_os_wait_stats view displays duplicate rows for the MISCELLANEOUS wait type. This can cause problems for monitoring tools.


The asynchronous bucketing target displays incorrect value/string pairs for mapped fields when it is compared to the information that is available in dm_xe_map_values.


FIX: The syscolpars system base table displayed duplicate rows. This fix distinguishes them by adding the procedure number in DBCC checkcatalog.


FIX: A new error code (6257) is returned when a user tries to register a CLR assembly that is built against a newer runtime, such as CLR v4. The previous error message (code 6218) was confusing and did not state the actual issue. See the bug for detailed information.


An edge case inserts an identity value outside the current range in "set identity_insert TABLE_NAME on" mode. This issue also occurs in backup/restore operations.


Incorrect column collation information is returned when BCP.exe retrieves column metadata information.


Using a PeriodsToDate function that has a Null member parameter may cause an "Unexpected exception" error.


When query has a filter that references a column in the sys.dm_server_audit_status view, the filter is ignored, and all the rows are returned from sys.dm_server_audit_status.


Error 955 occurs when users tried to configure Management Data Warehouse if they have databases on their server that are not online.


The ring buffer displays incomplete event data (events output from dm_xe_session_targets) when it reaches the size limit for the XML output.


FIX: An access violation occurs when you use a stored procedure or a user-defined function to create a table variable in SQL Server 2008


Fixes an issue in which a remote query brings 7359 error code in SQL Server 2008 R2. This issue occurs if a UDF uses a synonym for a linked table, an execution plan for the UDF exists on the local server, and a schema version of the linked table is updated on a remote server.


Fixes a "Read AV in FullXactImpBase::GetXdes xact.cpp @ 2536" error that occurs when a database db1 is created, a query is cached for db1, then db1 is dropped, a second database is created, then db1 is created again, and the cached query is rerun.


Fixes an incorrect result from queries executed inside trigger bodies. The scenario requires a unique filtered index. The trigger must contain a query that is affected by whether a column is unique for the whole table.


Fixes an issue in which backups are corrupted when databases have Transparent Database Encryption enabled, have page checksums turned on, and the backed up is using checksums.


FIX: This fix addresses timeouts and deadlocks that may occur during subscription processing, when many subscriptions are processed concurrently. The hotfix applies when Reporting Services is deployed in SharePoint Integrated mode.


Fixes an issue in which customer has to be doing a sort and a sort page is spilt to disk. Additionally, TDE scan comes concurrently touching that particular page. You can restart the computer to bypass the problem. However, you cannot avoid this issue completely unless you turn off TDE.


Fixes a potential problem that occurs after you apply a hotfix that is described in VSTS bug 473052.


Fixes an issue in which extended events or SQL Audit log files collected may display incorrect timestamp information.


Fixes an issue in which a C# null value is converted to dbNull before persisting it.


FIX: Support is provided for a maximum of 15,000 partitions in tables and in indexes in the Datacenter, Enterprise, Developer and Evaluation editions of Microsoft SQL Server 2008 R2 SP1. For more information about how this support can be enabled and disabled, about its limitations, and about some known issues and workarounds, see the "Support for 15,000 Partitions" white paper


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?

Thank you for your feedback!