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

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/ms144688.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
Set permissions on existing PSFS filesystems
If you will be installing a SQL 2005 instance on a mountpoint for a PSFS filesystem created under
Matrix Server 3.2 or earlier, the installation may fail if the file permissions are not set appropriately.
You can use any of the following methods to set the permissions if necessary.
• Mount the filesystem as a drive letter (for example, s:\). In Windows Explorer, open the Properties
for the volume and select the Security tab. Then set the permissions to Full Control for Administrat-
ors/users.
• Mount the filesystem as a mountpoint such as c:\psfs\psd15p1. In Windows Explorer, open
the Properties for the folder, go to the “Mounted Volume” properties (this is not the same as the
folder security), and set the permission for Administrators/users to Full Control.
• Use the cacls.exe utility to give the local Administrators group full control and to give Everyone
read-only permissions. In the following command, %1 is the mounted folder.
cacls %1 /t /m /p Administrators:F Everyone:R
For example:
cacls c:\psfs\psd1p1 /t /m /p Administrators:F Everyone:R
Install SQL Server instances18