Vous êtes sur la page 1sur 25

Module 3

Installing and
Configuring SQL Server
2012
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: Using 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 2012 Edition Maximum Memory
Enterprise Operating system max
Business Intelligence 64GB
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


Software Requirements
Operating Systems
Operating system (General Summary)
Windows Server 2008 R2 SP1
Windows Server Core 2008 R2 SP1
Windows Server 2008 SP2
Windows 7 SP1
Windows Vista SP2
Avoid installation on domain controllers
Prefer 64 bit SQL on 64 bit OS but WOW is supported
Software Requirements General
.NET Framework
.NET Framework 4.0 is required
Some components require .NET Framework 3.5 SP1 also
PowerShell 2.0
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
Determining File Placement
File Type Consideration

Primary and
If you have tables that are frequently used together, you
secondary data
should put them on separate filegroups and physical drives
files

Create the transaction log on a physically separate disk or


Transaction Logs
RAID array

Place the tempdb database on a fast disk drive subsystem


tempdb
to ensure good performance

Disk Planning and File Placement


The most important considerations are the number of disks or spindles available
to a particular volume 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
A collation encodes the rules governing the proper use of characters for
a language such as Greek, or an alphabet, such as Latin1_General

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
Demonstration 1A: Using
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: Using System
Configuration Checker
Overview of the Installation Process
Component Update

SQL Setup MSI


System Configuration Checker

Feature Selection

Server Configuration

Install
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\110\Setup Bootstrap\Log
Detail, summary, and additional logs created as needed at
each phase:
Global rules text
Component update
User-requested action
Demonstration 2A: Using 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
SQL Server Servicing
Unattended Installation
Demonstration 3A: Creating an 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 some SQL Server versions have additional


considerations:
Shared components are upgraded to the latest version if the major build of
the two installations is the same (i.e.: 2008 and 2008 R2)
SQL Server Servicing
SQL Server can be configured to receive automatic updates
directly from Microsoft Update
Caution needs to exerted on this for large production environments
SQL Server feedback should be recorded at
http://connect.microsoft.com
Bug notifications
Suggestions for improvements
SQL Server updates are released in several ways
Hotfixes
Cumulative Updates
Service Packs
Unattended Installation
Can install SQL Server from the command line
Setup.exe /q /ACTION=CompleteImage /INSTANCENAME=MYNEWINST /INSTANCEID=<MYINST>
/SQLSVCACCOUNT="<DomainName\
/SQLSVCACCOUNT="<DomainName\UserName>" /SQLSVCPASSWORD="<StrongPassword>"
/SQLSYSADMINACCOUNTS="<DomainName\
/SQLSYSADMINACCOUNTS="<DomainName\UserName>" /AGTSVCACCOUNT="NT AUTHORITY\
AUTHORITY\Network
Service" /IACCEPTSQLSERVERLICENSETERMS

Can also upgrade SQL Server from the command line


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\
Authority\Network Service"
/IACCEPTSQLSERVERLICENSETERMS
Demonstration 3A: Creating an
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
Virtual machine 10775A-MIA-SQL1

User name AdventureWorks\Administrator


Password Pa$$w0rd

Estimated time: 45 minutes


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