From this state of SQL Setup onward, you will go through the SQL Features and Parameters selection till the Setup complete. The first screen prompts you for the selection of SQL Setup. Select SQL Server Features Installation and press [Next] to proceed.


The SQL Setup prompts you the SQL individual feature selection. You can use this screen to add and remove any of the SQL features after the installation. For this installation guide, we select all features. The 2 Shared Features directories show the location of the SQL Setup files. One for the 32-bits Setup Files, and one for the 64-bits Setup File. You can change the directories to your Application Disk. For this installation guide, I leave it as the default directories.


SQL Setup will go through the third round of Check on the installation rules. The table below shows the Checks and Requirements.

RulesCheck and Requirement
Prior Visual 2010 instances requiring updatesThis rule determines whether the computer has any prior installations of Visual Studio 2010 that might require Service Pack 1 update.
SQL Server Analysis Services Server Mode and Edition CheckChecks whether the SQL Server edition supports the currently selected Analysis Services server mode.
Microsoft .NET Framework 3.5 is installed on Windows or higherIf you are installing SQL Server on Windows 8 or higher version of Windows, Microsoft .NET Framework 3.5 might not be installed by default. In order to ensure successful installation of all SQL Server features that requires Microsoft .NET Framework 3.5, confirm that Microsoft .NET Framework 3.5 is installed or enabled prior to running the SQL Server setup. If Microsoft .NET Framework 3.5 is not installed or enabled prior to the SQL Server setup, Windows will attempt to install Microsoft .NET Framework 3.5 during the SQL Server installation process. Incomplete installation of SQL Server may result if Windows is not able to successfully access and install Microsoft .NET Framework 3.5.

If there any Rules that failed the Check, resolve the issue and re-scan again. All Rules must be passed before proceeding with the installation.


The SQL Instance Configuration lets you change the SQL Instance Name install on the server. You might consider changing the default name “MSSQLSERVER” for security reasons, or you might have multiple SQL Instances going to be created on the same SQL Server. The SQL Instance Name is the ID for your SQL Database connection. You can use different SQL Instance name to represent your Application Database. This SQL Instance Name is listing in Windows Services.


On the next Setup, the disk space requirement summaries the disk storage required to complete the installation. This is the directory you selected for the SQL Setup Files to store.


From the Server Configuration screen, you can specify the Windows Account to start the SQL Services and change the Startup Type. If you are installing your SQL Server on a domain network, highly recommend you to use a domain account as the Service Account for better cross-server communication and authentication.


Under the SQL Setup Collation, you can change the Database Collation. For this Setup, clicks on [Next] to accept the default settings. You can change the collation after the Setup.


For the authentication mode, you can select either the purely Windows Authentication Mode or the Mixed Mode. If you select the Mixed Mode, you will enter the SQL SA account password. Some applications required SQL Mixed Mode authentication. Please check your application’s requirements. For either of the selections, clicks [Add Current User] button to delegate local Administrator account with SQL Server Administrator rights. You also can add additional User Accounts by clicking the [Add] button.


Under the Data Directories tab, you can specify the directories to store the SQL Database files and Database Transactions Log file. Usually, this directory will be your dedicated storage with enough spaces for database and transactions log to grow. It is not advisable to store your database files and transactions log file at the same partition with your Windows operation system installed. It will affect the System I/O performance. Allocate a dedicated partition for database data files and the transaction log file. Monitoring the disk space growth if you have limited storage space. Perform regular database maintenance to reduce the file size.


For the FILESTREAM tab, we leave the default and clicks [Next] to proceed.

The Analysis Services is an Online Analytical Processing tool for SQL Data Warehousing and Business Intelligence services. We leave the default setting for now and delegate the local Administrator account with the Analysis Services administrator’s right for future configuration.


For SQL Online Reporting Services, we leave it with the default settings and clicks [Next] to proceed. We can always configure the services after the Setup.


The SQL Server 2012 Distributed Replay feature helps you assess the impact of future SQL upgrades. It functions with Distributed Replay Controller and Distributed Replay Client. There will be only one Distributed Replay Controller in each environment. For performance consideration, it’s not recommended to install the Controller on the same server with the Database Instances. For this installation guide, we just accept the default setting to install the Controller on the local server and grant the local Administrator account with unlimited access right to the Controller. You can always select a dedicated domain account to run this service.


For the Distributed Replay Client, specify the location of the Controller installed. In this scenario, we install both Controller and Client on the same Server. Clicks [Next] to proceed.


On the Error Reporting, if you agree to send error reports to Microsoft or a reporting server, check the box. Clicks [Next] to proceed.


The SQL Server Setup will come to the final Check to confirm all the Supporting Files and requirements are met before the installation starts. The table below lists out the Check Rules and Requirement.

RulesCheck and Requirement
FAT21 File SystemChecks whether the specified drive is FAT32 file system volume. Installing on a FAT32 file system is supported but not recommended as it is less secure than the NTFS file system.
Existing clustered or cluster-prepared instanceChecks if the selected instance name is already used by an existing cluster-prepared or clustered instance on any cluster node.
Cross-language installationChecks whether the Setup language is the same as the language of existing SQL Server features.
Same architecture installationChecks whether the installing feature(s) are the same CPU architecture as the specified instance.
Reporting Services Catalog Database File ExistenceChecks whether the Reporting Services catalog database file exists.
Reporting Services Catalog Temporary Database File ExistenceChecks whether the Reporting Services catalog temporary database file exists.
SQL Server Analysis Services Server Mode and Edition CheckChecks whether the SQL Server edition supports the currently selected Analysis Services server mode.

If there any Rules that failed the Check, resolve the issue and re-scan again. All Rules must be passed before proceeding the installation.


The next screen summarized the features selected for the SQL Setup. Review all the settings. If there any changes to make, click on the [Back] button to correct it. If nothing to change, click [Install] button to begin the installation.


The installation copies all the System Files and configures the SQL Server Services. This process will take an hour to complete. It depends on the total features selected and the Server capacity.


After the installation completed, review the installation summary to any Features that failed to install. Clicks on [Close] to complete the installation.


Post Installation Checks

After the SQL Setup completed, you can perform some simple Checks to confirm the SQL Server is installed successfully. The following are some of the steps that you can perform.

Check the SQL Server Services

Launch Windows Services. The SQL Server Instance (MSSQLSERVER for this installation guide) is running. Stop and Start the service, it should be able to restart without any error.


Check the Server Windows Logs

Launch the Windows Application Logs viewer. Check on the MSSQLSERVER Source. Review the event logs for any suspicious services.


Check TCP/IP Protocol enable at SQL Server

You can perform this test form within the SQL Server and from a Client machine. Telnet the SQL Server from the Command Prompt – telnet <SQL Server IP Address> <port number>

The default TCP Port for SQL Server is 1433 and the UDP Port is 1434. If the telnet is not able to connect to the SQL Server, check on the Windows Firewall and/or the network firewall setting.