[Company Logo Image] 

Home Up Contents Coffee Break Credits Glossary Links Search

 How to install SQL Server 2016
 

 

 

Home
Analysis Services
Azure
CLR Integration
High Availability
Open Source
Security
SQL Server 2008
SQL Server 2012
SQL Server 2014
SQL Server 2016
Tips
Troubleshooting
Tuning

How to install SQL Server 2016.


Applies to: Microsoft SQL Server 2016, Windows Server 2012


This article will guide you on how to perform a new SQL Server 2016 standalone installation.

An evaluation copy of SQL Server 2016 can be downloaded from here.

If you are upgrading to SQL Server 2016, consider these resources and recommendations:

bulletRead about supported upgrade scenarios here.
bulletDownload and run SQL Server Upgrade Advisor from here (located at the bottom of the link)
bulletUpgrade to the same language version as the existing instance of SQL Server.

However this article is not for upgrade scenarios.


The following are some recommendations before installing SQL Server 2016:
 

bulletThe computer where SQL Server will be installed should have access to the Internet.
bulletIt is not supported to install SQL Server 2016 through Terminal Services client.


Hardware Requirements.
 

bulletProcessor. SQL Server 2016 only supports 64-bit processors with a minimum speed of 1.4 Ghz (2.0 Ghz recommended).
bulletPhysical Memory (RAM). 512 MB minimum of RAM for Express Edition, but the minimum for all other editions is 1 GB of RAM (the minimum is 2 GB if Data Quality Services is going to be installed). Recommended amount of RAM for Express Edition is 1 GB of RAM, but the recommended amount of RAM for all other editions is 4 GB of RAM.


Operating Systems Requirements.
 

bulletThe recommended file system format is NTFS.
bulletDo no try to install SQL Server 2016 on a compressed, mapped, encrypted or read-only drive, because setup will block the installation.
bulletDo not install SQL Server on a Domain Controller. Click here for more information.
bulletVerify Windows Management Instrumentation service (Control Panel -> Administrative Tools -> Services) is running.
bulletConfigure your firewall to allow SQL Server access. Click here for more information about protocols and port numbers.
bulletThe user account that is running SQL Server Setup must have administrative privileges on the computer.
bulletIt can be installed on Windows Server 2012 R2, Windows Server 2012, Windows 10, Windows 8.1, Windows 8
bulletThe following operating systems are not supported: Windows 7, Windows Vista, Windows XP, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 R2, Windows Server 2003 and Windows Server 2000.
bulletAt least 6.0 GB of disk space are required by SQL Server setup.


Additional software requirements and hardware requirements:
 

bulletEnable .NET Framework 3.5. Click here to know how.
bulletSQL Server includes .NET Framework 4.6 and will install it .NET Framework 4.6. Express Edition will download it from the Internet.
bulletThe full MSDN article with hardware and software requirements of SQL Server 2016 can be found here.
bulletIf you are planning to install the "PolyBase Query Service for External Data" feature of SQL Server 2016, you need to install it on a 64-bit SQL Server instance, with Microsoft .NET Framework 4.0, Oracle Java SE RunTime Environment (JRE) version 7.51 or higher (64-bit), a minimum 4 GB of RAM, and 2 GB of disk space. For more information, click here.
 

Important notes before installing.

 

bulletSQL Server Management Studio 2016 is not part of the SQL Server 2016 media anymore. Please download it and install it from here.
bulletSQL Server Data Tools is not part of the SQL Server 2016 media anymore. Please download it from here.
bulletSQL Server 2016 does not provide a 32-bit version anymore. All SQL Server 2016 features are supported on x64 (64-bit) systems, but only the following subset of features are supported on x86 (32-bit) systems: Data Quality Client, Client Tools Connectivity, Integration Services, Client Tools Backwards Compatibility, Client Tools SDK, Documentation Components, Distributed Replay Components, Distributed Replay Controller, Distributed Replay Client, SQL Client Connectivity SDK. For more information, please click here.
bulletIt is critical for the stability of SQL Server 2016 that customers download and install this critical update for VC++ 2013 [Critical].

 







Step-by-step procedure to install SQL Server 2016.


Run SQL Server 2016 setup.









On the screen below, make a click on the "Installation" hyperlink in the left side of the screen.

The next screen shows the types of installation available.  Let's select the first type available "New SQL Server stand-alone installation or add features to an existing installation".









On the page below, specify the edition of SQL Server to install, if you are choosing to install a free edition of SQL Server 2016 or an Evaluation Edition of SQL Server 2016.

You should also provide a product key, if you are installing a licensed edition of SQL Server. Sometimes the product key is included in the media (the product key is pre-pidded).







Below image is associated with the License Terms page.  Read the license agreement and if you agree with it, check the "I accept the license terms" check box, and then click the Next button.








Below screen belongs to the set of Global Setup Rules. To have detailed information about the cause of errors and warnings you may receive click on the "Show details" button and then click on the blue hyperlinks associated with each warning/error.







On the "Microsoft Update" page, SQL Server 2016 setup is trying to get updates from Microsoft Update, and for this reason is important to have Internet access when installing SQL Server as mentioned at the beginning of this article. Make a click on the checkbox to get the updates, if the computer has Internet access, then click on the Next button.












The next screen belongs to the Install Rules page. To have detailed information about the cause of errors and warnings you may receive on this page, click on the blue hyperlinks associated with each warning/error.

About the Windows Firewall warning you are seeing on this image, you can go ahead with the installation of SQL Server, but when it finishes configure your Windows Firewall to allow SQL Server access or disable it. Click here to know how to configure Windows Firewall for SQL Server access.

Alternatively, you can opt to turn off Windows Firewall if you are installing SQL Server for personal use. You can go to Control Panel and turn it off







On the Feature Selection page, please select the features you would like to install. A description of each feature will appear on the "Feature description" area when you click on a feature. For a detailed description of each feature, please click here.






Once you have selected the features to install, please click on the "Next" button.







The next screen is the "Feature Rules" and a common warning on this screen is shown below. The warning says "Post-installation steps are required for Advanced Analytics Extensions".

If you are planning to use SQL Server R services after installing SQL Server 2016, you must perform some additional steps to register the extensions and to provision required accounts. The steps are outlined here.







On the Instance Configuration page, select a default or named instance for your installation. SQL Server supports multiple installations on the same computer, each installation receives the name of "instance". The default instance gets the name of the computer, but the named instances, receive the name of the computer plus the name provided by the user on this setup page. To access a default instance once it is installed, using SQL Server Management Studio or any other program, you just need provide the computer name. To access a named instance, you will need to provide the name of the instance in the forma of computername\nameoftheinstance.






On the PolyBase Configuration page of SQL Server setup, select the standalone option to configure this SQL Server instance as a standalone PolyBase head node.

Choose the second option to use this instance as part of a PolyBase scale-out group, and this will open the firewall to allow incoming connections to the SQL Server Database Engine, SQL Server PolyBase Engine, SQL Server PolyBase Data Movement service and SQL Browser. The firewall will be opened to allow incoming connections from other nodes in a PolyBase scale-out group. Selecting the scale out option option will also enable Microsoft Distributed Transaction Coordinator (MSDTC) firewall connections and modify MSDTC registry settings. For more information about what scale-out option to choose, click here.
 

Please, specify a port range with at least six ports also. SQL Server setup will allocate the first six available ports from the range.






On the following screen you need to provide the service accounts that SQL Server services will use. As you can notice, SQL Server setup provides virtual accounts by default, they are auto-managed, they can access the network on a domain environment by using the credentials of the computer account.

However, I still recommend to create a local user or use a domain user account to start SQLServer services.

If the computer is not part of a domain, use a local user account without Windows administrator permissions. You can create this account using Control Panel -> User Accounts. Please provide a strong password to this account since SQL Server setup will required it on this "Server Configuration" page.

Use a Domain User Account if the service must interact with network services or access domain resources. This account should be pre-created by a domain administration in your environment.

Whether you create a local user or a domain user account, the password you use to create the account must be a strong password since SQL Server setup will required it on this "Server Configuration" page.

You can also use built-in accounts (the Network Service account, Local Service, Local System) as service accounts. However, I would not recommend to use Local Service Account for SQL Server (MSSQLSERVER). Use Local System if you need a very high-privileged account, or you are having issues installing SQL Server using virtual accounts as service accounts. It has extensive privileges on the local system.

Microsoft recommends you to specify an individual account for each service. The service accounts used for this configuration must have a strong password as mentioned above, otherwise you will get the error "Invalid or missing username or password. To continue, provide valid credentials for the SQL Server Agent service".  A strong password  is one that has a combination of letters in uppercase, lowercase, numbers and special characters.






To provide a local Windows account as SQL Server service account, you need to open Computer Management and create a standard user account as shown in the image below.





Replace default existent service account on the Server Configuration page with the newly created local account, with a Domain Account for built-in account as Local System. Look at below images to know how to change a service account.







Write the name of the account we created or the name of the domain account, click on Check Names to verify the name is correct, and then click the OK button.






You can do the same for the first 4 SQL Server services: SQL Server Agent, SQL Server Database Engine, SQL Server Analysis Services and Reporting Services.







If you click on the Next button, and you receive an error message ("There are validations errors on this page"), probably you did not provide a strong password for the service account, or maybe the password does not match with the password the account has on Windows or on Active Directory. If you cannot get rid of this message, change the service account specified at the bottom of the page (with the red balloon) to Local System my work.

On the next screen, the Database Engine Configuration page (see below image), choose the authentication mode to use for your SQL Server installation.  If you select Mixed Mode, Setup creates an sa account.

Enter and confirm the password for the (sa) login when you choose Mixed Mode Authentication.

You will get the error "Missing system administrator account. To continue, provide at least one Windows account to provision ...", if you fail to provide SQL Server administrators and try to continue with the next page of Setup.  The error message "There are validation errors on this page ..." will also appear. Click the buttons "AddCurrent User" or "Add ..." to provide at least one account that will have unrestricted access to the SQL Server instance.







Click on the "Data Directories" tab (above image), to change the location of SQL Server default directories, if you prefer them to be hosted on another disk drive/partition. For information about default location of files on SQL Server instances, please click here.







Now on the TempdDB tab of the Database Engine Configuration page of SQL Server 2016 setup, you have the opportunity to configure TempDB settings.

SQL Server setup will allow you to set a maximum 256 MB for the size of TempDB data file and the same for the size of TempDB log file. This is because of the impact of the impact on installation time. The size of both database files can be set higher after SQL Server setup finishes installation.







Use the FileStream tab on below screen to configure FileStream settings on this instance. To enable it, select "Enable FILESTREAM for Transact-SQL access".

Select "Enable FILESTREAM for file I/O streaming access" to enable Win32 streaming access for FileStream.

On the "Windows share name" text box, to enter the name of the Windows share in which the FileStream data will be stored.

Select "Allow remote clients to have streaming access to FILESTREAM data" to allow remote clients to access this FileStream data on this server.


For more information about enabling and configuring FileStream, please click here.








On the "Analysis Services Configuration Page" (bellow image), please select "Install Analysis Services in Multidimensional and Data Mining Mode" to install Analysis Services with support for online analytical processing databases and data mining models.

Select "Tabular Mode" to install Analysis Services with support for tabular models.

Each mode is exclusive of the other.

Please provide also a user account that will be an Analysis Services administrator.







On the Reporting Services Configuration page (above), choose to install Reporting Services on Native Mode or SharePoint Integrated Mode.







On the Feature Configuration Rules page, if the status of all rules is passed, just click on the Next button. To have detailed information about the cause of errors and warnings you may receive on this page, click on the blue hyperlinks associated with each warning/error.







On the Ready to Install page, review the summary of features and components for your SQL Server installation. To proceed, click Install.













On the "Complete" page (above image), you can view the Setup summary log by clicking the blue link provided on the bootom this page. To exit the SQL Server Installation Wizard, click Close.





 


If the installation fails or you experience any issue on your computer please create a thread on any of the following SQL Server forums:

 

bulletSQL Server Setup Forum (English). Click here.
bulletMSDN Data Foro (Spanish). Click here.
bulletMSDN SQL Server Forum (French). Click here.
bulletMSDN SQL Server fórum - Gerenciamento, Configuração, Instalação, e Segurança (Portuguese - Brazil). Click here.
bulletMSDN SQL Server Forum (Chinese Simplified). Click here.
bulletMSDN 포럼 (Korean).  Click here.
bulletMSDN SQL Server (Japanese). Click here.
bulletMSDN SQL Server (German). Click here.
bulletMSDN Работа с данными (Russian). Click here.



 

 

 

.Send mail to webmaster@sqlcoffee.com with questions or comments about this web site.