Module 3

Installing and Configuring SQL Server

2008 R2

Module Overview

• Preparing to Install SQL Server

• Installing SQL Server

• Upgrading and Automating Installation

Lesson 1: Preparing to Install SQL Server

• Hardware Requirements – General

• Hardware Requirements - Memory

• Software Requirements – Operating Systems

• Software Requirements - General

• Determining File Placement

• Service Account Requirements

• Working with Collations

• Demonstration 1A: Collations

Hardware Requirements - General

• Processors Almost any processor is now fast enough

Number of processors needs to be considered

• Disk Disk space requirements for SQL Server are trivial compared to

current drive sizes

User database size is a determining factor

Disk I/O performance is critical to SQL Server performance

• Virtualization SQL Server virtualization is now very common

Hardware Requirements - Memory

SQL Server 2008 R2 Edition Maximum Memory

Datacenter Operating system max

Enterprise Operating system max up to 2TB

Standard 64GB

Workgroup 4GB

Web 64GB for Database Engine, 4GB for Reporting Services

Express 1GB

Express with Advanced Services 1GB for Database Engine,4GB for Reporting Services

• 32 bit servers have limited "visible" address space

• AWE memory can only be used for data page caching

Software Requirements – Operating Systems

• Operating system (General Summary) Windows Server 2008 R2

Windows Server 2008 SP2

Windows Server 2003 R2

Windows Server 2003 SP2

Windows 7

Windows Vista SP2

Windows XP SP3

• Avoid installation on domain controllers

• Prefer 64 bit SQL on 64 bit OS but WOW is supported

Software Requirements – General• .NET Framework

.NET Framework 2.0 SP2 for SQL Server 2008 R2 on Windows Server 2003 R2 64bit Itanium and SQL Server Express

.NET Framework 3.5 SP1 for all other editions

• SQL Server Native Client

• SQL Server Setup support files

• Windows Installer 4.5 or later

• Internet Explorer 6 SP1 or later

• Network software Shared memory

Named pipes

TCP/IP

VIA (deprecated)

Determining File Placement

File Type Consideration

Primary and secondary data files

• If you have tables that are frequently used together, you should put them on separate filegroups and physical drives

tempdb • Place the tempdb database on a fast disk drive

subsystem to ensure good performance

Transaction Logs • Create the transaction log on a physically separate disk or RAID array

Disk Planning and File Placement

The most important considerations are the number of disks

or spindles available to a particular drive and the speed of

the drives involved

Service Account Requirements• Carefully consider service account requirements

Create service accounts that have least privileges Generally choose domain accounts Local Service account might be appropriate in some

environments

• If accounts are set using SQL Server setup, minimal permissions will be configured automatically

• Each service account has different permission requirements Consult BOL for details of specific permissions for each

account Use a different account for each service

Working with Collations

• Windows Collations

• Based on the rules for the associated Windows locale

• SQL Server Collations

• Matches the code page number and sort order that may have been specified in earlier versions of SQL Server

• Default Collation and Sort Rules

• Default collation applies if you do not designate collation and sort rules

A collation encodes the rules governing the proper use of characters for a language such as Greek, or an alphabet, such as Latin1_General.

A collation encodes the rules governing the proper use of characters for a language such as Greek, or an alphabet, such as Latin1_General.

Demonstration 1A: Collations

• In this demonstration, you will see how collations affect T-SQL queries.

Lesson 2: Installing SQL Server

• Overview of the Installation Process

• System Configuration Checker

• Post-installation Checks

• Demonstration 2A: System Configuration Checker

Overview of the Installation Process

SQL Setup MSI

Component Update

Feature SelectionFeature Selection

System Configuration CheckerSystem Configuration Checker

InstallInstall

Server ConfigurationServer Configuration

System Configuration Checker

Checks Installation Requirements:

Software Requirementsüü

Hardware Requirementsüü

Security Requirements üü

System State Requirementsüü

Post-installation Checks

• Verify that installed SQL Server services are running SQL Server Configuration Manager is a good place to do this

• If errors occur during setup, log files are helpful Every setup creates a new timestamped log folder

Location is:

%programfiles%\Microsoft SQL Server\100\Setup Bootstrap\Log

• Detail, summary, and additional logs created as needed at each phase: Global rules text

Component update

User-requested action

Demonstration 2A: System Configuration Checker

• In this demonstration you will see how to run the first phase of SQL Server installation, the System Configuration Checker. You will see the rules that the SCC implements.

Lesson 3: Upgrading and Automating Installation

• Upgrading SQL Server

• Unattended Installation

• Demonstration 3A: Unattended Installation File

Upgrading SQL Server

In-place Upgrade Side-by-side Upgrade

• Easier, mostly automated • More granular control over process

• System data upgraded • Can be used to perform test migration

• No additional hardware • Relatively straightforward rollback

• Apps pointing to same names • Can leverage failover/switchover

• Side-by-side installs of SQL Server 2008 R2 and SQL Server 2008 have additional considerations: Same major version number Shared components are upgraded to the latest version

(they do not co-exist) Setup support files can work with either version. (You

can later change installed SQL Server 2008 components).

Unattended Installation• Can install SQL Server from the command line

• Can also upgrade SQL Server from the command line

Setup.exe /q /ACTION=CompleteImage /INSTANCENAME=MYNEWINST /INSTANCEID=<MYINST> /SQLSVCACCOUNT="<DomainName\UserName>" /SQLSVCPASSWORD="<StrongPassword>" /SQLSYSADMINACCOUNTS="<DomainName\UserName>" /AGTSVCACCOUNT="NT AUTHORITY\Network Service" /IACCEPTSQLSERVERLICENSETERMS

Setup.exe /q /ACTION=CompleteImage /INSTANCENAME=MYNEWINST /INSTANCEID=<MYINST> /SQLSVCACCOUNT="<DomainName\UserName>" /SQLSVCPASSWORD="<StrongPassword>" /SQLSYSADMINACCOUNTS="<DomainName\UserName>" /AGTSVCACCOUNT="NT AUTHORITY\Network Service" /IACCEPTSQLSERVERLICENSETERMS

Setup.exe /q /ACTION=upgrade /INSTANCENAME=MSSQLSERVER /RSUPGRADEDATABASEACCOUNT="<Provide a SQL Server logon account that can connect to the report server during upgrade>" /RSUPGRADEPASSWORD="<Provide a password for the report server upgrade account>" /ISSVCAccount="NT Authority\Network Service" /IACCEPTSQLSERVERLICENSETERMS

Setup.exe /q /ACTION=upgrade /INSTANCENAME=MSSQLSERVER /RSUPGRADEDATABASEACCOUNT="<Provide a SQL Server logon account that can connect to the report server during upgrade>" /RSUPGRADEPASSWORD="<Provide a password for the report server upgrade account>" /ISSVCAccount="NT Authority\Network Service" /IACCEPTSQLSERVERLICENSETERMS

Demonstration 3A: Unattended Installation File

• In this demonstration, you will see an unattended installation file that could be used to configure SQL Server

Lab 3: Installing and Configuring SQL Server

• Exercise 1: Review installation requirements

• Exercise 2: Install the SQL Server instance

• Exercise 3: Perform Post-installation Setup and Checks

• Challenge Exercise 4: Configure Server Memory (Only if time permits)

Logon information

Estimated time: 45 minutes

Virtual machine 623XB-MIA-SQL

User name AdventureWorks\Administrator

Password Pa$$w0rd

Lab Scenario

The development group within the company has ordered a new server for the work they need to do on the Proseware system. Unfortunately, the new server will not arrive for a few weeks and the development group cannot wait that long to start work.

The new server that was provisioned by the IT Support department already has two instances of SQL Server installed. The support team have determined that the new server will be able to support an additional instance of SQL Server on a temporary basis, until the server for the development group arrives.

You need to install the new instance of SQL Server and if you have time, you should configure the memory of all three instances to balance their memory demands, and you should create a new alias for the instance that you install.

Lab Review

• When the DEV instance is no longer required, what actions would be needed when removing it from the server?

• What does CI indicate as part of the name of a collation?

Module Review and Takeaways

• Review Questions

• Best Practices