SQL Installation Process

Uploaded by

carlos zoro

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

12 views

SQL Installation Process

Uploaded by

carlos zoro

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 14

Sql Server Installation Options

Introduction

The purpose of this document is to report the steps to follow during the installation process of Microsoft Sql Server.
Features
The following features have to be enabled:
- Instance features:
o Database engine services
 Full-Text and Semantic Extraction … (ONLY IF USED SYSTORE HELP DATABASE)
- Shared features
o Client tools connectivity
o Integration services
o Client tools backward compatibility
o Client tools SDK
o Documentation Components
o Management tools – Basic
 Management Tools – Complete
o Sql Client Connectivity SDK

Instance configuration
It’s possible to keep default instance or if, for any reasons, it’s required a specific name (i.e. two Sql Server engine
involved) is possible to change it.
Server Configuration

Service Accounts
The Sql Server services have to be setup with the following accounts:
- Sql Server Agent: NT AUTHORITY\NETWORK SERVICE, automatic startup
- Sql Server Database Engine: “Domain Account” (see below), automatic startup
- Sql Server Browser: NT AUTHORITY\LOCAL SERVICE, automatic startup
During the commissioning phase we will setup some scheduled task, executed by Sql Server Agent, that make
maintenance activities on the database. A couple of these jobs make the backup of the database and of the
transaction log and copy them to a “safe” location on the customer network.
For this reason System Logistics needs:
- a shared folder, accessible from the database server virtual machine, where Sql will put the backups
- a domain user with the read/write permissions on this network folder. This user as to be setup as the account
associated to the Sql Server Database Engine service.

An important notice: typically the domain accounts have a limited number of days for the validity of the password. It’s
recommended to setup that the account associated to the Sql Server engine has no password expiration, otherwise it’s
highly likely that, after the password expires, in case of a restart of the engine, Sql Server doesn’t start causing many
problems.

Collation
“Latin1_General_CI_AS” suggested collation, depending on the country.
(“Case Insensitive“, Accent Sensitive”).

Database Engine Configuration

The following options have to be provided:
- Server configuration:
o Both options are admitted
 Windows authentication mode, defining in a second step the rule for the “sa” super user
 Mixed authentication mode, with a complex password for the “sa” super user (policy)
o one account as Sql Server administrator (typically the one used for the database engine account)
- Data directories: no specific requirements needed
- FILESTREAM: leave this option unchecked

Database Engine Configuration for “Windows authentication mode”

Connect to Sql Server using the “Windows Authentication
Enter in the “Properties” of the engine

In the “Security” menu:

- Set “Sql Server and Windows Authentication mode” in “Server authentication” menu
Enter in the “Properties” of the “sa” user
In the “General” menu:
- Set the password “SYSTEM”
- Uncheck the option “Enforce password policy”
In the Status menu:
- Set “Enabled” in “Login:” part
Restart Sql Server service
Reconnect using “Sql Server Authentication”