Module 2: Planning to

Install SQL Server

Overview

 Hardware Installation Considerations

 SQL Server 2000 Editions
 Software Installation Considerations
 Methods of Installing SQL Server
 Upgrading SQL Server
 Verifying the Installation
 Configuring SQL Server Enterprise Manager
 Troubleshooting
Hardware Installation Considerations

 Minimum Hardware Requirements

 Optimize Hardware for SQL Server
 Minimum Hardware Requirements

Component
Component Minimum
Minimumrequirements
requirements
Processor
Processor
Intel
Inteland
andcompatible
compatiblesystems
systems(166-MHz
(166-MHzPentium
Pentiumororhigher)
higher)

Memory
Memory Minimum
Minimum256
256MB
MB(All
(Allserver
serverversions
versionsofofWindows
Windows2000)
2000)
Minimum
Minimum 64 MB (All server versions of Windows NT4.0)
64 MB (All server versions of Windows NT 4.0)
Hard
Harddisk
diskspace
space 250
250MB
MB(typical
(typicalinstallation)
installation) 100
100MB
MB(client
(clienttools)
tools)
270
270MB
MB(full
(fullinstallation)
installation) 50 50-130
-130MB
MB(Analysis
(AnalysisServices)
Services)
MB
80
80MB
MB(English
(EnglishQuery)
Query)
Optimize Hardware for SQL Server

 Processor
 Scale up
 Scale out
 Disk Subsystem
 RAID levels
 Memory
 Read from disk or memory cache
 Network
 Impact throughput and performance of SQL Server
SQL Server 2000 Editions

 Comparing Standard and Enterprise Editions

 Standard Edition supports many SQL Server 2000
features
 Enterprise Edition contains all features required to
support an enterprise-wide environment
 Installing Other SQL Server 2000 Editions
 Selecting the Appropriate Operating System
Software Installation Considerations

 Licensing
 Determining the Security Context of the Services
Accounts
 Using Named and Multiple-Instances of SQL Server
 Selecting a Security Mechanism
 Selecting SQL Server Collations and Sort Rules
 Selecting Network Libraries
Licensing

 Per Processor Licensing

 Acquire a license for each processor running
SQL Server 2000
 Allows an unlimited number of users to connect from a
LAN or WAN
 Per Seat Licensing
 Acquire a server license for each SQL Server and a CAL
for each workstation that connects to any instance of
SQL Server
Determining the Security Context of the Services
Accounts
 Default SQL Server Services Logon Account
 An instance of SQL Server service
 An instance of SQL Server Agent service
 Using a Domain User Logon Account
 Uses Windows 2000 trusted connections
 Using the Local System Logon Account
 Cannot communicate with remote servers that use Windows 2000
trusted connections
 Autostart Services
 Run automatically when Windows 2000 services are started
Using Named and Multiple Instances of SQL Server

 Default Instance
 Is identified by the network name on which it is running
 Only one default instance is permitted
 Named Instance
 Is identified by the network name plus an instance name
 Applications must use SQL Server 2000 client components to
connect to a named instance
 Multiple Instances
 Default instance and one or more named instances
 Each instance operates independently on the same computer
Selecting a Security Mechanism

 Selecting Windows Authentication Mode

 User must have valid Windows 2000 or Windows NT
user account
 User must receive validation by the operating system
 Selecting Mixed Mode
 User can use Windows Authentication
 User can use SQL Server Authentication
Selecting SQL Server Collations and Sort Rules

 Groups of Collations
 Windows collation is based on the rules for an
associated Windows locale
 SQL collation matches attributes of code page number
and sort order specified in earlier versions of SQL Server
 Default Collation and Sort Rules
 SQL Server applies the default if you do not designate a
collation and sort rules
 Avoid changing the default collation and sort rules
Selecting Network Libraries

 Default Network Libraries

 Named Pipes and TCP/IP Sockets are the default for server network
libraries for an instance of SQL Server
 TCP/IP sockets client network library for all management tools
 Named Pipes as a second client network library on all versions of
Windows NT 4.0 and Windows 2000
 Server Network Libraries That SQL Server Supports
 TCP/IP sockets  VIA GigaNet SAN
 Named pipes  Multiprotocol
 NWLink IPX/SPX  AppleTalk ADSP
 VIA ServerNet II SAN  Banyan VINES
Methods of Installing SQL Server

 Standard Installation
 Unattended Installation
 Remote Installation
Standard Installation

 The Default Installation Type Is Typical

 Types of SQL Server Installation
 Minimum installation—installs a minimum server
configuration
 Typical installation—presents a limited selection
of server configuration options
 Custom installation—presents all components
and server configuration options
Unattended Installation

 Performing an Unattended Installation

 Command and Setup Initialization Files
 Creating a Custom Setup Initialization File
 Use a text editor
 Run SQL Server Setup
Remote Installation

 How SQL Server Performs a Remote Installation

 Saves information into a Setup.iss file
 Starts the remote setup process: starts remote service,
copies files, and runs an unattended installation
 Requirements for Remote Installation
 User account must be an administrator on the remote
computer
 User account must have read access to the Setup
source files folder
Upgrading SQL Server

 Upgrading from Version 7.0

 Install a default instance (upgrades existing installation)
 Install a new named instance (retains existing
installation)
 Upgrading from Version 6.5
 Install a default or named instance (both create new
instances)
 Use version switching to switch between versions
 Upgrading from Version 6.0
 First upgrade to version 6.5 or 7.0
Verifying the Installation

 Reviewing Installation Results

 Starting, Stopping, and Pausing SQL Server Services
 Connecting to SQL Server
Reviewing Installation Results

 SQL Server Services

 Management Tools
 Databases
 Directories and Files
 Default Startup Options
 Default Security Mode
Starting, Stopping, and Pausing the SQL Server
Services

 Automatically Starting the SQL Server Service

 Manually Starting, Pausing, and Stopping a Service
 Default instance: net start mssqlserver,
net pause mssqlserver, or net stop sqlserveragent
 Named instance: net start mssql$instancename
Connecting to SQL Server

 Using a Graphical Tool

 SQL Query Analyzer
 SQL Server Enterprise Manager
 Using the osql Command Prompt Utility
 Communicates by using ODBC
Configuring SQL Server Enterprise Manager

 Registering Servers
 Registration Information
 Registering Multiple Named Instances and Servers
 Administering SQL Server
 Creating server groups
 Accessing Registration Information
 Registration information is private by default
 Sharing registry information
Troubleshooting

 Identifying the Problem

 Review error messages
 Review the Sqlstp.log file
 View log information
 Test network connections
 Finding Solutions to Common Problems
Recommended Practices

Use
Use aa Write-caching
Write-caching Controller
Controller That
That Is
Is Designed
Designed for
for Database
Database Use
Use

Use
Use the
the Same
Same Collation
Collation and
and Sort
Sort Rules
Rules Within
Within Your
Your Organization
Organization

Use
Use aa Dedicated
Dedicated Domain
Domain User
User Logon
Logon Account
Account

Register
Register All
All Instances
Instances of
of SQL
SQL Server
Server That
That You
You Manage
Manage with
with
SQL
SQL Server
Server Enterprise
Enterprise Manager
Manager

Assign
Assign aa Password
Password to
to the
the SQL
SQL Server
Server sa
sa Login
Login Account
Account
Lab A: Installing SQL Server
Review

 Hardware Installation Considerations

 SQL Server 2000 Editions
 Software Installation Considerations
 Methods of Installing SQL Server
 Upgrading SQL Server
 Verifying the Installation
 Configuring SQL Server Enterprise Manager
 Troubleshooting