Install Microsoft SQL Server

Overview

This topic provides a step-by-step procedure for installing a new instance of SQL Server 2016 using the SQL Server setup installation wizard. The SQL Server Installation Wizard provides a single feature tree for installation of all SQL Server components so that you do not have to install them individually. For more information on various components that can be installed, see Installation for SQL Server 2016.

Before You Begin

For local installations, you must run Setup as an administrator. If you install SQL Server from a remote share, you must use a domain account that has read and execute permissions on the remote share.

To install SQL Server 2016

1. Insert the SQL Server installation media. From the root folder, double-click Setup.exe. To install from a network share, locate the root folder on the share, and then double-click Setup.exe.
The Installation Wizard runs the SQL Server Installation Center. To create a new installation of SQL Server, click Installation in the left-hand navigation area, and then click New SQL Server stand-alone installation or add features to an existing installation.
2. On the Product Key page, select an option to indicate whether you are installing a free edition of SQL Server, or a production version of the product that has a PID key.
To continue, click Next.
3. On the License Terms page, review the license agreement and, if you agree, select the I accept the license terms check box, and then click Next.
4. In the Global Rules window, the setup procedure will automatically advance to the Product Updates window if there are no rule errors.
5. The Microsoft Update page will appear next if the Microsoft Update check box in Control Panel\All Control Panel Items\Windows Update\Change settings is not checked. Putting a check in the Microsoft Update page will change the computer settings to include the latest updates when you scan for Windows Update.
6. On the Product Updates page, the latest available SQL Server product updates are displayed. If no product updates are discovered, SQL Server Setup does not display this page and auto advances to the Install Setup Files page.
7. On the Install Setup files page, Setup provides the progress of downloading, extracting, and installing the Setup files. If an update for SQL Server Setup is found, and is specified to be included, that update will also be installed.
8. On the Setup Role page, select SQL Server Feature Installation, and then click Next to continue to the Feature Selection page.
9. On the Feature Selection page, select the components for your installation. A description for each component group appears in the Feature description pane after you select the feature name. You can select any combination of check boxes. The minimum required features to deploy DynThings are the following:
Database Engine Services (no need for inner nodes).
Integration Services.
The prerequisites for the selected features are displayed in the Prerequisites for selected features pane. SQL Server Setup will install the prerequisite that is not already installed during the installation step described later in this procedure.
You can also specify a custom directory for shared components by using the field at the bottom of the Feature Selection page. To change the installation path for shared components, either update the path in the field at the bottom of the dialog box, or click Browse to move to an installation directory. The default installation path is C:\Program Files\Microsoft SQL Server\130\.
The path specified for the shared components must be an absolute path. The folder must not be compressed or encrypted. Mapped drives are not supported.
If you are installing SQL Server on a 64-bit operating system, you will see the following options:
Shared feature directory
Shared feature directory (x86)
The path specified for each of the above options must be different.
The Feature Rules window will automatically advance if all rules pass.
10. On the Instance Configuration page, specify whether to install a default instance or a named instance.
Instance ID — By default, the instance name is used as the Instance ID. This is used to identify installation directories and registry keys for your instance of SQL Server. This is the case for default instances and named instances. For a default instance, the instance name and instance ID would be MSSQLSERVER. To use a non-default instance ID, specify a different value for Instance ID text box.You should not change the default instance ID unless you have already used the default instance for another project.
Typical stand-alone instances of SQL Server 2016, whether default or named instances, do not use a non-default value for the Instance ID.
All SQL Server service packs and upgrades will apply to every component of an instance of SQL Server.
Installed instances — The grid shows instances of SQL Server that are on the computer where Setup is running. If a default instance is already installed on the computer, you must install a named instance of SQL Server 2016.
The Workflow for the rest of the installation depends on the features that you have specified for your installation. You might not see all the pages, depending on your selections.
Use the Server Configuration — Service Accounts page to specify login accounts for SQL Server services. The actual services that are configured on this page depend on the features that you selected to install.
You can assign the same login account to all SQL Server services, or you can configure each service account individually. You can also specify whether services start automatically, are started manually, or are disabled. Microsoft recommends that you configure service accounts individually to provide least privileges for each service, where SQL Server services are granted the minimum permissions they have to have to complete their tasks.
To specify the same logon account for all service accounts in this instance of SQL Server, provide credentials in the fields at the bottom of the page.
Important:
Do not use a blank password. Use a strong password.
Use the Server Configuration — Collation page to specify non-default collations for the Database Engine and Analysis Services.
Use the Database Engine Configuration - Server Configuration page to specify the following:
Security Mode — Select Mixed Mode Authentication, you must provide a strong password for the built-in SQL Server system administrator account. After a device establishes a successful connection to SQL Server, the security mechanism is the same for both Windows Authentication and Mixed Mode.
SQL Server Administrators — You must specify at least one system administrator for the instance of SQL Server. To add the account under which SQL Server Setup is running, click Add Current User. To add or remove accounts from the list of system administrators, click Add or Remove, and then edit the list of users, groups, or computers that will have administrator privileges for the instance of SQL Server.
12.Use the Database Engine Configuration - Data Directories page to specify non-default installation directories. To install to default directories, click Next.
Important
If you specify non-default installation directories, ensure that the installation folders are unique to this instance of SQL Server. None of the directories in this dialog box should be shared with directories from other instances of SQL Server.
13. Use the Analysis Services Configuration — Account Provisioning page to specify the server mode and the users or accounts that will have administrator permissions for Analysis Services. Server mode determines which memory and storage subsystems are used on the server. Different solution types run in different server modes. If you plan to run multidimensional cube databases on the server, choose the default option, Multidimensional and Data Mining server mode. Regarding administrator permissions, you must specify at least one system administrator for Analysis Services. To add the account under which SQL Server Setup is running, click Add Current User. To add or remove accounts from the list of system administrators, click Add or Remove, and then edit the list of users, groups, or computers that will have administrator privileges for Analysis Services. For more information about server mode and administrator permissions, see Analysis Services Configuration - Account Provisioning.
When you are finished editing the list, click OK. Verify the list of administrators in the configuration dialog box. When the list is complete, click Next.
14. Use the Analysis Services Configuration — Data Directories page to specify non-default installation directories. To install to default directories, click Next.
Important
When installing SQL Server, if you specify the same directory path for INSTANCEDIR and SQLUSERDBDIR, SQL Server Agent and Full Text Search do not start due to missing permissions.
If you specify non-default installation directories, ensure that the installation folders are unique to this instance of SQL Server. None of the directories in this dialog box should be shared with directories from other instances of SQL Server.
15. Use the Reporting Services Configuration page to specify the kind of Reporting Services installation to create.
After you choose an option, click Next to continue.
16. Use the Distributed Replay Controller Configuration page to specify the users you want to grant administrative permissions to for the Distributed Replay controller service. Users that have administrative permissions will have unlimited access to the Distributed Replay controller service.
Click the Add Current User button to add the users to whom you want to grant access permissions for the Distributed Replay controller service. Click the Add button to add access permissions for the Distributed Replay controller service. Click the Remove button to remove access permissions from the Distributed Replay controller service.
To continue, click Next.
17. Use the Distributed Replay Client Configuration page to specify the users you want to grant administrative permissions to for the Distributed Replay client service. Users that have administrative permissions will have unlimited access to the Distributed Replay client service.
Controller Name is an optional parameter, and the default value is <blank>. Enter the name of the controller that the client computer will communicate with for the Distributed Replay client service. Note the following:
If you have already set up a controller, enter the name of the controller while configuring each client.
If you have not yet set up a controller, you can leave the controller name blank. However, you must manually enter the controller name in the client configuration file.
Specify the Working Directory for the Distributed Replay client service. The default working directory is <drive letter>:\Program Files\MicrosoftSQL Server\DReplayClient\WorkingDir\.
Specify the Result Directory for the Distributed Replay client service. The default result directory is <drive letter>:\Program Files\MicrosoftSQL Server\DReplayClient\ResultDir\.
To continue, click Next.
18. The Ready to Install page shows a tree view of installation options that were specified during Setup. On this page, Setup indicates whether the Product Update feature is enabled or disabled and the final update version.
To continue, click Install. SQL Server Setup will first install the required prerequisites for the selected features followed by the feature installation.
During installation, the Installation Progress page provides status so that you can monitor installation progress as Setup continues.
After installation, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the SQL Server installation process, click Close.
19. If you are instructed to restart the computer, do so now. It is important to read the message from the Installation Wizard when you have finished with Setup. For more information, see View and Read SQL Server Setup Log Files.