Welcome to one of the thousands of articles on
SQL Server installation. In this article, I will explain the installation of
SQL Server 2017 and I will discuss a few trick points.
The first thing you need to know is that
SQL Server 2017 is separated from the Management Studio and SQL Server. When you install SQL Server,
SSMS (SQL Server Management Studio) does not come with this nice feature, because when SSMS bug comes out, it is not necessary to update it with SQL server. We’re moving quickly to setup.
From the Installation section, we start by saying New SQL Server Stand Alone.
Here we select Version Evaluation and continue. For those who do not know;
Evaluation: 180-day trial
Developer: A license for developers. Runs all Enterprise functions.
Express: Free version and basic configuration are ideal for end-users in general. Supports up to 10 GB in database size
We accept the terms of the license and proceed with saying next.
After a short check, it is automatically next and continues to install.
Update We accept the terms and click next.
After a short scan, we come to the feature selection screen. As you can see here, Windows Firewall warns about.
The corresponding ports are not open in warnings. You can disable Windows Firewall or define the required accesses and press next.
The Feature Select screen appears. I don’t understand why in most articles I still do this.
This means that after you install the W2K12, it’s like choosing not only AD or IIS but choosing all features.
DO NOT INSTALL THAT YOU DO NOT NEED. INSTALL WHEN YOU NEED.
You can find all of them in this LINK. I’m gonna set up what I’ve marked.
If you keep changing the instance name, you can change it doesn’t pose a problem and click on next.
The key point is that if you are in a domain environment, you need to create and define a user for SQL Server Agent.
The area I mark with yellow is an important but ignored option. With Server 2016, the feature added here provides an excellent performance advantage in data processing between SQL and Server (Database creation, Adding Data Files, Increasing Size, Restoring a Deleted Database). Call next.
Here we select Mixed mode and specify the password for the system administrator and add the Administrator user.
Then we move on to the other tab.
In this tab, we select the location where the Database files will be hosted.
I count the details that are important here;
- The allocation unit sizes of the disks you select must be 64K.
- Database and Log Must be on separate disks
- The first and second details should not be omitted.
If we applied these details carefully, we go to the other tab.
Here are our settings for Temp DB. We start the details,
- It may make sense to make File Count as your Core number (if less than 8)
- It is useful to have the same size as the Temp Files you create. All can be 1 GB
- Save the Temp Files in a separate location from normal DB and Log, as we have separated from the previous tab.
I made my settings like in the picture (don’t look at the directors) 4 temp DB total 4 GB space, 8 GB growth space and 2 GB Log space.
And we call it NEXT.
Finally, the Install option comes up and starts the installation.
As mentioned at the beginning of the article, SSMS and SQL Database were separated from each other. In order to install SSMS, we click on the same place from the same setup.
This gives you the link below downloads and install. The installation of this is much simpler, you’ll continue to click next.
I hope it has been a useful article.