List of the bugs that are fixed in SQL Server 2008 Service Pack 1

944390

FIX: Error message when you connect to a named instance of SQL Server on a client computer that is running Windows Vista or Windows Server 2008: "Specified SQL server not found" or "Error Locating Server/Instance Specified"

955769

FIX: The Shared Memory protocol for an instance of SQL Server 2008 is always enabled and the VIA protocol for the instance is always disabled after you repair the instance

956031

FIX: Error message when you estimate the compression on a table in SQL Server 2008: "Subquery returned more than 1 value"

956427

You cannot add a cluster node when you install SQL Server 2008 Analysis Services and you do not install the SQL Server 2008 Database Engine

958778

FIX: The default instance name is set incorrectly to SQLEXPRESS when you install SQL Server 2008 Express

959001

FIX: The Log Reader Agent skips some transactions when the Log Reader Agent runs to replicate transactions for a transactional replication in SQL Server 2005 and in SQL Server 2008

959025

FIX: Error message when you call a stored procedure that returns a rowset which has the DBPROP_MAXROWS rowset property or the SSPROP_MAXBLOBLENGTH rowset property specified: "The incoming tabular data stream (TDS) protocol stream is incorrect"

959026

FIX: Error message when you run a DB2 query that uses the WITH UR query hint in SQL Server 2005 Analysis Services and in SQL Server 2008 Analysis Services: "OLE DB error: OLE DB or ODBC error: An unexpected token "WITH" was found following "<Query>""

961126

FIX: Error message when you run a maintenance plan in SQL Server 2008: "The SQL Server Execute Package Utility requires Integration Services to be installed"

961271

FIX: In a SQL Server 2008 Reporting Services report that contains several levels, some items disappear when you collapse another item

961633

FIX: A SQL Server 2008 Reporting Services report is displayed incorrectly in Mozilla Firefox if the report is displayed by using the ReportViewer control

962900

FIX: Error message when you run a query that involves an outer join operation in SQL Server 2008: "Attempting to set a non-NULL-able column's value to NULL"

963070

FIX: You cannot edit or debug an SSIS package in BIDS when SQL Server 2008 Enterprise Edition, Standard Edition, Developer Edition, or Evaluation edition is installed without the SSIS feature

963658

FIX: PAGE compression is removed from a SQL Server 2008 data table after you shrink the database

967470

FIX: Error message when you perform an update or a delete operation on a table that does not have a clustered index created in SQL Server 2008: "The operating system returned error 1450"

968587

FIX: The aggregate value is incorrect when you design a query that contains some entity groups by using the Report Model Query Designer in SQL Server 2008 or in SQL Server 2005

968599

FIX: Error message when you try to specify the SQL Server 2008 Reporting Services account as the credential for a report server in SharePoint Central Administration: "Unable to connect to Report Server WMI provider"

968693

FIX: A query that uses parameters and the RECOMPILE option returns incorrect results when you run the query in multiple connections concurrently in SQL Server 2008

968828

FIX: The system objects may not be checked as expected when you use different policy evaluation modes in SQL Server 2008

968829

FIX: Error message when you try to upgrade an instance of SQL Server 2005 to SQL Server 2008: "Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes"

968830

FIX: An incorrect version is displayed on the Instance Selection page when you use SQL Server 2008 Setup to upgrade an instance of SQL Server 2008

971268

'Microsoft SQL Server management studio' and 'SQL Server Profiler' report 'Evaluation period has expired' message even after upgrading to a licensed edition

A new trace event is added in SQL Server 2008 SP1 to better diagnose unexpected cancellation issues in SQL Server 2008 Analysis Services.

Some trace events that are related to personalization extension are added to the SQL Server Profiler trace definitions in Analysis Services.

When a client that is based on MSOLAP, Analysis Management Objects (AMO), or ADOMD.NET connects to Analysis Services over an HTTP connection, the client does not send back certain HTTP headers.

In SQL Server 2008 SP1, more information is added to the minidump files that are generated for troubleshooting in Analysis Services.

You cannot browse time series models that have nested tables by using the SQL Server Data Mining Add-ins for Office 2007.

You receive an error message when you process an association rules mining model in SQL Server 2008 Standard Analysis Services: "Errors in the metadata manager. An error occurred when loading the <Mining Model Name> mining model."

The decision tree algorithm returns a regression formula that contains valid floating-point regression coefficients in Analysis Services.

When the cross-validation stored procedure is invoked by using a specific target start and probability threshold, incorrect results are returned for the True Positive measure, for the True Negative measure, for the False Positive measure, and for the False Negative measure in Analysis Services.

You receive an incorrect result when you use the NON EMPTY statement and the CROSSJOIN function in a Multidimensional Expressions (MDX) statement that queries from a Sum-based measure and a LastNonEmpty-based measure in Analysis Services.

A subselect clause that uses calculated members does not consider the granularity to determine whether a calculated member should be included in Analysis Services.

In SQL Server 2008 SP1, improvements are made to help you troubleshoot unexpected cancellation issues in Analysis Services.

When a polling query is querying a DateTime value, the proactive caching process crashes in Analysis Services.

An access violation occurs when you process a dimension that has a calculated member that references another member that is defined later in the cube script in Analysis Services.

The SQL Server Browser Service crashes in SQL Server 2008.

The service pack configuration files are not up to date in SQL Server 2008.

You cannot browse for a named instance of SQL Server 2008 Express that is installed on a Windows Vista-based computer.

When you call the sp_server_info stored procedure to return the database version, the words "Microsoft SQL Server Yukon" are returned instead of the words "Microsoft SQL Server 2008."

A memory leak occurs when you use the bcp utility to copy data from a table to a file by specifying the field terminator for a column of the sql_variant date type in SQL Server 2008.

When you call the SQLBulkOperations function to insert multiple rows in SQL Server 2008, only the first row is inserted, and the rest of the rows are skipped.

The SQLColumns function returns an error if the trailing character of a table name is an escape character in SQL Server 2008.

In SQL Server 2008, if a SELECT statement causes a server error and the next statement causes a server warning, the SQL Server Native Client ODBC driver returns a SUCCESS state for the statement.

When you call the SQLProcedureColumns function in SQL Server 2008, the information about the parameters of the CLR type is missing.

When you use table-valued parameters whose SQL types are variable length types in a SQL Server 2008-based application, the SQL Server Native Client ODBC provider creates an incorrect tabular data stream (TDS).

You receive an error message when you use the ICommand::Execute interface by using table-valued parameters without using the SetParameterInfo function in SQL Server 2008: "The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect."

In a SQL Server 2008-based application, a long text string is truncated. This problem occurs if comments are at the beginning of the statement and if the parameter for the string is passed as the DBTYPE_VARIANT data type and as the BSTR subtype.

In SQL Server 2008, if data of a user-defined type is very large, the data is broken on a 32-bit computer. This issue occurs if you do not provide the length for the binding and if you use one of the following interfaces: IRowsetChange::InsertRow, IRowsetUpdate::Update, IRowsetChange, or IRowsetChange::SetData.

The IRowsetChange interface and the IRowsetUpdate interface incorrectly handle the ISequentialStream::Read implementation if the implementation returns the S_FALSE value at the end of the data stream in SQL Server 2008.

When you install SQL Server Native Client, the installer sets the version information in an incorrect registry subkey in SQL Server 2008.

When you connect to an instance that is earlier than SQL Server 2008 by using SQL Server Management Studio in SQL Server 2008, the parentheses-matching-and-highlighting feature does not work.

An exception occurs when you try to expand databases by using a non-administrator login in Object Explorer in SQL Server 2008.

When you use the Generate SQL Server Scripts Wizard to generate one file per object in SQL Server 2008, the default constraints are scripted in a separate file and not in the table script file.

When you transfer data for a table that contains triggers by using SMO or the Copy Data Wizard in SQL Server 2008, the operation fails.

When you use the Transfer class in SQL Server Management Objects (SMO) in SQL Server 2008 to transfer data, the connection is not disposed of after it is used.

SQL Server adds the full Windows Installer logs to the Windows Error Reporting report instead of adding only the logs up to the moment that the error occurred.

SQL Server 2008 SP1 improves the error reporting for errors that may occur when you install the SqlSupport.msi file.

Submissions that are not valid are reported to Windows Error Reporting because the submissions are overwritten when you uninstall SQL Server 2008.

Windows Error Reporting reports for external exceptions do not include the HRESULT message in SQL Server 2008.

SQL Server 2008 SP1 improves Windows Error Reporting by removing localized strings.

SQL Server 2008 SP1 improves Windows Error Reporting by removing platform designations from parameter names.

SQL Server 2008 SP1 improves the logging of Windows Error Reporting bucket parameters by logging parameter values before and after hashing.

The SQL Server 2008 installation file reports the setup operation to Windows Error Reporting even if the setup operation is canceled by the user.

SQL Server Agent displays an incorrect command line in the Datasource control for a SQL Server 2008 Integration Services package job.

SQL Server Agent crashes when SQL Server Agent tries to report an unsuccessful attempt to run a Microsoft ActiveX script under a proxy account.

You receive an incorrect syntax error message when you create a condition that contains an enumeration in Policy Management in SQL Server 2008.

SQL Server 2008 SP1 adds the Concatenate (string, string) function and the Escape (string, char, char) function to the Policy Management condition evaluation functions to support WMI Query Language (WQL) execution.

When you run a policy against a remote server in SQL Server 2008, the policy uses the local subscription table instead of the subscription table from the remote server.

In SQL Server Management Studio, Object Explorer is no longer limited to 2,500 items that are displayed at any single level.

A very quick query that is run in a loop shows a confusing CPU wait status in the Resource Waits list in Activity Monitor in SQL Server 2008.

Long-running queries may not appear in the Expensive Queries list in Activity Monitor until they have completed execution in SQL Server 2008.

When you use the Generate SQL Server Scripts Wizard to script an offline database that has the AUTO_CLOSE option set to ON, the collation of the database is queried.

An error occurs in the Script Data Wizard if there is an offline database in SQL Server 2008.

Some keyboard shortcuts are missing in SQL Server Management Studio.

The filter lookup list is not populated in Model Designer when you use a Teradata data source in SQL Server 2008 Reporting Services.

Charts, gauges, and images may appear blurry when you view them in Business Intelligence Development Studio or in Report Builder 2.0 Preview mode.

When you export a report in the comma separated values (CSV) format, Reporting Services may omit a row for a Tablix data region that has dynamic groups.

Table group headings do not repeat when you render a report as a PDF, as a Print Preview, or as an image if a row does not completely fit on one page.

A text box that splits across pages does not correctly display all the content in Reporting Services.

The memory throttling behavior for different editions of Reporting Services is not enforced correctly.

A SQL Server 2005 Reporting Services report that contains the SyncLock statement in the report code cannot be rendered in a fresh installation of SQL Server 2008.

When you view a SQL Server 2008 Reporting Services report in a SQL Server 2005 viewer control, the viewer control shows an incorrect page count.

When you use the sp_configure stored procedure to configure the access check cache quota option in SQL Server 2008, the quota set is not enforced.

The HAS_PERMS_BY_NAME built-in function does not work when column names contain quotation marks in SQL Server 2008.

When you are not a member of the db_owner fixed database role, you cannot change the data type of a column to a user-defined data type in SQL Server 2008.

SQL Server 2008 cannot restart after the resource database files are moved to a location that differs from the location of the Sqlserver.exe file.

The sys.dm_exec_query_stats view reports an incorrect CPU time for parallel query plans in SQL Server 2008.

A memory leak occurs in the list of triggers to be fired. For example, a memory leak occurs for the first trigger object if two triggers are fired in an ALTER TABLE SWITCH PARTITION statement.

Results that are not valid are returned when you run a query that converts the user-defined type (UDT) to the varbinary data type in the same SELECT statement in SQL Server 2008.

Incorrect results are returned when you call a stored procedure that has table-valued parameters and that has the same table variable passed for two or more parameters in SQL Server 2008.

Dynamic management views may return incorrect results for cross-database queries when the database is dropped or is re-created in SQL Server 2008.

Query fingerprints and plan fingerprints are not stable for queries on temporary tables in SQL Server 2008.

Change data capture incorrectly reports an UPDATE statement as a DELETE statement that is followed by an INSERT statement in SQL Server 2008.

The ALTER TRIGGER statement is not replicated if it is issued against a trigger that is in a specific schema in SQL Server 2008.

When you validate a publication in a transactional replication in SQL Server 2008, articles that you added after you added a vertical filter to an article are not validated.

The About dialog box in Replication Monitor for the release version of SQL Server 2008 uses the "Katmai" code name as the background image.

The error messages and the warning messages are not localized when you use the ssbdiagnose utility in SQL Server 2008.

The SQL Server WMI Provider cannot be loaded on a named cluster instance of SQL Server 2008.

SQL Server 2008 timing values may be incorrect when you use utilities or technologies that change CPU frequencies.

The AUDIT LOGIN trace event always provides the correct database ID for the system databases and the user databases in SQL Server 2008. However, the database name is provided only for the system databases. The database name is NULL for the user databases.

You cannot use the sp_altermessage stored procedure to enable or disable system messages to the Windows event log in SQL Server 2008.

You receive the incorrect result when you query the sys.dm_xe_packages view by filtering on the module_address column in SQL Server 2008.

SQL Server 2008 seems to make slow progress and may return error 701 if the buffer pool size is very small.

On a computer that has lots of memory, messages may be reported incorrectly in the SQL Server 2008 error log. The messages indicate that the process is paged out when it is not paged out.

The start time that is reported in the sqlserver_start_time column of the sys.dm_os_sys_info view is calculated by obtaining the current time in milliseconds and then by subtracting the number of seconds since the server started in SQL Server 2008.

All information about schedulers is collected in the dump file to help debug in SQL Server 2008.

When you use the SQLIOSim utility in SQL Server 2008, the SQLIOSim utility stops if you selected the stamp files or if you specified "StampFiles=TRUE" in the configuration file.

The optimizer generates an incorrect execution plan for a query that uses a spatial index in SQL Server 2008.