Before you install SQL Server Code-Named “Denali”, read the following required actions.
1.1 Installation Prerequisite Handling During SQL Server Code-Named
“Denali” Setup
The following items describe the prerequisite installation behavior during SQL Server Code-Named “Denali” Setup:
-
Installing SQL Server Code-Named “Denali” is supported only on Windows 7 SP1 or Windows Server 2008 R2 SP1. However, Setup does not block installing SQL Server Code-Named “Denali” on Windows 7 or Windows Server
2008 R2.
-
The .NET Framework 3.5 SP1 is a requirement for SQL Server Code-Named “Denali” when you select Database Engine, Replication, Master Data Services, Reporting Services, Data Quality Services (DQS), or SQL Server
Management Studio, and the framework is no longer installed by SQL Server Setup.
-
If you run Setup on a computer with the Windows Vista SP2 or Windows Server 2008 SP2 operating system, and you do not have the .NET Framework 3.5 SP1 installed, SQL Server Setup requires you to download and install
the .NET Framework 3.5 SP1 before you can continue with the SQL Server installation. The error message includes a link to the Download Center, or you can download the .NET Framework 3.5 SP1 from Windows Update. To avoid the interruption during SQL Server Setup,
you can download and install the .NET Framework 3.5 SP1 before you run SQL Server Setup.
-
If you run Setup on a computer with the Windows 7 SP1 or Windows Server 2008 R2 SP1 operating system, you must enable the .NET Framework 3.5 SP1 before you install SQL Server Code-Named "Denali".
-
The .NET Framework 4 is a requirement for SQL Server Code-Named “Denali”. SQL Server Setup installs the .NET Framework 4 during the feature installation step. SQL Server Express does not install the .NET Framework
4 when installing on the Windows Server 2008 R2 SP1 Server Core operating system. You must install the .NET Framework 4 before you install SQL Server Express on a Windows Server 2008 R2 SP1 Server Core operating system.
-
To make sure that the Visual Studio component can be installed correctly, 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 system, you must enable the .NET Framework 3.5 SP1 before you install SQL Server Code-Named "Denali".
The .NET Framework 4 is a requirement for SQL Server Code-Named “Denali”. SQL Server Setup installs the .NET Framework 4interruption during SQL Server Setup, you can download and install the update as described below before running SQL Server Setup (or you can install all the updates
for the .NET Framework 3.5 SP1 that are available on Windows Update):
Windows PowerShell 2.0 is a pre-requisite for installing SQL Server Code-Named “Denali” Database Engine components and SQL Server Management Studio, but Windows 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.
1.2 Supported Operating Systems for SQL Server Code-Named “Denali”
Evaluation Edition
SQL Server Code-Named “Denali” Evaluation Edition is supported on the Windows Vista SP2, Windows Server 2008 SP2, Windows 2008 R2 SP1, and Windows 7 SP1 operating systems.
1.3 Installing SQL Server Code-Named “Denali” on Windows
Server 2008 R2 Server Core Service Pack 1
Starting with SQL Server Code-Named “Denali” CTP3, you can install SQL Server on Windows Server 2008 R2 Server Core SP1, with the following limitations:
- Microsoft SQL Server Code-Named “Denali”, Community Technology Preview 3 (CTP 3) does not support Setup using the installation wizard on the Server Core operating system. When installing on Server Core, SQL Server Setup supports full quiet mode by using
the /Q parameter, or Quiet Simple mode by using the /QS parameter.
- Upgrade of an earlier version of SQL Server to Microsoft SQL Server Code-Named “Denali”, Community Technology Preview 3 (CTP 3) is not supported on a computer that is running Windows Server 2008 R2 Server Core SP1.
- Installing a 32-bit version of Microsoft SQL Server Code-Named “Denali”, Community Technology Preview 3 (CTP 3) edition is not supported on a computer running Windows Server 2008 R2 Server Core SP1.
- Microsoft SQL Server Code-Named “Denali”, Community Technology Preview 3 (CTP 3) cannot be installed side-by-side with earlier versions of SQL Server on a computer that is running Windows Server 2008 R2 Server Core SP1.
- When you try to launch the SQL Server Setup by running “setup.exe /QS” on Server Core without specifying /Action, Setup will open the SQL Server Installation Center and will not be able to proceed with the installation. The workaround is to specify an action
using the /Action command line parameter.
- Microsoft Sync Framework is supported on Windows Server 2008 R2 Server Core SP1. You can download the appropriate version of Sync Framework from this
Microsoft Download Center page (http://go.microsoft.com/fwlink/?LinkId=221788) and install it on a computer
that is running Windows Server 2008 R2 Server Core SP1.
1.4 “Test” Update Available to Try New Product Update Feature
In this release of SQL Server, you can try out the new Product Update feature. This feature integrates the latest product updates with the main product installation so that the main product and its applicable
updates are installed at the same time. Product Update can search Microsoft Update, Windows Server Update Services (WSUS), a local folder, or a network share for applicable updates.
For this CTP release, the test update will not be distributed to WSUS. When SQL Server 2011 releases, updates will be available to WSUS under the product “SQL Server 2011 Product Updates For Setup”. After a WSUS
administrator approves, any client that is pointed to the WSUS service will see these updates. For this CTP release, you can still verify the WSUS functionality by importing from the Microsoft Update Catalog. To do this, follow these steps:
- Right-click the Updates node within your WSUS server, and then click
Import Updates.
- In the Search box, search for SQL Server "Denali" CTP3 Test Update.
- Select the update to add, and then click View Basket.
- Select Import directly into Windows Server Update Services.
- Approve the imported update.
For more information about the Product Updates feature in SQL Server Code-Named “Denali”, see "Product Updates" in the SQL Server "Denali" Installation topic.
1.5 Setup Error on Windows Vista and Windows Server 2008
SQL Server Code-Named “Denali” 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).
You might see the following error:
"This package is not applicable."
1.6 Renaming the SQL Network Name Resource Is Not Supported in SQL Server
Code-Named "Denali"
SQL Server Code-Named “Denali” 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.
1.7 Instance Name Ending with '$' Fails Validation During Setup on Clustered
Environment
SQL Server Setup requires user to define the Instance Name for new installations. If you define an instance name that ends with "$", in the
Server Configuration page where accounts for services are identified, Setup fails to validate the default accounts derived from instance names. You will see the following validation error in the Setup UI or in the Detail.txt setup log if the
setup is run on the command line:
1.7 Instance Name Ending with '$' Fails Validation During Setup on Clusteredpt 30pt;">
“The name provided is not a properly formed account name.”
Workaround: Change the instance name while making sure the instance does not end with "$". Or, you can change service accounts that end with "$" and use another account, such as a service account,
that is appropriate for this purpose.
1.8 A Cluster Group Name that Includes a "\" or "'" Will Cause Setup to Fail When
Installing a Clustered Instance
SQL Server Setup requires users to specify a name for the SQL Server cluster resource group for new cluster installations. If you define an cluster group name that includes a "\" or “ ‘ “, setup will later fail when configuring cluster group. You might see
an error similar to the following:
“The cluster group ‘MYGROUP\WITHBACKSLASH’ could not be created.”
Workaround: Change the cluster group name while making sure the instance does not include “\” or “ ‘ ”.
1.9 Semantic Search Requires You to Install an Additional Dependency
Statistical Semantic Search has an additional prerequisite, the semantic language statistics database, which is not installed by the SQL Server Setup program.
Workaround: To set up the semantic language statistics database as a prerequisite for semantic indexing, do the following things:
- Locate and run the Windows Installer package named SemanticLanguageDatabase.msi
on the SQL Server installation media to extract the database. For SQL Server Code-Named “Denali” Express, download the semantic language statistics database from
Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=221787), and then run the Windows Installer
package.
- Move the database to an appropriate data folder. If you leave the database in the default location, you must change permissions before you can attach it successfully.
- Attach the extracted database.
- Register the database by calling the stored procedure sp_fulltext_semantic_register_language_statistics_db and providing the name that you gave to the database when you attached it.
If these tasks are not completed, you will see the following error message when you try to create a semantic index:
Msg 41209, Level 16, State 3, Line 1
A semantic language statistics database is not registered. Full-text indexes using 'STATISTICAL_SEMANTICS' cannot be created or populated.
1.10 Sync Framework Is Not Included in the Installation Package
Sync Framework is not included in the SQL Server Code-Named "Denali" CTP3 installation package. You can download the appropriate version of Sync Framework from
this Microsoft Download Center page.
1.11 Using Denali's SharePoint Features Requires SharePoint Server 2010 SP1
If you plan to use SQL Server Code-Named "Denali" features in a SharePoint environment, then SharePoint Server 2010 Service Pack 1 (SP1) is required.
Workaround: You must install SP1 and fully patch the server farm before you add SQL Server features to the farm. This requirement applies to the following Denali features: using an instance of
Database Engine as the farm's database server, configuring PowerPivot for SharePoint, or deploying Reporting Services in SharePoint mode.
2.1 Cannot Create or Open Tabular Projects When BUILTIN\Administrators
Group Name Cannot Be Resolved
You must be an administrator on a workspace database server before you can create or open tabular projects. A user can be added to the server administrators group by adding the user name or group name. If you
are a member of the BUILTIN\Administrator group, you cannot create or edit BIM files unless the workspace database server is joined to the domain from which it was originally provisioned. If you open or create the BIM file, it will fail with the following
error message:
"The BIM file cannot be opened. The server connected to is not valid. Reason: You are not an administrator of server [server name]."
Workarounds:
- Re-join the workspace database server and Business Intelligence Development Studio (BIDS) computer to the domain.
- If the workspace database server and/or BIDS computers are not going to be domain joined at all times, add individual user names instead of the BUILTIN\Administrators group as administrators on the workspace database server.
2.2 RS Data Driven Subscriptions Might Not Work Against an AS Data Source
SQL Server 2008 Analysis Services (AS) OLE DB Provider uncot;The BIM file cannot be opened. The server connected to is not valid. Reason: You are not an administrator of server [server name]."
Workarounds:
- Re-join the workspace database server and Business Intelligence Development Studio (BIDS) computer to the domain.
- If the workspnditionally overwrites the registry to point to itself as the latest provider, whether or not a newer provider is installed. Data Driven Subscriptions
within Reporting Services (RS) require the SQL Server Code-Named "Denali" provider to work.
Office 2010 installs the SQL Server 2008 provider. In the case where Office is installed after Denali, the SQL Server 2008 provider declares itself as the latest even though it is not. If you attempt to create
or edit a Data Driven Subscription with a Delivery Query that obtains data from Analysis Services using MDX, then you receive the following error:
"The dataset cannot be generated. An error occurred while connecting to a data source, or the query is not valid for the data source.
Workaround: Repair the Denali CTP3 version of Microsoft Analysis Services OLE DB Provider for Microsoft SQL Server.
2.3 Installing SQL Server 2008
R2 after installing SQL Server Denali causes parse failures in the Reporting Services Query Designer
Create a new report project in SQL Server Denali. Add a new dataset to this report. Open the Query Designer and add a query. You might receive the following error message:
"Query preparation failed. Failed to parse the query to detect if it is MDX or DMX. (MDXQueryGenerator)"
Workaround: This error message occurs only if you install SQL Server 2008 R2 after installing SQL Server Denali. To fix the problem, re-install the MSOLAP provider using the Denali provider.
Download SQL Server Code-Named “Denali” CTP3
from the Download Center page.
2.4 Databases Cannot Be Restored Using SSMS When a Server Only Has
Models in DirectQuery Mode
You cannot restore a database by using SQL Server Management Studio (SSMS) when the server only has models in DirectQuery Mode.
If you install an Analysis Services instance running in VertiPaq mode, deploy only DirectQuery models to it, right-click any database, click Restore or Restore from PowerPivot, and click Browse to find the follow,
then the following error message appears:
"DirectQuery error: MDX/SQL operations are not supported in DirectQuery mode."
Workaround: You can restore the database by using XMLA script, PowerShell, or AMO. You can use SSMS to restore DirectQuery models if there is at least one VertiPaq model on the server.
2.5 Creating Partitions After Deployment Can Fail the Next Deployment
Processing might fail after you re-deploy a model with modified partition definition queries.
For example, you might start with a model with one partition (Partition 1), deploy and process this model, leave your data unchanged, and modify your partition definition. Then you define a second partition (Partition
2) that includes a subset of the previous data set for Partition 1 and then deploy and process your model. When the model is deployed and processed using the Default processing option command, the engine says that there is no need to process Partition 1, since
it already has data, and therefore it introduces duplicate data into the model when Partition 2 is processed.
Workarounds:
- Before you re-deploy your model, go to SQL Server Management Studio (SSMS), right-click the database, and then click
Process Database. Select the Process Clear option from the dialog box, and then click
OK. This removes all the data from your database, and then you can deploy and process from Business Intelligence Development Studio (BIDS) as expected.
- Change your deployment setting for the model. Right-click your .smproj file, and then click
Properties. Change the Processing Option property from
Default to Do Not Process or Full.
2.6 Metadata Pane in SSMS Is Empty When You Browse an AS Database
The metadata pane is empty when you browse an Analysis Services (AS) database in SQL Server Management Studio (SSMS).
For example, if you open SSMS, connect to an AS server, right-click a database, and then click
Browse, the metadata pane in the cube browser is empty.
Workaround: Drag the metadata pane to resize it, or switch from Design mode to Text mode. This will show the model metadata and allow you to drag-and-drop into the cube browser.
2.7 Working with Large Models Can Be Difficult to Navigate
In tabular modeling, when you work on a model with many tables, the table tabs do now allow scrolling like they do in Excel. Navigating the tables is a challenge when you have about 10 or more tables.
Workarounds:
- You can drag a table from the list and position the tab where you want, so that you can access specific tabs more easily.
- You can rearrange the order and position of the existing tabs.
In the SQL Server Management Studio (SSMS) Connection Properties dialog box for tabular models, the Connection Manager shows the wrong provider for some types of connections, such as data feeds.
Workaround: Manually type the connection string in the Connection Properties dialog box rather than using the Connection Manager.
2.11 Filtering Members from Different Levels of a Hierarchy Causes an Error
With SQL Server Analysis Services installed in tabular mode, Data Analysis Expressions (DAX) and Multidimensional Expressions (MDX) queries against a tabular model that involve arbitrary shapes with mixed granularity
will fail with an error message that indicates such queries are not supported in VertiPaq mode. You see the following error in the PivotTable:
“The query requires the generation of a data request involving a slice that consists of an arbitrary-shaped set with tuples from different hierarchy levels, which is not supported when using Analysis Services
in VertiPaq mode.”
2.12
Installing BIDS Fails to Load the VSTS Package
If you install and open Business Intelligence Development Studio (BIDS) and then create a new Analysis Services, Reporting Services, or Integration Services project, the following error message appears:
"'VSTS for Database Professionals SQL Server Data-tier Application' package didn't load correctly"
You can ignore this message if you want to work with Analysis Services, Reporting Services, or Integration Services.
Workaround: To work with the data applications, install Project Juneau after you install BIDS.
2.13 BIDS Stops Responding When You Copy a Large Amount of Data to the Clipboard
If you copy a large amount of data to the clipboard or select many columns and rows in a tabular model project, Business Intelligence Development Studio (BIDS) stops responding.
Workaround: Copy only small data sets from the tabular project.
2.14 Overriding a Database in Restore from PowerPivot Is Not Supported
In the Restore from PowerPivot dialog box, you can find an
Override Database checkbox. Overriding a database when restoring a PowerPivot workbook is not supported for the SQL Server Code-Named "Denali" CTP3 release of PowerPivot.