In part 2, I showed you how to build an Active Directory Domain Controller. In this part, we shall build a SQL Server 2014 SP1 database server. The following steps are to install SQL Server 2014 SP1. These steps do not necessarily include hardening and enterprise grade configuration, but I have added two critical steps which is part of best practices, i.e. custom instance name and SPN configuration. .Net Framework 3.5 is a mandatory pre-requisite. You can verify and install it using Add Roles and Features Wizard under Features as shown in Figure 1.
Run SQL Server setup.exe and under installation, select New SQL Server stand-alone installation or add features to an existing installation.
- Enter your Product Key (or select evaluation) and click next. Click next after accepting the License Terms.
- Select Use Microsoft Update to check for updates (recommended) and click next.
- Click next
- On the Setup Role, select SQL Server Feature Installation and click next.
- Select Database Engine Services along with other required Shared Features as showing in Figure 7 and 8
- Click on Named Instance and enter the name of Instance you wish to select. In this case, I have added SP2016SQL. Click Next.
- Change the default account name to SQL Server Service Account that you have created in Active Directory. If you have not yet created, use Active Directory Users and Computers to create a service account. The service account should have local admin rights on SQL Server. Click Next.
- Under Database Engine Configuration, you have an option to go total windows authentication or Mixed Mode. For lab accounts, I prefer to use Mixed Mode, but you can choose the one that is convenient to you. Click Next.
- The Ready to install screen will show the summary of features and configurations. Its always a good idea to review it. Click Install.
- Once the installation is completed successfully, you would see the following screen. Click Close.
- Reboot the server.
- Open SQL Server Management Studio and verify that you are able to connect to your database instance.
SPN registration is mandatory as we are planning to use Kerberos as authentication method for web applications. Please note that you need to register SPN for
- SQL Server Name
- SQL Server Name (FQDN):
- SQL Server Name Instance:Port
- SQL Server Name (FQDN) Instance:Port
The following figure illustrates SPN registration for MS SQL Server service account.
Once this step has completed, it is imperative to configure firewall for accepting requests to SQL Server based on your existing firewall configurations. The SQL Server is ready for hosting database server for SharePoint 2016.
This article showed you steps to build and configure MS SQL Server 2014 SP1. In the next article of the series, we will install SharePoint Server 2016. Till then, keep watching this space.