Side-by-side support in this release is as follows:

There is no side-by-side support for SQL Server failover clusters in this release.

To determine if there is an upgrade failure that can be uninstalled and then reinstalled, search for the following string in the detailed Setup log located at <drive>:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\<YYYYMMDD_HHMM>\<ComputerName>_YYYYMMDD_HHMM_Detail.txt:

Feature <Name of feature> failed, upgrade for all instance products will be terminated.

You must uninstall each February CTP component individually. You will also need the Instance ID to run the uninstall command. To determine the Instance ID, search the detail Setup log for "Instance ID". For example, you will see something similar to this in Setup logs:

10/30/2007 09:53:54 Slp: Using instance id 'MSSQL10.KATMAI' for product SQL Server Database Services

10/30/2007 09:53:54 Slp: Using instance id 'MSAS10.KATMAI' for product Analysis Services

10/30/2007 09:53:54 Slp: Using instance id 'MSRS10.KATMAI' for product Reporting Services

To uninstall and reinstall the February CTP, follow these steps:

1. Individually uninstall each component of the February CTP by using the following syntax:
   
   • For the Database Engine: Setup100.exe /Action=uninstall /SQLInstanceID=<enter the Instance ID for the Database Engine>/Features=SQL
     
   • For Analysis Services: Setup100.exe /Action=uninstall /ASInstanceID=<enter the Instance ID for Analysis Services>/Features=AS
     
   • For Reporting Services: Setup100.exe /Action=uninstall /RSInstanceID=<enter the Instance ID for Reporting Services>/Features=RS
     
2. Review the Setup summary log and detailed Setup log files to identify blocking issues.
   
3. Remove blocking issues.
   
4. Run the upgrade operation again.
   

If upgrade fails, you might be prompted to run a repair operation. The repair operation will not run Replication upgrade scripts correctly. Users should not do DML or run Replication agents on the Distributor, Publisher, or Subscribers now. Replication upgrade scripts must be run manually after the repair process has been completed. To run these upgrade scripts to repair a failed Replication upgrade, execute the stored procedure sp_vupgrade_replication in the master database. After sp_vupgrade_replication has successfully run, DML and Replication agents can continue operation. For more information about sp_vupgrade_replication, see SQL Server Books Online.

The Custom Report Item (CRI) interface has changed for the February CTP. Earlier versions of the CRI interfaces are not supported in this CTP release. For more information, see the "Temporary Breaking Changes in SQL Server 2008 CTP Releases" section in the "Breaking Changes in SQL Server Reporting Services" topic on MSDN. Some existing Dundas Chart CRIs can be upgraded in this release. For more information, see "Upgrading Reports" on MSDN.

Installing SQL Server 2008 on a domain controller is not recommended. Installing SQL Server 2008 on a read-only domain controller is not supported.

By default, Error and Usage Reporting is enabled in the February CTP. You can disable Error and Usage Reporting during UI installations by clearing the check boxes in the Error and Usage Reporting Setup dialog boxes.

You can disable Error and Usage Reporting during unattended installations by using the parameter /ERRORREPORTING=0.

To disable Error and Feature Usage Reporting after Setup is finished, use the SQL Server Error and Usage Reporting tool on the Configuration Tools menu. To run the reporting tool, click Start, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Error and Usage Reporting.

In SQL Server 2005, SQL Server Browser was an integrated installation together with Database Engine or Analysis Services. In SQL Server 2008, SQL Server Browser is a separate installation, performed automatically with the Database Engine or Analysis Services. If you have installed multiple instances of SQL Server 2008, SQL Server Browser will uninstall automatically when the last instance of SQL Server 2008 is uninstalled.

However, if SQL Server 2005 exists on the system with one or more instances of SQL Server 2008, SQL Server Browser will not be removed automatically when the last instance of SQL Server 2008 is uninstalled. The SQL Server Browser that is installed with SQL Server 2008 will remain on the system to improve connections to the instance of SQL Server 2005. You can leave SQL Server Browser installed with SQL Server 2005 and it will continue to function correctly.

To uninstall all components of SQL Server 2008, you must uninstall SQL Server Browser manually by using Programs and Features in Control Panel. If you remove SQL Server Browser when a named instance of SQL Server 2005 is present, connectivity to SQL Server 2005 might be disrupted. If this occurs, you can re-install SQL Server Browser in one of the following ways:

• Repair the instance of SQL Server 2005 by using Programs and Features.
  
• Install an instance of the SQL Server 2005 Database Engine or Analysis Services.
  

If you uninstall SQL Server Management Tools from an instance of SQL Server where Database Engine Services and Management Tools are installed, the SQL Server Agent service might not restart. To work around this issue, create a REG_SZ value named “Path” under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.SqlServer.Management.PowerShell.sqlps.

The following changes have been made to the xml data type and XQuery support, but have not yet been reflected in SQL Server Books Online.

When using an Itanium 64-bit computer, SQL Server Management Studio might throw a Null Reference exception when it expands the object explorer tree for an instance of the Database Engine. To resolve this issue, reconnect to the instance of the Database Engine until the exception is no longer thrown. Or, connect to the instance of the Database Engine from a non-Itanium computer.

• MERGE statement behavior has changed. Columns defined in the target column list of the INSERT clause now must be specified as a single-part name, or else the MERGE statement will fail. In previous CTP releases, these columns could be specified as fully qualified identifiers.
  
• Full-text predicates are no longer allowed in the OUTPUT clause when the database compatibility level is set to 100.
  
• A user-defined function cannot be created if it contains an OUTPUT INTO clause whose target is a table.
  
• Minimal logging is not available for INSERT INTO <target> SELECT <columns> FROM <rowset> Transact-SQL operation in this CTP. The topic "Operations That Can Be Minimally Logged" is incorrect regarding this operation.
  
• 
  

The ExpressionNodeList class accepts only a comma as a parameter separator and only a period as a decimal separator. Using other characters can cause unexpected results.

In the February CTP, if you script a database for transfer and the database name contains quotation marks, the script operation fails. The transfer operation will appear to run successfully, but the script that was generated to transfer the database objects will be empty. No objects will be transferred.

This can occur when you use the Copy Database Wizard and when you use SMO:

• When you use the Copy Database Wizard, this error occurs only if you select the SQL Management Object option on the Select the Transfer Method page. This error does not occur when you use the detach-and-attach transfer method.
  
• When you use SMO, this error occurs in the Transfer.ScriptTransfer method. No exception will be thrown, but the script will be empty.
  

To transfer the database in the February CTP, you must rename the database, and remove the quotation marks.

The SQL Server Native Client component in SQL Server 2008 is equivalent to SQL Native Client in SQL Server 2005. Both contain the ODBC driver and the OLE DB provider for SQL Server. You can have both versions of the component installed on the same computer, because each version uses a different ODBC driver name and different OLE DB progIDs and classIDs. Therefore, existing applications can continue to use SQL Native Client from SQL Server 2005. To use the new data types and features introduced in SQL Server 2008, you must rebuild your applications and reference sqlncli.h from SQL Server 2008, and you must revise connection strings to target SQL Server Native Client by updating the OLE DB ProgIDs to SQLNCLI10 and the ODBC driver names to SQL Server Native Client 10.0. For more information, see the "Building Applications with SQL Server Native Client" section of SQL Server 2008 Books Online.

Users in the PolicyAdministratorRole role can create policies that contain a condition that uses the ExecuteSql or ExecuteWql functions. If a user that has sysadmin permissions later executes the policy, the Transact-SQL that is provided by the Policy Administrator will be executed with the sysadmin permission of the user that is executing it.

When replication is configured, several user tables are created, and then the new tables are marked as system tables. The process of enabling replication could be blocked if there are Policy-Based Management policies that prevent certain tables from being created, for example policies that require tables to have names in a specific format. If this occurs, disable the appropriate Policy-Based Management policies while enabling replication, and then re-enable the policies.

Generating scripts for Policy-Based Management objects is not supported in the February CTP. In SQL Server Management Studio, the script buttons and menu items are enabled but are not functional.

If you are using Policy-Based Management in an installation of the November CTP and you upgrade that installation to the February CTP, you will receive an error message similar to the following when you try to save policies and conditions:

Operation 'Create' on object <object name> failed during execution (Microsoft.SqlServer.Management.Sdk.Sfc)

After you upgrade to the February CTP, to be able to save policies and conditions, you must manually update the msdb.dbo.syspolicy_management_facets table by running the following script:

IF (SELECT COUNT(name) FROM msdb.dbo.syspolicy_management_facets WHERE name = 'Audit') = 0
BEGIN
INSERT msdb.dbo.syspolicy_management_facets (name, execution_mode) VALUES ('Audit', 4);
END
IF (SELECT COUNT(name) from msdb.dbo.syspolicy_management_facets WHERE name = 'CryptographicProvider') = 0
BEGIN
INSERT msdb.dbo.syspolicy_management_facets (name, execution_mode) VALUES ('CryptographicProvider', 4);
END
IF (SELECT COUNT(name) from msdb.dbo.syspolicy_management_facets WHERE name = 'DatabaseAuditSpecification') = 0
BEGIN
INSERT msdb.dbo.syspolicy_management_facets (name, execution_mode) VALUES ('DatabaseAuditSpecification', 4);
END
IF (SELECT COUNT(name) from msdb.dbo.syspolicy_management_facets WHERE name = 'ISurfaceAreaConfigurationForAnalysisServer') = 0
BEGIN
INSERT msdb.dbo.syspolicy_management_facets (name, execution_mode) VALUES ('ISurfaceAreaConfigurationForAnalysisServer', 0);
END
IF (SELECT COUNT(name) FROM msdb.dbo.syspolicy_management_facets WHERE name = 'ISurfaceAreaConfigurationForReportingServices') = 0
BEGIN
INSERT msdb.dbo.syspolicy_management_facets (name, execution_mode) VALUES ('ISurfaceAreaConfigurationForReportingServices', 0);
END
IF (SELECT COUNT(name) from msdb.dbo.syspolicy_management_facets WHERE name = 'ResourceGovernor') = 0
BEGIN
INSERT msdb.dbo.syspolicy_management_facets (name, execution_mode) VALUES ('ResourceGovernor', 7);
END
IF (SELECT COUNT(name) FROM msdb.dbo.syspolicy_management_facets WHERE name = 'ResourcePool') = 0
BEGIN
INSERT msdb.dbo.syspolicy_management_facets (name, execution_mode) VALUES ('ResourcePool', 7);
END
IF (SELECT COUNT(name) from msdb.dbo.syspolicy_management_facets WHERE name = 'ServerAuditSpecification') = 0
BEGIN
INSERT msdb.dbo.syspolicy_management_facets (name, execution_mode) VALUES ('ServerAuditSpecification', 4);
END
IF (SELECT COUNT(name) FROM msdb.dbo.syspolicy_management_facets WHERE name = 'WorkloadGroup') = 0
BEGIN
INSERT msdb.dbo.syspolicy_management_facets (name, execution_mode) VALUES ('WorkloadGroup', 7);
END
IF (SELECT COUNT(event_name) FROM msdb.dbo.syspolicy_facet_events WHERE event_name = N'ALTER_RESOURCE_GOVERNOR_CONFIG') = 0
BEGIN
INSERT msdb.dbo.syspolicy_facet_events (management_facet_id,event_name,target_type,target_type_alias) 
SELECT management_facet_id,N'ALTER_RESOURCE_GOVERNOR_CONFIG',N'RESOURCEGOVERNOR',N'RESOURCE GOVERNOR CONFIGURATION'
FROM [dbo].[syspolicy_management_facets]
WHERE name = 'ResourceGovernor'
END
IF (SELECT COUNT(event_name) from msdb.dbo.syspolicy_facet_events WHERE event_name = N'CREATE_RESOURCE_POOL') = 0
BEGIN
INSERT msdb.dbo.syspolicy_facet_events (management_facet_id,event_name,target_type,target_type_alias) 
SELECT management_facet_id,N'CREATE_RESOURCE_POOL',N'RESOURCEPOOL',N'RESOURCE POOL'
FROM [dbo].[syspolicy_management_facets]
WHERE name = 'ResourcePool'
END
IF (SELECT COUNT(event_name) FROM msdb.dbo.syspolicy_facet_events WHERE event_name = N'ALTER_RESOURCE_POOL') = 0
BEGIN
INSERT msdb.dbo.syspolicy_facet_events (management_facet_id,event_name,target_type,target_type_alias) 
SELECT management_facet_id,N'ALTER_RESOURCE_POOL',N'RESOURCEPOOL',N'RESOURCE POOL'
FROM [dbo].[syspolicy_management_facets]
WHERE name = 'ResourcePool'
END
IF (SELECT COUNT(event_name) from msdb.dbo.syspolicy_facet_events WHERE event_name = N'CREATE_WORKLOAD_GROUP') = 0
BEGIN
INSERT msdb.dbo.syspolicy_facet_events (management_facet_id,event_name,target_type,target_type_alias) 
SELECT management_facet_id,N'CREATE_WORKLOAD_GROUP',N'WORKLOADGROUP',N'WORKLOAD GROUP'
FROM [dbo].[syspolicy_management_facets]
WHERE name = 'WorkloadGroup'
END
IF (SELECT COUNT(event_name) from msdb.dbo.syspolicy_facet_events WHERE event_name = N'ALTER_WORKLOAD_GROUP') = 0
BEGIN
INSERT msdb.dbo.syspolicy_facet_events (management_facet_id,event_name,target_type,target_type_alias) 
SELECT management_facet_id,N'ALTER_WORKLOAD_GROUP',N'WORKLOADGROUP',N'WORKLOAD GROUP'
FROM [dbo].[syspolicy_management_facets]
WHERE name = 'WorkloadGroup'
END

When you use FILESTREAM, consider the following issues:

• FILESTREAM cannot be enabled on instances of SQL Server that are running on Windows on Windows 64 (WOW64).
  
• If you add a FILESTREAM filegroup to an existing database and do not take another database snapshot, a REVERT DATABASE statement will fail.
  
• After you run a REVERT statement, FILESTREAM filegroups will appear offline in the database snapshot.
  
• FILESTREAM is not supported on tables that use table-valued parameters. In these tables, columns that have the FILESTREAM attribute are treated as varbinary(max) columns.
  
• When you use ALTER DATABASE to set an empty FILESTREAM filegroup to default for the first time, the Database Engine will not return an error. This is by design.
  
• A DROP DATABASE statement can take a long time to complete if the database contains FILESTREAM filegroups that contain lots of BLOBs.
  
• In rare cases, computers that are running antivirus products can cause an SQL Exception. This occurs during a DROP DATABASE or ALTER DATABASE statement when the Database Engine cannot delete the FILESTREAM data container. The data container must be removed manually.
  
• FILESTREAM data container paths that are longer than 160 characters must be prefixed with the following characters: \\?\.
  
• In the following scenario, the call to OpenSqlFileStream() fails because the SELECT query has not completed when the call is made to OpenSqlFileStream().
  

  BEGIN TRANSACTION SELECT col1, convert(varchar(max), col2) col2 FROM t_FS_MARS_02_2 ORDER BY col1 SafeFileHandle readHandle = NativeMethods.OpenSqlFilestream(…); COMMIT

• FILESTREAM data containers are not automatically added to the system access control list. If you detach a FILESTREAM database from instance A and try to attach it to instance B, the operation will fail if instance A and B are using different service account groups. In this case, a member of the service account group for instance A must manually add the directories to the system access control list.
  
• On Windows Vista or Windows XP Service Pack 2, if you set the FILESTREAM access level to 2 or 3, the server message block (SMB) port in the Windows firewall will be opened for out-of-band data. For more information, see the topic "sp_filestream_configure" in SQL Server 2008 Books Online.
  
• Mount points are not supported in the February CTP. A mount point is a volume or drive that is mapped to a folder on an NTFS file system volume.
  

SQL Server Management Studio may not properly create audit specification details. To work around this behavior, clear the Enabled check box when creating the audit specification, and then enable the audit specification on the Audit Specification property page as a second step. Query sys.server_audit_specifications and sys.database_audit_specifications for the status of audit specifications.

In previous versions of SQL Server, any user could obtain information about backup sets and backup devices by using the RESTORE FILELISTONLY, RESTORE HEADERONLY, RESTORE LABELONLY, and RESTORE VERIFYONLY Transact-SQL statements. Because they reveal information about the content of the backup files, in SQL Server 2008 and later versions these statements require CREATE DATABASE permission. This requirement secures your backup files and protects your backup information more fully than in previous versions. For information about this permission, see "GRANT Database Permissions" in SQL Server 2008 Books Online.

Server collations may not be recognized by a client installed with a version of SQL Server older than SQL Server 2008 or a SQL Server client installed on a Windows operating system earlier than Windows Vista. Additionally, SQL Server 2008 Windows collations may not be recognized in third-party client applications that rely on older versions of either SQL Server or the Windows Vista operating system.

The client may return an error mid-connection. In cases where the collation information is required at connection time, the connection will be dropped. A server-side error will be generated when the connection is dropped between server and client. The error specifies the connection failure and the name of the collation that is not recognized on the client.

You cannot currently replicate to SQL Server Compact any columns that contain the FILESTREAM attribute or the geography, geopmetry, or hierarchyid data types.

Replication will fail even if you use article schema options or the publication compatibility level to specify that these data types should be mapped to data types that are supported by SQL Server Compact. You can replicate tables that contain columns with the new data types by filtering out these columns. For more information about filtering, see SQL Server Books Online.

SQL Server 2008 uses a different version of the SQL Native Client from the one included in SQL Server 2005. (SQL Native Client is called SQL Server Native Client in SQL Server 2008.) Therefore, Integration Services packages that use SQL Server Native Client and were created in SQL Server 2005 cannot run automatically in SQL Server 2008. To run these packages, follow one of these steps:

• Run the SSIS Package Upgrade Wizard to upgrade packages and update the connection strings.
  
• On the computer that is running SQL Server 2008, install SQL Native Client (sqlncli.dll) from SQL Server 2005.
  

  Note:
  You can install SQL Native Client side by side with SQL Server Native Client.

• Revise the connection strings in the package to specify SQL Server Native Client. To revise the connection strings, replace SQLNCLI with SQLNCLI10.
  

SQL Server 2008 includes a different version of the Analysis Services OLE DB provider from the one included in SQL Server 2005. Therefore, Integration Services packages that use the Analysis Services OLE DB provider and were created in SQL Server 2005 cannot run automatically in SQL Server 2008. To run these packages, follow one of these steps:

• Run the SSIS Package Upgrade Wizard to upgrade packages and update the connection strings.
  
• On the computer that is running SQL Server 2008, install the Analysis Services 9.0 OLE DB provider. The Analysis Services 9.0 OLE DB provider is the version of the provider that SQL Server 2005 includes.
  

  Note:
  You can install the Analysis Services 9.0 OLE DB provider side by side with the Analysis Services 10.0 OLE DB provider. The Analysis Services 10.0 OLE DB provider is the version that SQL Server 2008 uses.

• Revise the connection strings in the package to specify the Analysis Services 10.0 OLE DB provider. To revise the connection strings, do the following steps:
  
  • Replace MSOLAP.3 with MSOLAP or MSOLAP.4. If you specify MSOLAP, your packages will use the latest installed version of the provider.
    
  • Replace MSOLAP90 with MSOLAP100.
    

If you developed a SQL Server 2005 Integration Services (SSIS) custom component, that custom component must be modified before it can be used in SQL Server 2008 Integration Services packages. You can either modify the component to run only in SQL Server 2008 packages or to run in both SQL Server 2005 and SQL Server 2008 packages.

You cannot connect from the version of SQL Server Management Studio that SQL Server 2008 installs to an instance of the Integration Services service that SQL Server 2005 installs.

If the computer is running Microsoft Windows Server 2008 Beta or the Microsoft .NET Framework 2.0 Service Pack 1 (SP1), a package will fail when the following conditions are true:

• The package contains an Execute SQL task whose ADO.NET connection manager uses the .NET Framework Data Provider for SQL Server (SqlClient) to connect to SQL Server 2008.
  
• The result set returned by the SQL statement includes Time columns or DateTimeOffset columns.
  

To run the package, add Type System Version=Sql Server 2005 to the connection string for the Execute SQL Task.

The Script task and Script component use Visual Studio for Applications (VSTA) 2.0. VSTA 2.0 is not supported on Itanium-based systems. If you deploy a package that contains a Script task or a Script component on this Itanium-based operating system, the package will not run. Also, you receive an error message that indicates that VSTA is not installed.

Business Intelligence Development Studio stops working if you try to create an HTML page file in Business Intelligence Development Studio by using the following procedure:

1. In Business Intelligence Development Studio, on the File menu, click New, and then click File.
   
2. In the New File dialog box, click HTML Page, and then click Open.
   

When Business Intelligence Development Studio stops working, stop and restart Business Intelligence Development Studio.

If you try to install a localized version of Visual Studio 2008 after you have installed a localized version of SQL Server 2008, Visual Studio 2008 may not install.

To install a localized build of Visual Studio 2008 after you have installed a localized version of SQL Server 2008, follow these steps:

1. Uninstall the localized version of the files that are associated with Business Intelligence Development Studio by running the following command:
   <drive>:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Setup100.exe /q/ACTION=uninstall /SKU=Dev /FEATURES=BIDS /InstanceName=MSSQLSERVER
   
2. Uninstall the localized version of Visual Studio 2008, the corresponding SQL Server 2008 Visual Studio Tools for Applications 2.0 Language Pack, and the English-language version of Microsoft Visual Studio Tools for Applications 2.0.
   
3. Install the localized version of Visual Studio 2008.
   
4. Install the localized version of Business Intelligence Development Studio.
   

In the February CTP and earlier CTP releases of SQL Server 2008, the Script task and Script component used a version of Visual Studio for Applications (VSTA) that is no longer supported. Therefore, the scripts that the Script task and Script component contain are not supported in the following cases:

• You used the February CTP or an earlier CTP release of SQL Server 2008 to open a SQL Server 2005 package, convert the existing scripts, and then save the converted package.
  
• You used the February CTP or an earlier CTP release of SQL Server 2008 to open a SQL Server 2005 package and add a script to the package.
  
• You used the February CTP or an earlier CTP release of SQL Server 2008 to create a new package and add a script.
  

If the script is not supported, SQL Server 2008 Integration Services will display an error message when you open the package. To run the package, create a new Script task or Script component and create a new VSTA script.

When you migrate a SQL Server 2005 package to SQL Server 2008, the migration process automatically converts the scripts in the package to the current version of VSTA. (The package migration feature for SQL Server 2005 packages will be available in a future release of SQL Server 2008.)

In this CTP release, when you upgrade Integration Services, the PATH environment variable will not be updated. This variable will still contain the value, " C:\Program Files\Microsoft SQL Server\90\DTS\Binn", which specifies the path of the earlier version of Integration Services. This value for the PATH environment variable will prevent the dtexec utility (dtexec.exe) and the other command-prompt utilities that Integration Services provides from working with SQL Server 2008 packages.

To use one of the command-prompt utilities that Integration Services provides with SQL Server 2008 packages, do one of the following steps:

• Specify the complete path, " C:\Program Files\Microsoft SQL Server\100\DTS\Binn", to the upgraded version of the utility when you use the utility at the command prompt.
  
• Change the PATH environment variable from " C:\Program Files\Microsoft SQL Server\90\DTS\Binn" to " C:\Program Files\Microsoft SQL Server\100\DTS\Binn".
  

An Integration Services package will stop responding or will fail before it starts to run when all the following circumstances are true:

• You use the dtexec utility (dtexec.exe) to run the package at the command prompt. (This problem does not occur when you use Business Intelligence Development Studio to run the package.)
  
• In the package, there is a data flow task with these conditions:
  
  • The data flow task contains at least one asynchronous transformation.
    
  • The asynchronous transformation has at least one output, other than an error output, that has not been connected to a downstream transformation or destination.
    
  • The value of the RunInOptimizedMode property of the data flow task is True. (This is the default value.)
    

To make sure that an Integration Services package that meets these conditions will run successfully, do one of the following steps:

• Connect all outputs of asynchronous transformations, other than error outputs, to downstream transformations or destinations. For example, an easy way to end the data flow path with minimal configuration is to connect the output to a Row Count transformation. However, the row count calculation that the Row Count transformation performs will decrease overall package performance by 10 percent to 30 percent.
  —or—
  
• Set the value of the RunInOptimizedMode property of the data flow task to False.
  

When you install the 32-bit versions of SQL Server and Integration Services on a 64-bit computer, scripts might not be supported. If the package contains a Script task and the script in that Script task is a Visual Basic script, the package will not run.

To successfully run a package that contains a Script task that uses Visual Basic script, follow these steps:

1. Run the cmd.exe tool that is located at %windir%\system32 to open a Windows Command Prompt window.
   
2. At the command prompt, type the following command:
   copy /Y "%ProgramFiles(x86)%\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SQLServer.DTSRuntimeWrap.dll" "%CommonProgramFiles(x86)%\microsoft shared\VSTA\Pipeline\AddInViews\"
   
3. Run the cmd.exe tool that is located at %windir%\SysWOW64 to open a Command Prompt window for "Windows on Windows 32".
   
4. At the command prompt, type the following command:
   "%windir%\Microsoft.NET\Framework\v3.5\AddInUtil.exe" -PipelineRoot:"%CommonProgramFiles(x86)%\microsoft shared\VSTA\Pipeline" –Rebuild
   

In the February CTP, if you install multiple instances of Reporting Services and both report server instances run under different service accounts, an "HTTP 500 Internal Server Error" might be displayed when accessing the report server URL. The report server trace log will contain the following additional information: "An internal or system error occurred in the HTTP Runtime object for application domain ReportManager_0. Failed to create HTTP Runtime." The exception for this message is: "The type initializer for 'System.Web.Compilation.CompilationLock' threw an exception. ---> System.InvalidOperationException: Mutex could not be created."

The error occurs when one of the report server instances runs under an account that has fewer permissions than the other; for example, one instance runs as Local System and the second server instance runs as Network Service. The error is the result of an ASP.NET grant rights permission issue.

To work around this error, you can either configure both server instances to run under the same account, or you can run the following command to grant permissions to the service account of the instance that you cannot access:

1. Open a Command Prompt window and navigate to %windir%\microsoft.net\framework\v2.0.50727
   
2. Type aspnet_regiis.exe –ga and specify the account for which you want to grant permissions.
   If it is a domain account, specify it as <domain>\<user>. If it is Network Service, the command should be specified as "NT AUTHORITY\NetworkService". The following example demonstrates the syntax you should use:
   aspnet_regiis.exe –ga "NT AUTHORITY\NetworkService"
   
3. Press ENTER.
   
4. Restart both instances of the report server.
   You can use the Reporting Services Configuration tool to connect to and restart the services.
   Type the report server URL to verify access. Be sure to restart both server instances before you retry access to the report server. You can use the URL pages in the Reporting Services Configuration tool to verify access to the Report Server Web service and Report Manager applications.
   

In SQL Server 2008, when you export a report to Microsoft Office Excel, expressions in the report are no longer translated to Excel formulas.

In earlier versions of Reporting Services, when you exported a report to a CSV file format, the data was formatted in a way that preserved the way the data appeared on the report page. For matrix data regions, this resulted in a data format that was inconvenient to import into other applications in order to continue to work with the data.

In this release, when you export a report to a CSV file, you can choose between two supported formats: Default mode and Compliant mode. Default mode is optimized for Excel. Compliant mode is optimized for third-party applications. For more information, see "Exporting to a CSV File" in SQL Server Books Online.

The earlier format for CSV files is no longer available. However, for reports that do not use matrix data regions, you can use Compliant mode to get a file format closest to the earlier CSV file format.

In the Report Designer Preview stand-alone client, there is no support for viewing subreport report items when you preview a report locally. To view subreports in a report, first publish the report to the report server, and then navigate to the Report Manager URL (for example, http://localhost/reports) to view the main report.

In this CTP release, you cannot use Report Builder if you configure the report server to use Basic authentication.

In the February CTP, the Data Source View wizard does not detect the relationships between SQL Server 2000 or later database tables when SQL Server Native Client (SQLCNLI) is not installed on the database server. To automatically detect the relationships, install SQLCNLI on the computer that you are running Model Designer on. If you cannot install SQLCNLI, the relationships will not be detected and you will be prompted to create relationships by name matching. If your database is not designed with foreign key relationships that can be determined based on name matching, you will need to manually define the relationships before generating your report model. For more information, see the "Installing SQL Server Native Client" topic in Books Online.

In Report Builder, fields with an infinite clickthrough action set on it in the first column of a table may cause an error when clicked. Report readers can click the field that is set as an infinite clickthrough field but the clickthrough report will not be displayed. In some instances, depending on the field expression’s scope, infinite clickthrough may work if the field is in the top cell of the left-most column when the report is rendered. Infinite clickthrough reports will be displayed if you add the field to another column within the report.

In the SQL Server 2008 version of Business Intelligence Development Studio, the designers that you use to create projects for Integration Services, Analysis Services, and Reporting Services cannot be installed side by side with the SQL Server 2005 designers. For both SQL Server 2008 and SQL Server 2005, these designers are part of the Workstation Components that SQL Server installs. However, for this CTP release, you cannot install the SQL Server 2008 designers if the SQL Server 2005 Workstation Components are already installed on the computer. You must uninstall the SQL Server 2005 Workstation Components before installing SQL Server 2008. If you try to install SQL Server 2008 without first uninstalling the SQL Server 2005 Workstation Components, you will be notified that the existing components on the computer are blocking the installation. To uninstall the existing Workstation Components, in Control Panel, open Add or Remove Programs, select SQL Server 2005, click Remove, and on the Component Selection page of the wizard, select Workstation Components. After you have uninstalled the SQL Server 2005 Workstation Components, you can install the SQL Server 2008 designers by installing SQL Server 2008.

To create projects for Integration Services, Analysis Services, or Reporting Services, you use their respective designers in Business Intelligence Development Studio. However, the designers in SQL Server 2008 cannot be installed side by side with those from SQL Server 2005. Furthermore, installing SQL Server 2008 replaces designers that were installed by SQL Server 2005 with the SQL Server 2008 versions.

You can use the SQL Server 2008 designers to open and modify projects that were created by using the SQL Server 2005 designers. However, if you use the SQL Server 2008 designers to modify SQL Server 2005 Business Intelligence projects, you can no longer save those projects in the SQL Server 2005 format. Upon opening a SQL Server 2005 project, the designer upgrades the project in memory to the SQL Server 2008 format. To permanently replace the SQL Server 2005 version of the project with the upgraded SQL Server 2008 version, you must either save the upgraded version of the project or perform an operation, such as running an Integration Services package, that will cause the upgraded version of the project to be saved. Otherwise, the upgraded version will not be saved.

The version of Business Intelligence Development Studio that the February CTP release of SQL Server 2008 uses differs from the version that the November CTP release uses. When you upgrade SQL Server from the November CTP release to the February CTP release, Business Intelligence Development Studio will not be automatically upgraded. You must manually upgrade Business Intelligence Development Studio from the version that is used by the November CTP release to the version that the February CTP release uses. If you do not upgrade Business Intelligence Development Studio, you will not be able to use the February CTP release to create and deploy projects to SQL Server.

You can manually upgrade Business Intelligence Development Studio either before or after you upgrade SQL Server to the February CTP release. We recommend that you upgrade Business Intelligence Development Studio before you upgrade SQL Server. If you decide to upgrade SQL Server before you upgrade Business Intelligence Development Studio, SQL Server displays the following warning:

Rule "Business Intelligence Development Studio for previous releases of SQL Server 2008 check" generated a warning. Business Intelligence Development Studio (BIDS) for the previous releases of SQL Server 2008 is installed on the machine. BIDS for SQL Server 2008 will not be installed because this feature does not support upgrading from or side by side installation with the previous version.

To upgrade Business Intelligence Development Studio before you upgrade to the February CTP release

1. Uninstall the version of Business Intelligence Development Studio that was installed by the November CTP release by running the following command:
   ‘%ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\Setup100.exe  /q /ACTION=uninstall /FEATURES=BIDS’
   
2. Upgrade to the February CTP release of SQL Server.
   
3. Install the version of Business Intelligence Development Studio that is included in the February CTP release by running the following command:
   ‘%February CTPSetupLocation%\setup.exe /q /ACTION=install /FEATURES=BIDS’
   

To upgrade Business Intelligence Development Studio after you upgrade to the February CTP release

1. Upgrade to the February CTP release of SQL Server.
   
2. Uninstall the version of Business Intelligence Development Studio that was installed by the November CTP release by running the following command:
   ‘%ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\Setup100.exe  /q /ACTION=uninstall /FEATURES=BIDS’
   
3. Install the version of Business Intelligence Development Studio that is included in the February CTP release by running the following command:
   ‘%February CTPSetupLocation%\setup.exe /q /ACTION=install /FEATURES=BIDS’