This page is carefully and closely monitored. Any changes you make will be evaluated and then quickly accepted, refined, or reverted. Because this is a wiki, additions or refinements to these release notes might have been made by community members. To read the original release notes document, click here.
This Release Notes document describes known issues that you should read about before you install or troubleshoot SQL Server Code-Named “Denali” CTP1 (download it here).
The information in this document has not been updated for SQL Server Express, and use of SQL Server Expresss with SQL Server "Code-Named "Denali" is not supported.
This Release Notes document is available online only, not on the installation media, and it is updated periodically.
For information about how to get started and install SQL Server Code-Named “Denali”, see the SQL Server Code-Named “Denali” Readme. The Readme document is available on the installation media and from the Readme download page.
1.0 Before You Install
2.0 Analysis Services
3.0 Database Engine
4.0 Integration Services
5.0 Reporting Services
7.0 Upgrade Advisor
8.0 Providing Documentation Feedback
9.0 How to Find More Known Issues
The following items describe the prerequisite installation behavior during SQL Server Code-Named “Denali” CTP1 Setup.
.NET 3.5 SP1 is a requirement for SQL Server Code-Named “Denali” CTP1, but it is no longer installed by SQL Server Setup.
If you install SQL Server Code-Named “Denali” on a computer with the Windows Vista SP2 or Windows Server 2008 SP2 operating system, and you do not have .NET 3.5 SP1, SQL Server Setup requires you to download and install.NET 3.5 SP1 before you can continue with the SQL Server installation. The error message includes a link to the download center. To avoid the interruption during SQL Server Setup, you can download and install .NET 3.5 SP1 before you run SQL Server Setup.
If you install SQL Server Code-Named “Denali” on a computer with the Windows 7 or Windows Server 2008 R2 operating system, SQL Server Setup enables 3.5 SP1 if it is not already enabled.
.NET 4.0 is a requirement for SQL Server Code-Named “Denali”. SQL Server installs .NET 4.0 during the feature installation step.
To avoid a computer restart when .NET 4.0 is installed, SQL Server requires you to install an update. SQL Server Setup checks for the presence of this update and then requires you to download and install the update before you can continue with the SQL Server installation. To avoid the interruption during SQL Server Setup, you can download and install the update before running SQL Server Setup as described below:
If you install SQL Server Code-Named “Denali” on a computer with the Windows Vista SP2 or Widows Server 2008 SP2 operating system, you can get the required update from here.
If you install SQL Server Code-Named “Denali” on a computer with the Windows 7 or Windows 2008 R2 operating system, you can get the required update from here.
Windows PowerShell 2.0 is a pre-requisite for installing SQL Server Code-Named “Denali” Database Engine components and SQL Server Management Studio, but PowerShell is no longer installed by SQL Server Setup. If PowerShell 2.0 is not present on your computer, you can enable it by following the instructions on the Windows Management Framework page.
SQL Server Code-Named “Denali” CTP1 requires Windows PowerShell 2.0 as a prerequisite. PowerShell 2.0 currently cannot be installed on either Windows Vista or Windows Server 2008 if the operating system language is one of the following 11 languages: Bulgarian (Bulgaria), Estonian (Estonia), Croatian (Croatia), Lithuanian (Lithuania), Latvian (Latvia), Slovak (Slovakia), Slovenian (Slovenia), Serbian (Latin, Serbia), Romanian (Romania), Thai (Thailand), or Ukrainian (Ukraine).
SQL Server Code-Named “Denali” Evaluation edition is supported on the Windows Vista SP2, Windows Server 2008 SP2, Windows 2008 R2, and Windows 7 operating systems.
SQL Server Code-Named “Denali” CTP1 Datacenter Edition cannot be used to install SQL Server failover multi-subnet clusters. If you try to install a SQL Server Code-Named “Denali” CTP1 Datacenter Edition or upgrade an earlier version of SQL Server to SQL Server Code-Named “Denali” CTP1 Datacenter Edition on a multi-subnet cluster, setup exits with the following message: "The selected SQL Server edition does not support multi-subnet failover clusters.”
To avoid this, use SQL Server Code-Named “Denali” CTP1 Evaluation Edition to install SQL Server failover multi-subnet clusters. SQL Server Code-Named “Denali” CTP1 Evaluation Edition has the same set of features as SQL Server Code-Named “Denali” CTP1 Datacenter Edition.
SQL Server Code-Named “Denali” CTP1 does not support renaming the SQL Network name resource. If you rename an existing SQL Network Name resource using Windows Cluster administrator, SQL Server upgrade and other setup operations of the renamed cluster instance might fail.
Installing a new SQL Server Code-Named “Denali” failover cluster using the advanced install option from the installation center will cause a failure during the Advance Cluster Completion step. To avoid this error, use the integrated install option by clicking New SQL Server failover cluster installation on the Installation page to create a new SQL Server Code-Named “Denali” failover cluster, or use the command-line option for the Advanced Cluster Completion step.
The following issue occurs when there is more than one SQL Server failover cluster instance on a node:
Select the SQL Server Failover Cluster instance using the Cluster Node Configuration page. After making the selection and clicking next on the Cluster Node Configuration page, you cannot change the SQL Server failover cluster instance selection by going back to the Cluster Node Configuration page. This might result in the incorrect removal of the cluster node.
To change your SQL Server failover cluster selection after the Cluster Node Configuration step, we recommended that you click Cancel and restart the Remove Node action by selecting Remove node from a SQL Server failover cluster on the Maintenance page from the Installation Center.
The SQL Server Code-Named “Denali” CTP1 Books Online Help viewer crashes if your computer is configured to run IPv6 without IPv4.
Workaround: Enable IPv4 on the system by executing ‘netsh interface ipv4 install’ from the command prompt. For more information, see Netsh commands for Interface Internet Protocol version 4 (IPv4) in the TechNet Library.
After you enable IPv4, you must reboot the system.
To view SQL Server Code-Named “Denali” CTP1 Books Online in this release, you must install the following SQL Server features: SQL Server Management Studio and Books Online. This is because the Help viewer for Books Online is installed only when the SQL Server Management Studio feature is installed. We might resolve this issue in a future CTP release so that the Help viewer for Books Online is installed when the Books Online feature is selected during SQL Server Setup.
We do not recommend installing SQL Server Express or Express Advanced editions for use with SQL Server Code-Named "Denali" CTP1. There are also no separate installation packages for SQL Server Express and SQL Server Express with Advanced Services in CTP1 of SQL Server Code-Named "Denali”.
Do not install or upgrade PowerPivot for SharePoint in this CTP. Neither upgrade nor side-by-side installation with a SQL Server 2008 R2 instance of PowerPivot for SharePoint is supported. PowerPivot workbooks that you created using SQL Server 2008 R2 software do not run on the CTP1 version of PowerPivot for SharePoint. If you publish a SQL Server 2008 R2 PowerPivot workbook to a SQL Server Code-Named “Denali” PowerPivot server, the “Unable to refresh data” error appears instead of the data you expect. An updated version of PowerPivot for Excel is currently planned to be available in a subsequent CTP.
Business Intelligence Development Studio (BIDS) is not supported in the following situations:
Microsoft SQL Server Code-Named “Denali” CTP1 BIDS is installed on the same server as an earlier release of MS SQL Server BIDS.
An earlier release of Microsoft SQL Server with BIDS is upgraded to Microsoft SQL Server Code-Named “Denali” CTP1.
Make sure you create and maintain BIDS projects on computers that do not fall into the categories above.
If you use SQL Server Management Studio (SSMS) when you connect to an Analysis Services (AS) server and click Browse from the AS context menu, the AS browser fails to load.
Workaround: Use Business Intelligence Development Studio (BIDS) to browse cubes, dimensions, mining structures, and mining models.
Formerly you could browse cubes, dimensions, and mining models, view the lift chart for a mining model, and build a prediction query in SQL Server Management Studio. However, this functionality is not available in this CTP release, pending migration of the SSMS toolset to Visual Studio 2010, which is being considered for a future release.
Workaround: Use Business Intelligence Development Studio (BIDS) to browse cubes, dimensions, mining structures, and mining models. BIDS functionality is not affected by this change, so you can continue to create OLAP objects and data mining objects by using BIDS.
For the Management Data Warehouse and the SQL Utility Control Point, if you upgrade from SQL Server 2008 or SQL Server 2008 R2 to SQL Server Code-Named “Denali”, the SQL Server Data Collector is disabled and errors occur. To enable the SQL Server Data Collector, in Microsoft SQL Server Management Studio, expand the Management folder, right-click the Data Collection node, and then click Enable Data Collection.
If you run a Transact-SQL statement that returns spatial data in SQL Server Management Studio, you cannot launch the Spatial Results tab. No workaround exists in SQL Server Code-Named “Denali”CTP1. Current plans are to enable the tab in a future CTP.
In SQL Server Management Studio, the maintenance plan design surface is not available in this release. When you right-click the Maintenance Plans node in Object Explorer, the New Maintenance Plan option is not displayed. To create a new maintenance plan, you must use the Maintenance Plan Wizard option. Users will also not be able to edit existing maintenance plans. Current plans are to resolve this issue in a future CTP release.
In SQL Server Management Studio, when expanding a database under the Databases node in Object Explorer, the Database diagrams node does not appear. No workaround for this issue currently exists. Current plans are to resolve this issue in a future CTP release.
A rolling upgrade involves upgrading the server instance that is currently acting as the mirror server in one or more database mirroring sessions and then manually failing over each mirroring session to the upgraded mirror server instance. The manual failover should cause the new principal database to run upgrade. However, in SQL Server Code-Named “Denali” CTP1, the database might fail to run upgrade, causing it to enter the SUSPECT state.
Workaround: To update a SUSPECT database and bring it online, restart the server instance one or more times until the database succeeds in coming online.
Changing the SQL Server service account might change the authentication method required for the database mirroring endpoint. In that case, you must drop and re-create the database mirroring endpoint. For more information, see "HADR" Prerequisites and Restrictions in Books Online.
Dropping the database mirroring endpoint terminates all sessions between local and remote availability replicas and between local and remote database mirroring partners/witnesses.
For an introduction to "HADR", see "HADR" Overview and "HADR" Prerequisites and Restrictions in Books Online.
3.7.1 "HADR" is Missing Features
The SQL Server Code-Named “Denali” CTP1 release of "HADR" is a preview and does not support the following features:
Synchronous data movement (synchronous-commit availability mode).
Manual failover and automatic failover.
The only supported form is forced failover, which allows data loss and suspends the secondary databases.
Automatic page repair.
The ALTER AVAILABILITY GROUP Transact-SQL statement does not support changing the configuration of the availability group such as changing read-only access to an availability replica, adding or removing an availability database, and adding or removing a secondary availability replica. For information about what this Transact-SQL statement supports, see ALTER AVAILABILITY GROUP (Transact-SQL) in Books Online.
Workaround: Delete the availability group, and then re-create it. For more information, see Deleting an Availability Group (SQL Server) and Creating an Availability Group (SQL Server) in Books Online.
"HADR" requires all server instances that host availability replicas to have the same SQL Server system collation.
On a secondary availability replica that is configured for read-only access:
Full-text search is disabled.
Automatic statistics are not supported.
3.7.2 Before Forcing a Failover, Verify That All Secondary Databases Are SYNCHRONIZING
After forcing an availability group to fail over, you must manually resume the secondary databases on the new secondary replica. Before failing the group over again, wait for every secondary database to be in the SYNCHRONIZING state. The SYNCHRONIZING state indicates that the new secondary database has completed reverting transactions that were lost during the forced failover and is currently synchronizing log records with the new primary database.
If you attempt another failover before every secondary database enters the SYNCHRONIZING state, any database that is not yet SYNCHRONIZING will be prevented from coming online as a primary database. In this case, re-establishing data synchronization for the database might require restoring transaction logs, restoring a full database backup, or failing over again to the original primary replica.
For information on how to determine the data-movement state of an availability database, see Monitoring Availability Groups (SQL Server Management Studio) or sys.dm_hadr_database_replica_states (Transact-SQL) and Monitoring Availability Groups (Transact-SQL) in Books Online.
3.7.3 A WSFC Cluster Might Need Shared Disks That Are Unavailable on Some Nodes
In deploying “HADR”, you might need to configure a Windows Server Failover Clustering (WSFC) cluster to include shared disks that are not available on all nodes. For example, in a WSFC cluster across two data centers with three nodes, two nodes host a SQL Server failover clustering instance (FCI) in the primary data center and have access to the same shared disks. The third node hosts a stand-alone instance of SQL Server in a different data center and does not have access to the shared disks from the primary data center. This WSFC cluster configuration supports the deployment of “HADR”, where the FCI hosts the primary replica and the stand-alone instance hosts the secondary replica.
With Windows Server 2008 R2 and earlier versions, you cannot configure a WSFC cluster through Failover Cluster Manager to add shared disks that are not available on all nodes.
With Windows Server 2008 R2 SP1, however, you can configure a WSFC cluster to include shared disks that are not accessible on all nodes as long as the shared disks are available on at least two nodes. You can download and install the beta version of this service pack from Windows 7 Service Pack 1 Beta and Windows Server 2008 R2 Service Pack 1 Beta.
3.7.4 Connecting to a Primary Availability Replica
After you create and configure an availability group, applications can connect to primary availability replicas in the following ways:
Set up multiple client connections using database mirroring connection strings. For more information, see the section “Client Connections” of the “HADR” Overview topic in Books Online.
Create a virtual network name (VNN) that directs connectivity to the current primary replica. This VNN must be unique in the domain. For more information, see the Microsoft paper, Creating a Virtual Network Name for “HADR”.
3.7.5 Connecting to a Secondary Availability Replica Configured for Read-Only Access
To connect to a secondary availability replica for read-only access, you must connect directly to the server instance that hosts the availability replica. For more information, see Creating a Valid Connection String Using TCP/IP in Books Online.
In CTP1, to be able to connect to a secondary replica, you must configure the secondary replica for read-only access when you create the availability group. For more information, see Read-Only Access to Secondary Availability Replicas in Books Online.
3.7.6 ‘Cross Subnet’ Failovers Take Longer Than Failovers Within a Subnet
Current drivers take longer for ‘cross subnet’ failovers than for failovers within a subnet.
3.7.7 Effects of Belonging to an Availability Group on a Contained Database
A contained user that is created in a contained database (that currently belongs to an availability group) will not be available for authentication to the secondary replica until the instance of SQL Server that hosts that replica is restarted or until a failover occurs.
Changes made to the some properties of a contained database that currently belongs to an availability group do not take effect on the secondary replica until the instance of SQL Server that hosts that replica is restarted or a failover occurs. These properties are as follows: default_language_lcid/default_language_name, default_fulltext_language_lcid/default_fulltext_language_name, is_nested_triggers_on, is_transform_noise_words_on, and two_digit_year_cutoff.
3.7.8 Deleting and Re-Creating a WSFC Cluster Requires Disabling and Re-enabling the HADR Service
If you delete and re-create the WSFC failover cluster on which you have deployed "HADR", you must disable and re-enable the HADR service for each server instance for which the HADR service was enabled on the original WSFC cluster. For more information, see Enabling the HADR Service on a Server Instance (SQL Server Configuration Manager) and Enabling the HADR Service on a Server Instance (SQL Server Configuration Manager) in Books Online.
Before you click Delete, you must select the row that corresponds to the environment variable to be deleted.
To restore an Integration Services project to a previous version, right-click the corresponding version, and then click Restore.
After moving Integration Services projects or environments in SQL Server Management Studio, the change might not automatically display in Object Explorer. To display the current location of the object, refresh Object Explorer.
In SQL Server Management Studio, the Operations dialog box does not perform well if there are a large number of operations occurring. Note: To open the Operations dialog box, right-click the SSISDB folder, and then click View Operations. To avoid this issue and view all operations, execute a Transact-SQL query against the Integration Services catalog views catalog.operations and catalog.operation_messages.
After you create an Integration Services environment variable, the data type of that variable cannot be changed. If a different data type is required, delete the environment variable, and then create a new environment variable with a different data type.
In Business Intelligence Development Studio, Integration Services parameter values are visible even if the parameter was marked as sensitive.
The Integration Services catalog requires you to enable CLR integration for the instance of SQL Server where it resides. To enable CLR integration, use the sp_configure stored procedure. The Integration Services catalog is required to use the new deployment and administration features in this release.
Creating an Integration Services environment and an environment reference to that environment at the same time might fail. To avoid this problem, create an environment before creating environment references to that environment.
With SQL Server Management Studio (SSMS), you cannot assign parameter values to an instance of execution. You can use SSMS to set default parameter values for projects and packages. You cannot use SSMS to override those default values after an execution has been created.To assign parameter values to an instance of execution, use the Transact-SQL stored procedure, catalog.set_execution_parameter_value.
You can create two environment variables with the same name, but with different cases. For example, you can create a variable named Var1 and another variable named VAR1. Integration Services treats these variables as two separate variables.
When using Business Intelligence Development Studio, the undo history might be cleared if you click Undo immediately after creating a source or destination with the source assistant or destination assistant, respectively.
Workaround: To avoid this issue, switch focus elsewhere in the designer before you click Undo.
When using Business Intelligence Development Studio in debug mode, if you click Undo or Redo, the undo history is cleared.
Workaround: To avoid the loss of undo history, do not click Undo or Redo while in debug mode.
In SQL Server Code-Named “Denali” CTP1, metadata extraction from SQL Server 2005 is not supported. You can create an extraction point that targets an instance of SQL Server 2005, but attempts to extract metadata from that instance result in an error.
You will encounter the following limitations when using Integration Services Source Assistant and Destination Assistant:
Not all installed connection managers appear as available in the dialog box.
You cannot create a Flat File destination with Destination Assistant.
You might not be able to double-click an item.
When you use Dependency Designer in SQL Server Management Studio, icons for SQL Server objects do not display.
If you open Dependency Designer in SQL Server Management Studio while an extraction is in progress or immediately after you cancel an extraction, you might get an error.
Workaround: To avoid this issue, do not open Dependency Designer in these situations. If you get an error, close and then re-open SQL Server Management Studio.
SQL Server Code-Named “Denali” CTP1 includes metadata providers for Integration Services and SQL Server. These metadata providers are still under development and are currently limited in their capabilities. Only a limited set of Integration Services tasks, transforms, connection managers, sources, and destinations are supported. Due to Transact-SQL parsing limitations, some SQL Server dependencies cannot be determined.
When you redeploy an Integration Services project with the Deployment Wizard, if any of the parameter data types have changed from what is currently deployed, the deployment fails.
Workaround; To avoid this, do not change parameter data types of projects that have already been deployed.
Managed custom extensions such as tasks, transforms, connection managers, and log providers that use supported SSIS interfaces and are built referencing the SSIS runtime from SQL Server 2008 or SQL Server 2008 R2 will continue to work in the new SSIS runtime from this release.
Third-party, native COM-based custom extensions such as tasks, transforms, connection managers, and log providers developed for previous versions of SQL Server Integration Services (SSIS) do not work with this release. To work with this release, new versions of these components must be compiled with the new SSIS runtime from this release.
In order to use the new version of the SSIS runtime from this release, you might need to modify or reconfigure applications that use the SQL Server Integration Services (SSIS) runtime object model. To redirect a managed application to use the new version of the SSIS runtime assemblies, use assembly redirection rules in your application configuration file. If the application creates components (such as tasks and transforms) using a ProgID or CLSID, then you must change all the references to those components. In the future, we recommend that you use a provided stock name or component creation name instead of a ProgID and CLSID.
If you install SQL Server Code-Named “Denali” CTP1 on the same computer that has a previous version of SQL Server and then repair this version of SQL Server, some Integration Services components from the previous version of SQL Server are removed.
When you install SQL Server Code-Named “Denali”, the SQL Server Integration Services Database (SSISDB) catalog is missing from the Integration Services node in Object Explorer.
If you do not upgrade to SQL Server Code-Named “Denali” from a previous version, to create the SSISDB catalog, right-click Integration Services in Object Explorer, and then click Create Catalog.
If you upgrade to SQL Server Code-Named “Denali” from a previous version, you need to complete the following steps to create the SSISDB catalog.
Create the asymmetric key named MS_SQLEnableSystemAssemblyLoadingKey by running the IALSetup.cmd (<drive>:\Program Files\Microsoft SQL Server\110\DTS\Binn). Use the following options.
Directory path to install the DependencyCatalog database to.
SQL Server instance name.
In SQL Server Management Studio, to create the SSISDB catalog, right-click Integration Services in Object Explorer, and then click Create Catalog.
By default in CTP1, BI Development Studio uses a version of Microsoft.SqlServer.Types that is not fully compatible with the latest version of SQL Server.
Because of this issue, maps and dataset queries or expressions that refer to spatial data types, SqlGeometry or SqlGeography, are not supported. Using features that depend on spatial data can cause unpredictable or wrong results. Symptoms related to this issue include the following:
When you create report expressions or run dataset queries that include references to SQL Server spatial, the error message that you see resembles the following text:
Could not load file or assembly 'Microsoft.SqlServer.Types, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. (Microsoft SQL Server Report Designer)
In the map layer wizard, if you choose the option Choose a dataset with SQL Server spatial data, BI Development Studio displays the following message.
Microsoft Visual Studio has encountered a problem and needs to close…
Workaround: Modify the devenv.exe.config file to specify the earlier version of Microsoft.SqlServer.Types. By default, the config file is in <drive>\Program Files\Microsoft Visual Studio 9.0\Common7\IDE. Add the following lines to the <runtime> section:
<assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" culture="neutral"/>
<bindingRedirect oldVersion="10.0.0.0" newVersion="18.104.22.168"/>
This change affects all BI Development Studio and Visual Studio 2008 projects.
The Report Builder 1.0 ClickOnce package does not download to client computers, and if you attempt the install, an error message indicates the ClickOnce package is corrupted. This issue occurs in the following scenarios:
You upgrade a report server to SQL Server Code-Named “Denali”, and the upgraded server was previously configured for Report Builder 1.0 as the default ClickOnce application. The SQL Server Code-Named “Denali” upgrade does not block or change the Report Builder 1.0 configuration, and it is incompatible with SQL Server Code-Named “Denali”.
After you install SQL Server Code-Named “Denali” you configure the report server to use Report Builder 1.0 instead of the default configuration for Report Builder 3.0. An error message does not appear during configuration. The error occurs when users try to open the ClickOnce Report Builder.
Workaround: There is no workaround to make Report Builder 1.0 work as the ClickOnce Report Builder application. However, you can configure your report server to use Report Builder 3.0 as the default ClickOnce Report Builder application. Report Builder 3.0 is included with SQL Server Code-Named “Denali”.
To change the default ClickOnce application in Report Manager (Native Report Server)
Start Report Manager.
Click Site Settings.
Click General in the left pane.
In Custom Report Builder Launch URL, delete the text. An empty value causes the default application to open, which is Report Builder 3.0.
To change the default ClickOnce application in SharePoint Central Administration
In SharePoint 2010 Central Administration, click the General Application Settings tab.
In the Reporting Services application section, click Set Server Defaults.
In Custom Report Builder Launch URL, delete the text. An empty value causes the default application to open, which is Report Builder 3.
When using Business Intelligence Development Studio to design a report, you might encounter the following problems:
When a report dataset uses a data source that connects to SQL Server Code-Named “Denali” and you attempt to edit the query for that dataset by using the graphical query designer, the following error occurs:
"This server version is not supported. Only servers up to Microsoft SQL Server 2005 are supported."
Workaround: Use the text-only query designer to edit the query.
When a report dataset uses a data source that connects to an earlier version of SQL Server (SQL Server 2000, SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2) and you use the graphical query designer to edit the query for that dataset, clicking the Add Table button causes the following error to appear:
"Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified."
When the report query result includes columns that contain SQL Server spatial data (such as SqlGeometry or SqlGeography), running the query in the text-only query designer causes the following error to appear:
"Could not load file or assembly 'Microsoft.SqlServer.Types, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified."
Workaround: Use SQL Server Management Studio to run the query.
When the report query result includes columns that contain SQL Server spatial data, previewing the report causes an error similar to the following to appear:
"[rsRuntimeErrorInExpression] The Value expression contains an error: The specified operation is not valid."
Workaround: Publish the report to a report server, and then run the report there.
The issues listed in section 5.3 apply to all operating systems, platforms, and install or upgrade scenarios supported in SQL Server Code-Named “Denali” CTP1.
Microsoft StreamInsight is not included with SQL Server Code-Named “Denali” CTP1.
To obtain the latest version of StreamInsight, download the appropriate package listed on this page.
If you run the upgrade advisor setup (sqlua.msi) from SQL Server Code-Named “Denali” Setup Installation Center page, you will see “Welcome to the Installation Wizard for Microsoft SQL Server 2008 R2 Upgrade Advisor”. This is because Upgrade Advisor is not currently ready for SQL Server Code-Named “Denali”. Upgrade Advisor for SQL Server Code-Named “Denali” might be available in a future CTP.
To provide feedback about a Books Online topic in this release, use the Click to Rate and Give Feedback mechanism that is part of SQL Server Books Online in the MSDN Library. Note that feedback is provided for individual topics, so you must have the topic displayed to provide feedback for it. To provide feedback about a SQL Server feature in this release, use the Connect Site.
You can join the SQL Server Community to share your experiences and learn from other people who are using SQL Server Code-Named “Denali”. For more information, see the SQL Server "Denali" Forums, SQL Server Connect Feedback Center (to search for and file bugs or suggestions), and the SQL Server Community Web site.
© 2010 Microsoft Corporation. All rights reserved.