• Adam Thurgar

Installing SQL Server - Part 2 Installation

This is the second part of a series on installing SQL Server.

This is based on an a standalone installation of SQL Server 2017.

This blog focuses on the installation at a high level with focus on what information you need to complete the installation.

You should plan your installation before you start so you know all of this information.

1. Product key

2. MS Updates - do you want these downloaded and installed automatically?

My preference is No, as I like to control when updates get applied to a SQL Server.

3. You will more than likely get a warning for the Windows firewall on the install rules.

4. What features do you want to install? For example, do you need to install:

SSAS, Polybase, R, Python, Distributed Relay, SSIS Scale out, client tools?

5. Instance name - do you use named instances or the default?

6. Changes to the server configuration.

I usually change the SQL Server Agent to automatic start and others to manual if installed, like SSIS Scale out.

I also enable the 'Grant Perform Volume Maintenance Task" privilege.

This is also when you need the information on what accounts the SQL Server services should be running under.

7. Changes to the database engine configuration.

What authentication mode do you use? If mixed then you will need a password for sa.

At this stage,I usually add the current user to SQL Admins.

If you have specific directories for data, logs and backups then you will need to change the settings for the data directories.

You can also configure tempdb files for location, size and autogrowth.

8. Depending on what features you selected to install, you will be asked for configuration setting for some of these features (Distributed Relay controller and client, SSIS Scale out) and for others consent to install (R and Python).

9. Start the install

10. Check for any failures on the install.

4 views0 comments

Recent Posts

See All

Cardinality estimator

Recently I was asked by a software vendor to review a particular query that ran in under a second on a SQL Server 2014 installation at a compatibility level of 110 (SQL Server 2012), but when run unde

Index fragmentation

A law firm client, occasionally has issues with their legal software, that is provided by the global leader in this field. The response from the software provider is always the same - you have index f

Deleting large amounts of data

I had a client call me about wanting to delete a large amount of data from their database. They knew what tables they wanted to delete from. They also knew that deleting large amounts of data causes t