Few things we need to keep in mind before performing the installation.
SQL Server Reporting Services (SSRS) is no longer part of SQL Server installation setup. We need to install SSRS separately.
The same is true for SQL Management Studio. Starting onwards SQL Server 2016, SQL Management studio is not part of the standard installation, hence we also need to install this separately.
There are more steps to cover while installing SQL Server 2017 unlike previously when standard installation was enough to configure everything.
Installation Prereq As we are going to install SQL Server on SCCM Server (Hostname used here: SCCM01), logon to the server SCCM01. In production, it is better to have 3 different physical disk or atleast 3 different partitions for following. For the sake of SCCM Lab, we are going with 2 partitions
SQL Database (We will be using E Drive)
SQL TempDB (We will be using G Drive)
SQL transaction Logs / SQL TempDB Logs (We will be using G Drive)
Lets start with the Standard SQL Server 2017 setup
Setup can be downloaded from following link: Once mounted (or extracted), launch the setup.exe
On left pane select “Installation”, on right pane click on “New SQL Server stand-alone installation or add features to an existing installation”
Select “evaluation” edition or provide product key if you have it.
Select “I accept the license terms” and click on next.
You can use Microsoft Update to look for latest updates.
This will verify the rules to make sure you are ready to run the installation. Make sure appropriate Windows Firewall ports are opened.
Various Inbound TCP / UDP ports are required to be opened, such as ports 1433, 1434, 4022, 135. If the named instance is the only instance of the Database Engine installed, it will probably use TCP port 1433.
Right Pane will show you the require prerequisites whether they are installed or going to be installed as part of installation. We can see the Microsoft .Net Framework 4.6 is showing as installed as I did it previously or else it would have shown error.
We can use Default Instance or Named Instance, recommended way is to go with Named Instance as we can host multiple instances on same SQL Box. We are going to use “InstanceSCCM” as Named instance.
We need to specify the Service Accounts. Recommended way in production environment is to have service accounts created for “SQL Server Agent” & “SQL Server Database Engine”. For the sake of lab environment, we are going to use SCCM Service Account ie “SVC-SCCMAdmin” which is a member of Domain Admin.
Click on tab “Collation” and make sure “SQL_Latin1_General_CP1_CI_AS” is selected.
Under Tab “Server Configuration”, click on “Add Current User” for SQL Server administration.
Click on tab “Data Directories”, we will see default values as shown below.
Ideally Data root directory, database directory & database log directory should be on a different drive. Click on Tab “TempDB” and specify Data directories
Click on “Install” for actual installation to begin.
We are done with the SQL Server installation. We will now proceed with SQL Management Studio
SQL Management Studio Installation
This can be downloaded from the link The latest version at the time of writing this blog is 17.9 Once downloaded, launch the setup.exe
Once installation is completed, you can launch the “Microsoft SQL Server Management Studio” which will be displayed under “Microsoft SQL Server Tools 17”
We need to specify the Server Name. For Default Instance, we need to just specify Server name only. But we selected Name Instance during installation. Hence we need to select “SCCM01\INSTANCESCCM” Where SCCM01 is Server Name and INSTANCESCCM is Named Instance.