SQL Server 2000 - Existing instances of SQL Server 2000 are not supported on the same computer together with SQL Server 2008.

SQL Server 2005 - Existing instances of SQL Server 2005 SP2 are supported on the same computer together with SQL Server 2008.

SQL Server 2008 – Previous versions of SQL Server 2008 January CTP are not supported side-by-side with this release of SQL Server 2008. You can install multiple instances of this release on the same computer.

To determine if there is an upgrade failure that can be uninstalled 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 SQL Server 2008 November 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 SQL Server 2008 November CTP, follow these steps:

1. Individually uninstall each component of SQL Server 2008 November CTP 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 Surface Area Configuration tool for SQL Server has been removed from SQL Server 2008. Replacement functionality in this release is as follows:

Upgrading Full-Text Search to the November CTP5 will uninstall and reinstall Full-Text service. After upgrade, Full-Text Search will lose previous configuration and will require manual steps to get it working again. After upgrade, follow these steps:

1. Open SQL Server Configuration Manager.
   
2. Change Full-Text service account to a different account.
   
3. Change Full-Text service account and password again to match the Engine service account and password.
   
4. Copy files in the FTData directory from the SQL Server 2008 instance directory to previous version's FTData directory (for example, from C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\FTData\ to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData\)
   
5. Then, configure SQL Server 2008 Full-Text Search for use with SQL Server 2008.
   

When upgrading to SQL Server 2008 November CTP from a SQL Server instance with case-sensitive collations, do not use domain accounts for SQL Server system administrator accounts. To provision system administrator accounts, configure the accounts after upgrade finishes.

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

Identifiers for objects in RDL (for example, textboxID) were previously unrestricted in length. In this release, the length of object identifiers is restricted to 256 characters. Identifiers still must be CLS-compliant.

You can install SQL Server 2008 on a domain controller. The following limitations apply:

• Due to security concerns, installation of SQL Server 2008 on a domain controller is not recommended.
  
• On Windows Server 2003, SQL Server services can run under a domain account or a local system account.
  
• You cannot run SQL Server services on a domain controller under a local service account or a network service account.
  
• After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the host computer to a domain controller.
  
• After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member.
  
• SQL Server is not supported on a read-only domain controller.
  

By default, Error and Usage Reporting is enabled in the November CTP. This setting will remain enabled for future CTP releases.

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 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 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 Add or Remove Programs 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 become disrupted. If this occurs, you can re-install SQL Server Browser in one of the following ways:

• Repair the instance of SQL Server 2005 through Add or Remove Programs.
  
• Install an instance of SQL Server 2005 Database Engine or Analysis Services.
  

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 is a fully reserved keyword when the database compatibility level is set to 100. The MERGE statement is also available under both 90 and 100 database compatibility levels, but the keyword is not fully reserved when the database compatibility level is set to 90.
  
• 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.
  

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 SQL Server 2008 November 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 SQL Server 2008 November CTP, you must rename the database, and remove the quotation marks.

The language parser for the Transact-SQL Editor has been redesigned to provide IntelliSense support. As part of that work, the parser in the November CTP has temporarily disabled the following functionality:

• Color coding is disabled for any syntax other than Transact-SQL keywords.
  
• Colorization of sqlcmd syntax is disabled.
  
• Parenthesis matching and highlighting is disabled.
  

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:

• 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:

• 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.
    

For the November CTP release, you must uninstall SQL Server 2005 Workstation Components before installing the SQL Server 2008 Workstation Components. Uninstalling the SQL Server 2005 Workstation Components removes three Integration Services components: the SQL Server 2005 version of the Execute DTS 2000 Package task and two supporting assemblies. These three Integration Services components support backward compatibility between SQL Server 2005 and SQL Server 2000 Data Transformation Services (DTS). Without these three components, SQL Server 2005 packages and tools that require DTS support will not run.

However, SQL Server 2008 Integration Services includes a version of the Execute DTS 2000 task and the two supporting assemblies. Therefore, you can upgrade SQL Server 2005 packages that require DTS support to the SQL Server 2008 format by opening them in the SQL Server 2008 version of Business Intelligence Development Studio, and then running those packages as SQL Server 2008 packages.

A custom application that uses both Integration Services and the .NET Framework Data Provider for SQL Server (System.Data.SqlClient) APIs will fail if the following conditions are true:

• The custom application uses the .NET Framework Data Provider for SQL Server APIs before the application uses the Integration Services APIs.
  
• The custom application runs on a computer that has both SQL Server 2008 and an edition of SQL Server 2005 that does not support some or all of the features of Integration Services.
  

Under these conditions, the custom application incorrectly detects the version of SQL Server as the edition of SQL Server 2005 that does not support Integration Services. This erroneous detection causes the custom application to fail when it calls the Integration Services APIs and to generate a DTS_E_PRODUCTLEVELTOLOW error. This error indicates that Integration Services is not supported on the detected version of SQL Server.

This failure does not occur in the following situations:

• When running packages in the design environment.
  
• When using dtexec.exe to run packages outside the design environment.
  
• When the custom application uses Integration Services APIs, but does not use the .NET Framework Data Provider for SQL Server APIs.
  

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.

To install VSTA when you install the November CTP, select the Software Development Kit option, and install either Integration Services or SQL Server Management Studio. If you only select the Software Development Kit option, VSTA will not be installed.

If VSTA was not installed when you installed the November CTP, you can manually install VSTA by running the VSTA_Aide.msi tool. The VSTA_Aide.msi tool is in the SQLDEV\Tools\Setup folder of the November CTP.

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.

In this CTP release, you also cannot use the Integration Services service that SQL Server 2008 installs to manage SQL Server 2005 packages that are stored in an instance of SQL Server 2005.

If SQL Server 2008 Integration Services is installed side-by-side with SQL Server 2005 Integration Services, the Analysis Services components that are used by Integration Services might cause an exception to be raised. When using the earlier version of Integration Services, the exception System.Runtime.InteropServices.COMException at Microsoft.SqlServer.Dts.Pipeline.Wrapper.CManagedComponentWrapperClass.ProvideComponentProperties() might occur. If you must use the Analysis Services components in SQL Server 2005 Integration Services, do not install SQL Server 2008 side-by-side.

In the November 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 November 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 November 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 November 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 the November 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.
   

The version of SQL Server Books Online that is included with the November CTP release of SQL Server 2008 includes documentation that refers to the SQL Server Business Intelligence Development Studio version of Report Designer, while documentation of new features refers to the stand-alone Report Designer Preview report authoring tool.

You can continue to author reports in Business Intelligence Development Studio just as you could in SQL Server 2005 Reporting Services. However, you cannot use Business Intelligence Development Studio to access the new report features described in the "What's New" topic. To author reports that use new features, you must use the Report Designer Preview client application that is included with this release.

For the November CTP, Report Designer Preview cannot access SQL Server Analysis Services data sources. The Data Source dialog box does not include Microsoft SQL Server Analysis Services.

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 earlier versions of Reporting Services, different renderers used different rules to determine which items with conditional visibility to include on a report page. For example, aggregate calculations were not performed for hidden items in printed reports, but were calculated for hidden items in reports that you viewed with a browser or in Excel.

In this release, all renderers use the same set of rules to determine which items are on a page.

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 release, the Report Object Model namespace has changed. This namespace provides read-only access from custom code to global collections like Fields, Parameters, and ReportItems. If existing custom code explicitly uses a fully qualified reference to an earlier namespace, this change is a breaking change.

We recommend that you do not use fully qualified references to access built-in collections from your code. By not explicitly specifying the namespace, custom code references resolve to the version of the report object model for the currently installed version of Reporting Services.

For example, in SQL Server 2005 Reporting Services, the following two examples contrast the use of a fully qualified reference to a parameter (Microsoft.ReportingServices.ReportProcessing.ReportObjectModel.Parameter) and a default reference to a parameter (Parameter) for passing a report parameter to a custom function that returns the report parameter label.

The following example shows a fully qualified reference for a report parameter. This example is NOT RECOMMENDED.

'DO NOT USE FULLY QUALIFIED NAMESPACE REFERENCES FOR RUN-TIME COLLECTIONS
Public Function ShowParams(ByVal reportparameter As _
Microsoft.ReportingServices.ReportProcessing.ReportObjectModel.Parameter) _
 As String
       Return reportparameter.Label
End Function

The following example shows the recommended way to access a run-time collection.

Public Function ShowParams(ByVal reportparameter As Parameter) _
 As String
       Return reportparameter.Label
End Function

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

In the November 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.

When you publish, deploy, or upload a report to a SQL Server 2008 report server, the report server tries to upgrade the report to the new report definition schema on first use. A report that is successfully upgraded is processed by the SQL Server 2008 Reporting Services report processor. A report that cannot be upgraded is processed by the SQL Server 2005 Reporting Services report processor. A report cannot be processed by both report processors.

When a report contains subreports, one of four possible states can occur during upgrade:

• The main report and all subreports can be successfully upgraded. They are processed by the SQL Server 2008 Reporting Services report processor.
  
• The main report and all subreports cannot be upgraded. They are processed by the SQL Server 2005 Reporting Services report processor.
  
• The main report can be upgraded but one or more subreports cannot be upgraded. The main report is processed by the SQL Server 2008 Reporting Services report processor, but the rendered report shows the message "Error: Subreport could not be processed" in the location where the subreport that could not be upgraded would appear.
  
• The main report cannot be upgraded but one or more subreports can be upgraded. The main report is processed by the SQL Server 2008 Reporting Services report processor, but the rendered report shows the message "Error: Subreport could not be processed" in the location where the subreport would appear.
  

If you see the error "Error: Subreport could not be processed", you must change the definition of the main report or the subreport so that the reports can be processed by the same version of the report processor. For more information, see " Breaking Changes in SQL Server Reporting Services" on MSDN.

Drillthrough reports do not have this limitation because they are processed as independent reports.

In SQL Server 2005 Reporting Services, a text box added to the report design surface with the expression =Fields!FieldName.Value renders without error if the report includes a single dataset. By design, the report processor evaluates the expression using the scope set to the name of the dataset.

When a report has more than one dataset, the expression is undefined. The SQL Server 2008 report processor detects the condition when no default dataset scope is set for an expression and more than one dataset exists in the report. The error message you see depends on how you view the report. In local preview, you see the message: "An error occurred during local report processing. The definition of the report 'TextBox' is invalid." In Report Manager, you see the message: "The Value expression for the textbox 'Textbox1' refers to the field 'FieldName'." Additionally, each message includes this explanation: "Report item expressions can only refer to fields within the current data set scope or, if inside an aggregate, the specified data set scope."

To correct this error, provide the scope for the expression in the text box. For example, =First(Fields!FieldName.Value, "DataSet1").

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.