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 Service Pack 2 (SP2).


  • 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 information about how to obtain SQL Server 2008 service packs, click the following article number to view the article in the Microsoft Knowledge Base:

How to obtain the latest service pack for SQL Server 2008

More Information

In addition to the fixes that are listed in this article, SQL Server 2008 SP2 contains the hotfixes that were included in Cumulative Update 1 through Cumulative Update 8 for SQL Server 2008 Service Pack 1 (SP1). For more information about the cumulative update packages that are available for SQL Server 2008 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

970365 The SQL Server 2008 builds that were released after SQL Server 2008 SP1 was released

The bugs that are fixed in this service pack

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

VSTS bug number

KB article number




FIX: Error message when you run the ProcessAdd command after you make changes to the partition on a server that is running SQL Server 2008: "Internal Error: An unexpected exception occurred"



FIX: Incorrect results if you use parentheses around SELECT in a statement that has a common table expression in SQL Server 2008



FIX: SQL Server 2008 Service Pack 2 enhancements to the “Operation has been cancelled” error message text in Analysis Services



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



SQL Server 2008 setup fails to install on a Windows Server 2008-based cluster mount point



Error message when you try to use the binaries from the SQL Server System CLR Types package (SQLSysClrTypes.msi): "Unable to load DLL 'SqlServerSpatial.dll': This application has failed to start because the application configuration is incorrect"



Slipstream installation of SQL Server 2008 fails if the /PCUSOURCE or /CUSOURCE has a space in the path



A SQL Server 2008 or SQL Server 2005 Analysis Services ROLAP query returns incorrect results



FIX: You may experience some loss of data when you use an UPDATE statement with a SET clause that uses the time, datetime2 and datetimeoffset types in SQL Server 2008



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: The margins are not retained in a report when the report is exported to Excel on a server that is running SQL Server 2008, and then you preview the report in Excel



FIX: Error message when you export a report to Excel in Report Manager on a server that is running SQL Server 2008: "Unhandled managed exception: Type = System.ArgumentOutOfRangeException"



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



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



Correcting the lack of cryptographic salt variation on SQL Server sa login hash



No mapping between account names and security IDs was done" error when adding a node to a SQL Server 2008 Failover Cluster



You cannot enroll a SQL Server 2008 database instance into a SQL Server Utility



You cannot deploy a Data-Tier application to a SQL Server 2008 database instance



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



FIX: A hotfix is available that enables SQL Server 2008 R2 Reporting Services to use a 2048-bit RSA key to encrypt a Reporting Services key for FIPS compliancy



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

Additional issues that are fixed in this service pack

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

VSTS bug number



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


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


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.


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


FIX: The Mismatched view can contain multiple views that have different numbers of indexes. This fix forces a deterministic order of views to compare, based on matched functions and on the number of matched indexes.


Users receive an "Access Denied" error message when they navigate to Report Manager locally if UAC is enabled. Adding an updated "Access Denied" message to mention UAC could allow users to address the setting accordingly.


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


Radial Gauge users who try to use “RateOfChange” or “Integral” as the formula type for the MaximumValue or MinimumValue on the gauge do not see a value in the property grid dropdown list.


FIX: The FailoverAnalysis.sql file is installed during a SQL Server Failover Cluster setup. This script will be called automatically when failure occurs. The SqlDMVScriptTimeout private property controls for how many milliseconds the script can take to finish.


Users receive a validation error when they are upgrading Shared Data Sources that have a space in the name. The error indicates that the name cannot contain spaces.


Installation of Service Pack 1 for SQL Server Business Intelligence Development Studio 2008 fails because of a missing configuration file.


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


Users cannot return multiple cookies in their HTTP module. This affect users when they try implement custom authentication.


The sqlsos.task_address, sqlsos.worker_address, and sqlsos.scheduler_address Extended Events actions display an incorrect address.


Reporting Services 2008 Designer converts centimeters to inches in the Tablix. This causes a loss of layout precision.


Uninstalling the first of two named AS instances disables the SQL Browser. This causes the second named instance to be unreachable.


Users cannot use stored credentials in their data sources if a Smart Card is required.


A query that has a subselect clause that uses a set expression that does not return any calculated members returns an error saying that subselects that have calculated members are not allowed.


In Analysis Services, setting a dimension default member by using an MDX expression that has a NonEmpty function causes the server to return an internal error when it tries to open the cube.


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


Integer value gets incorrectly rounded in the SQL Server Reporting Services Reusable Query Designer.


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.


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.


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


SQL Server Reporting Services 2008 experiences a connection leak when a user uses the SOAP interface to run and export a report.


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


Users receive a "Page Expired" error message when they try to refersh a rendered report after the report remains idle for one hour.


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


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.


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.


FIX: A new error message indicates the cause of an access violation that occurs if the bucketizer target parameters are set incorrectly.


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


Subscriptions fail during execution because of an in-memory data structure problem during the attempted email delivery of an MHTML-rendered report.


BIDS 2008 Report Designer running together with SQL Server Reporting Services 2008 crashes when users resize a table row.


The TO, CC, and BCC fields of the "Report Delivery Options" dialog box are cleared after users cancel or close the "Schedule Details" dialog box to return to "Report Delivery Options."


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.


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


When users clear the selection of one or more months in a monthly schedule, SSRS creates separate schedules for each month that is still selecteded. In some cases, this can cause an "@active_end_date cannot be before @active_start_date" error.


Data-Driven subscription fails if a NULL value is returned when it is mapped to the report parameter, which accepts a NULL value.


Subscription and Delivery issues are difficult to diagnose in the Reporting Services trace file. More verbose logging is required.


Users receive an "Index was out of range. Must be non-negative and less than the size of the collection" error message when they export to PDF.


Users cannot use custom authentication in the SQL Server 2008 Web SKU.


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 containing a column of the user-defined type, a self-deadlock occurs. Additionally, the connection that tries to perform these operations is terminated.


FIX: Support is provided for a maximum of 15,000 partitions in tables and in indexes in the Enterprise, Developer, and Evaluation editions of Microsoft SQL Server 2008 SP2. 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 (


In Analysis Services, some customers may experience access violation when they use a parent-child hierarchy in the condition of an IIF function.


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


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.


A secondary exception may occur when Analysis Services generates a Watson dump. This is true whether the Watson dump 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 dumps, and then shuts down the server.


FIX: In SSRS 2008 Service Pack 2, the RS add-in for SharePoint 2007 for communicating with SSRS 2008 R2 report server is updated. This enables access to certain functionality in ReportBuilder 3.0, ReportParts, and ATOM Renderer, including the new Report preview in ReportBuilder 3.0.


Processing objects in a database that contains thousands of metadata objects takes a long time to begin importing the data. This occurs because the server has to build a job schedule before the data import begins. Additionally, the algorithm that is used to determine dependencies causes slow performance when many metadata objects exist in the database.


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


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


Using cell security together with calculations yields incorrect results when a NON EMPTY clause is used.


Read access violation occurs during a commit process if two transactions run simultaneously: one to modify or create a partition, and one to process a dimension.


When Microsoft Office 12 is integrated with SQL Server 2008 Reporting Services, the SharePoint integration does not default to the Report Builder clickonce URL, preventing Report Builder from starting.


FIX: Localization issue in the Turkish SKU: bread crumbs are now localized on new reportpart library pages.


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


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


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


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


During a check for a granular audit, the algorithm that is used to list any audits that include the event may experience memory leaks of the list of audits. This continues until out-of-memory errors occur and the service has to be restarted to reclaim the memory.

Note If you are upgrading from SQL Server 2008 SP1Cumulative Update 9 or a later version, you must apply a post-SQL Server 2008 SP2 cumulative update after you upgrade to SQL Server 2008 SP2 to obtain all the fixes.

For more information about the post-SQL Server 2008 SP2 Cumulative Update, click the following article number to view the article in the Microsoft Knowledge Base:

2289254 Cumulative update package 1 for SQL Server 2008 Service Pack 2


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!