3.6.0 MxDB for SQL Server Installation and Administration Guide (5697-7088, December 2007)

Chapter 3: Install SQL Server Instances 11

Installation Considerations for SQL Server 2005

Template File

The Multi-Node Installer creates an INI template file that is used in the

installation. This file should be saved in a location that provides read

access for all nodes. The installer encrypts passwords in the file using a

PolyServe algorithm. Do not change this file.

IP Network Configuration

The SQL Server 2005 instance installation captures and stores the current

IP network configuration of the node on which it is installed. If you later

need to change the network configuration (for example, to remove a NIC

or change its IP), it is necessary to devirtualize the Virtual SQL Servers on

the affected node, make the needed changes, and then revirtualize the

Virtual SQL Servers.

“Instance-Aware” and “Non-Instance-Aware” Components

The SQL Server 2005 package includes both “Instance-Aware” and

“Non-Instance-Aware” components. The Instance-Aware components are

installed and managed by reference to the name of the instance (or simply

the server name if the Default instance is used). The Non-Instance-Aware

components are installed once per server and shared by all instances

active on that server.

The Instance-Aware components are:

• Database Engine. The “Default” or named instance itself.

• Full Text Search Engine. A child instance-aware service installed only

if the Database Engine is installed on the node.

• Analysis Services. A separate service that does online data analysis for

data mining and reporting.

• Reporting Services. The server and client components required to do

reporting and data presentation development.

• Server Agent. The service that handles the management and

maintenance jobs for the instance.