SQL Server Express users: click Feature Selection (SQL Server Express) for information that is specific to SQL Server Express Setup.
Use the Feature Selection page of the Microsoft SQL Server Installation Wizard to select individual features for your installation, and to specify an installation directory. For an existing installation, use this page to add or remove features.
The Feature Selection page consists of two panes. The left pane shows a tree view of the features that you can install and you can expand a feature to view its subfeatures. The right pane displays feature descriptions. When you click a feature or subfeature, the Feature description pane displays a description of the selection and its disk space requirements.
To add or remove a feature, click the arrow next to the feature name, and then choose one of the following options from the drop-down list:
- Will be installed on local hard drive
Install the selected feature in the location shown under Installation Path.
- Entire feature will be installed on local hard drive
Install the selected feature and all subfeatures. Expand the parent feature to view its subfeatures.
Will be installed to run from network
Run the following from a network location:
- Replication Monitor
Entire feature will be unavailable
For a new installation of SQL Server, this option passes over the installation of the selected feature. For an existing installation, this option removes the feature from the installation. After you select this option, a red X appears on the feature tree next to the feature name, and the icon on any parent features in the tree view appears dimmed.
You cannot clear a feature if one of its subfeatures is selected. In order to deselect a feature, make sure that all of its subfeatures are also deselected.
The Feature Selection page also offers the following options:
During Setup, you can change the installation path for the following features:
The installation path is displayed only for features with a user-configurable destination folder:
Component Default path1, 2 Configurable or fixed path
Database Engine server components
\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\Binn\
Database Engine data files
\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\Data\
Analysis Services server
\Program Files\Microsoft SQL Server\MSSQL.n\OLAP\Bin\
Analysis Services data files
\Program Files\Microsoft SQL Server\MSSQL.n\OLAP\Data\
Reporting Services report server
\Program Files\Microsoft SQL Server\MSSQL.n\Reporting Services\ReportServer\Bin\
Reporting Services report manager
\Program Files\Microsoft SQL Server\MSSQL.n\Reporting Services\ReportManager\Bin\
<Install Directory>\90\Notification Services\
Replication and server-side COM objects
Program Files\Microsoft SQL Server\90\COM\5
Integration Services component DLLs for the Data Transformation Run-time engine, the Data Transformation Pipeline engine, and the dtexec command prompt utility
Program Files\Microsoft SQL Server\90\DTS\Binn
DLLs that provide managed connection support for Integration Services
Program Files\Microsoft SQL Server\90\DTS\Connections
DLLs for each type of enumerator that Integration Services supports
Program Files\Microsoft SQL Server\90\DTS\ForEachEnumerators
SQL Server Browser Service, WMI providers
\Program Files\Microsoft SQL Server\90\Shared\
Components that are shared between all instances of SQL Server 2005
\Program Files\Microsoft SQL Server\90\Shared\
1Make sure that the \Program Files\Microsoft SQL Server\ folder is protected with limited permissions.
2 The default drive for these locations is systemdrive, normally drive C.
3Installation paths for child features are determined by the installation paths of their parent features.
4A single installation path is shared between Integration Services, Notification Services, and Client Components. Changing the installation path for one component also changes it for other components. Subsequent installations will install components to the same location as the original installation.
5This directory is used by all instances of SQL Server on a computer. If you apply an update, like a service pack, to any of the instances on the computer, any changes to files in this folder will affect all instances on the computer.
For clustered configurations, you must select a local drive that is available on every node of the cluster.
When adding features to an existing installation, you cannot change the location of a previously installed feature, nor can you specify the location for a new feature.
When you specify an installation path during Setup for the server components or data files, the Setup program uses the instance ID in addition to the specified location for program and data files. Setup does not use the instance name for tools and other shared files. Setup also does not use any instance name for the Analysis Services program and data files, although it does use the instance name for the Analysis Services repository.
For more information about installation directories, see File Locations for Default and Named Instances of SQL Server 2005.
For more information about hard disk space requirements, see Hardware and Software Requirements for Installing SQL Server 2005.
If you set an installation path for the "Database Engine" feature, SQL Server Setup will use that path as the root directory for all instance-specific folders for that installation, including "SQL Data Files." In this case, if you set the root to "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\," instance-specific directories will be tacked onto that path.
Customers choosing to use the USESYSDB upgrade functionality in the SQL Server Installation Wizard (Setup UI mode) can easily lead themselves into a situation where the product gets installed into a recursive folder structure - for example, <SQLProgramFiles>\MSSQL.1\MSSQL\MSSQL.1\MSSQL\Data\. Instead, to use the USESYSDB feature, set an installation path for the "SQL Data Files" feature instead of the "Database Engine" feature.
Note: Data files are always expected to be found in a child directory named "Data." For example, specify "C:\Program Files\Microsoft SQL Server\MSSQL.1\" to specify the root path to the data directory of the system databases during upgrade when data files are found under "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data."
Note: You cannot install SQL Server Windows on Windows (WOW64) to the root directory of a physical disk. Configurable paths must be specified to a node below the root directory. For example, you cannot install Database Engine server components to c:\. You can install the Database Engine server components to c:\SQL Server\. For more information about WOW64 see Extended System Support in Hardware and Software Requirements for Installing SQL Server 2005.
Installing AdventureWorks Sample Databases
AdventureWorks Sample OLTP, AdventureWorksDW Sample Data Warehouse, and AdventureWorks Sample OLAP, and related samples are not installed by default. To install one or more of these features, select Workstation Components, Books Online, and Development Tools from the Components to Install page during SQL Server 2005 Setup and then click Advanced. Expand Documentation and Samples and then select the databases and samples to be installed.
Launches the Change Folders page, which allows you to change the folder where the selected feature will be installed. This button is available only for features with a user-configurable installation path. Installation paths for a child feature is determined by the installation path of its parent feature. For more information on installation paths, see File Locations for Default and Named Instances of SQL Server 2005.
Displays the available space for installing to different system drives on your computer. After examining the disk space on your computer in the Disk Cost dialog box, click Close to continue installing SQL Server.
Browse… and Disk Cost… buttons on this page are disabled for failover cluster installations, as failover cluster installations have a separate Installation Folders page.