4.0.0 HP PolyServe Software for Microsoft SQL Server Administration Guide (T5392-96056, March 2010)

http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-
508D977D32A6
• Windows Installer 4.5:
http://www.microsoft.com/downloadS/details.aspx?familyid=5A58B56F-60B6-4412-95B9-
54D056D6F9F4
• Windows Powershell:
http://www.microsoft.com/windowsserver2003/technologies/management/powershell/de-
fault.mspx
Installation considerations for SSAS 2008 instances
SSAS 2008 instances are installed through the SQL Server 2008 instance installation procedure (see
“Install SQL Server 2008 instances” on page 19). When you create a template for the installation,
select Analysis Services on the Template Features Wizard screen. The SSAS instance will then be
installed. SSAS instances can be installed as part of a SQL Server instance installation, or you can
install just the SSAS instance.
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 HP PolyServe algorithm. HP recommends that you use filesystem permissions to restrict
access to template files.
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.
SQL Server 2005 SP2 required for Full Text Search
SQL Server 2005 SP2 is required if you will be using FTE. SP2 provides the NTLM Security Support
Provider (NTLMSSP) service, which is used by FTE. Because Windows Server 2008 does not include
the NTLMSSP service, FTE will fail if SP2 is not installed.
Virtual MSDTC
SQL Server instances cannot be installed on nodes configured for Virtual MSDTC. The installation will
fail on these nodes.
“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 should be 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.
HP PolyServe Software for Microsoft SQL Server administration guide 17