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

“Instance-Aware” and “Non-Instance-Aware” components
The SQL Server 2008 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.
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 present-
ation development.
• Server Agent. The service that handles the management and maintenance jobs for the instance.
We recommend that you install the Non-Instance-Aware components only once per server. Any future
install templates should not include these components. After each installation, check the logs for
information such as whether a reboot is necessary.
The following Books On Line (BOL) article provides a summary of the issues associated with installing
multiple instances on a single node:
http://msdn2.microsoft.com/en-us/library/ms143531.aspx
The next article lists the default file locations for all components of a SQL Server instance and explains
concepts for the installed instances of the Database Engine, Analysis Services, and Reporting Services.
As you review this article, note that moving the installed data file directories for the configurable
components has not been tested with HP PolyServe Software; however, as long as the configuration
is identical for an instance across all nodes, it should be functional.
http://msdn2.microsoft.com/en-us/library/ms143547.aspx
The following article contains tables listing the directory structure and configurable components:
http://msdn2.microsoft.com/en-us/library/ms144275.aspx
The following article discusses installing components. Be sure to review the footnotes for the table.
Also note that installing both 32-bit and 64-bit Reporting Services on a node running a 64-bit operating
system is not supported by Microsoft or HP PolyServe Software.
http://msdn2.microsoft.com/en-us/library/ms143786.aspx
Instance ID
SQL Server 2008 provides an “Instance ID” that is used to identify installation directories and registry
keys for a particular instance. By default, the instance ID is the same as the instance name. You can
specify a different ID if desired when you install an instance.
File streaming implications
Although the SQL Filestream can be enabled during an installation of SQL 2008, the actual BLOB
cannot be put on an HP PolyServe clustered filesystem (PSFS).
HP PolyServe Software for Microsoft SQL Server administration guide 15