How to install SQL Server 2005 Analysis Services on a failover cluster (910230)



The information in this article applies to:

  • Microsoft SQL Server 2005 Analysis Services

SUMMARY

You can install Microsoft SQL Server 2005 Analysis Services (SSAS) on a failover cluster. When you do this, Microsoft Cluster Service (MSCS) provides superior reliability for SSAS.

This article describes the following topics:
  • How to install SQL Server 2005 Analysis Services on a failover cluster
  • How to verify whether the installation is successful
  • How to remove SQL Server 2005 Analysis Services from a failover cluster
  • Known issues

INTRODUCTION

This article describes how to install SQL Server 2005 Analysis Services on a failover cluster and provides more information about Analysis Services failover clustering.

MORE INFORMATION

You can install SQL Server 2005 Enterprise Edition or SQL Server 2005 Standard Edition to support failover clustering. The following table compares the two different editions when you install Analysis Services on a failover cluster.
Edition of SQL Server 2005Supported nodesSupported instances of SQL Server 2005 Analysis Services
SQL Server 2005 Enterprise EditionSQL Server 2005 Enterprise Edition supports many nodes as the underlying operating system supports.

For example, if you install SQL Server 2005 Enterprise Edition on a failover cluster that is running Microsoft Windows Server 2003, you can add 8 nodes to the cluster.
50
SQL Server 2005 Standard Edition216
Note All the SQL Server 64-bit editions support failover clustering. When you install a SQL Server 2005 x64 edition, both failover clustering and management tools are supported. When you install a SQL Server 2005 edition for Itanium-based systems, management tools are not supported.

How to install Analysis Services on a failover cluster

You can install Analysis Services with or without SQL Server 2005 on a failover cluster. To install Analysis Services on a failover cluster, follow those steps:
  1. Insert the Microsoft SQL Server 2005 DVD in the DVD drive. If the SQL Server Installation Wizard does not start automatically, double-click the Splash.hta file in the root folder of the DVD.

    If you are installing SQL Server from a network location, share the installation files and then connect to the location from the computer on which you want to install SQL Server.
  2. To start the installation process, click Server components, tools, Books Online, and samples.
  3. On the End User License Agreement page, read the license agreement, click to select the check box to accept the license terms and conditions, and then click Next.
  4. SQL Server Component Update runs and installs the software that is required before you install SQL Server. When SQL Server Component Update is finished, click Finish.
  5. On the Welcome page of the SQL Server Installation Wizard, click Next.
  6. On the System Configuration Check (SCC) page, the installation computer is scanned for conditions that may block setup. To interrupt the scan, click Stop. After the scan is completed, click Continue.

    Note If the scan reports any errors, identify the error, and then click Exit. You cannot complete the installation until all blocking errors are resolved.

    For more information, visit the following Microsoft Developer Network (MSDN) Web sites:

    System Configuration Check (SCC)
    http://msdn2.microsoft.com/en-us/library/ms143185.aspx

    Check parameters for the System Configuration Checker
    http://msdn2.microsoft.com/en-us/library/ms143753.aspx

    On the Microsoft SQL Server Installation page, the SQL Server Installation Wizard prepares to install the software. The Installation Wizard proceeds when the preparation is completed.
  7. On the Registration Information page, type information in the Name and Company boxes, and then click Next.
  8. On the Components to Install page, click to select the Analysis Services check box and the Create an Analysis Server failover cluster check box to install Analysis Services on a failover cluster, and then click Next.

    Notes
    • You can click to select any combination of check boxes. When you click to select the SQL Server Database Services check box or the Analysis Services check box, if the Setup program detects that you are installing to a cluster node, the Create a SQL Server failover cluster check box or the Create an Analysis Server failover cluster check box is selected.
    • You can choose not to install administration tools to shorten the installation time. If you choose to install the tools, the tools are only installed on the current cluster node.
  9. On the Instance Name page, select a default or named instance for your installation. If a default or named instance is already installed and you select the existing instance for your installation, the Setup program upgrades the existing instance and lets you install additional components.

    To install a new default instance, no default instance should exist on the computer.

    To install a new named instance, click Named Instance, and then type a unique instance name.

    For more information about instance naming rules, visit the following MSDN Web site:
  10. On the Virtual SQL Server Name page, type a unique name for the clustered Analysis Services. This name is used to identify the failover cluster on the network. The virtual SQL Server name must be unique on the network and must have a name that differs from the host cluster and cluster nodes. Click Next.
  11. On the Virtual SQL Server Configuration page, enter one IP address for each network that is configured for client access. For example, enter one IP address for each network on which the virtual SQL Server is available to clients on a public (or mixed) network. Only one IP address is allowed on each subnet.

    To avoid IP address conflicts, make sure that the IP address that is assigned to a subnet is not shared by any other applications.

    Select the network for which you want to enter an IP address, enter the IP address, and then click Add. The IP address and the subnet appear. Continue to enter IP addresses for each installed network until you have populated all desired networks by using an IP address. Then, click Next.

    The Cluster Group Selection page appears.

    For more information about virtual server configuration, visit the following MSDN Web site:
  12. In the Available Cluster Groups list, click the group that contains the drive that you want to use for Analysis Services. If you click the group that contains the cluster quorum resource, you receive a warning message that recommends that you do not install to the cluster quorum resource. You can also specify a custom path for data files in the Data Files box. To continue, click Next.

    Note You can specify a custom path for data files that are used by Analysis Services. However, you cannot specify a path for the program files. The program files are automatically installed in the following folder:

    SystemDrive:\Program Files\Microsoft SQL Server

    For more information about cluster group selection, visit the following MSDN Web site:
  13. On the Cluster Node Configuration page, specify the nodes to include in the virtual SQL Server. To add a node to the virtual SQL Server, click the computer name in the Available Nodes list, and then click Add. To remove a node from the virtual SQL Server, click the computer name in the Selected Nodes list, and then click Remove. Any nodes that are unavailable appear in the Unavailable Nodes list.

    To create a one-node failover cluster, only the node that will be installed with the virtual SQL server should be listed in the Required Node list. To continue, click Next.

    For more information about cluster node configuration, visit the following MSDN Web site:
  14. On the Remote Account Information page, specify the remote logon information by typing a username and a password for an account that has administrator rights on all nodes of the cluster. This page only appears if you are installing Analysis Services to a remote node. The credentials that you provide are only used during SQL Server setup to configure SQL Server on each node in the virtual SQL Server. This account must be a valid administrator account on all nodes of the cluster. To continue, click Next.

    For more information about remote account information, visit the following MSDN Web site:
  15. On the Service Accounts (Clusters) page, specify the username, the password, and the domain name for Analysis Services accounts. You cannot use the same account that was assigned to the cluster service.

    For more information about cluster service accounts, visit the following MSDN Web site:
  16. On the Domain Groups for Clustered Services page, type DomainName\GroupName for the clustered Analysis Services service. To continue, click Next.

    For more information about domain groups for clustered services, visit the following MSDN Web site:
  17. On the Authentication Mode page, select the authentication mode to use for your SQL Server installation. You must also type and confirm a strong password for the System Administrator (sa) login. To continue, click Next.
  18. On the Collation Settings page, specify the sorting behavior for Analysis Services. You can use one collation for SQL Server and Analysis Services, or you can specify collations for individual components.

    To set separate collation settings for SQL Server and for Analysis Services, click to select the check box to customize for each service account. After you click to select the check box, a drop-down list appears. Select a service from the drop-down list, and then assign the collation for the service. Repeat this step for each service. To continue, click Next.

    For more information about collation settings, visit the following MSDN Web site:
  19. On the Error and Usage Report Settings page, optionally click to clear the check boxes to disable error reporting or feature usage reporting. To continue, click Next.
  20. On the Ready to Install page, review the summary of features and components for your SQL Server installation. To continue, click Install.
  21. On the Installation Progress page, you can monitor installation progress on individual cluster nodes by selecting a node from the Node drop-down list. Setup progress appears for the selected node. To view the log file for a component during installation, click the product or the status name on the Installation Progress page.
  22. On the Completing the Microsoft SQL Server Installation Wizard page, you can view the Setup summary log by clicking the link that is provided. To exit the SQL Server Installation Wizard, click Finish.
  23. If you are instructed to restart the computer, restart the computer now. When you complete the installation, we recommend that you read the message from the Setup program. Failure to restart any one of the specified nodes may cause failures when you run the Setup program again.

How to verify whether the installation is successful

To verify whether Analysis Services has been successfully installed on each cluster node, verify that all the following conditions are true:
  • For each cluster node, open the Cluster Administrator tool, and then click the cluster group that you selected in step 12 in the "How to install Analysis Services on a failover cluster" section. You must find Analysis Services listed as a resource of the cluster group.
  • For each cluster node, you find SQL Server Analysis Services listed in the services list when you open the Services tool.

    Note We do not recommend that you perform any operation on this service at any cluster node. You can manage the clustered Analysis Services by using the Cluster Administrator.
  • For each cluster node, the Analysis Services program files were copied to the following folder:

    SystemDrive:\Program Files\Microsoft SQL Server

  • The Analysis Services data files must be copied to a folder that is created on the shared drive. By default, if you did not specify a custom path for the data files, the files are copied to the following folder:

    SharedDrive:\Program Files\Microsoft SQL Server

  • SQL Server Management Studio and SQL Server Business Intelligence Development Studio must be installed on the cluster node on which you run the Setup program. SQL Server Management Studio and SQL Server Business Intelligence Development Studio must not be available in the other nodes.
  • You can connect to the clustered Analysis Services by using the virtual server name that you specified step 10 in the "How to install Analysis Services on a failover cluster" section.

    Note Even if you install the instance of SSAS as a named instance, you must specify the named instance as the virtual server name. You cannot use VirtualServerName/InstanceName to connect to the instance.

How to remove Analysis Services from a failover cluster

To remove the clustered Analysis Services, follow these steps:
  1. In Control Panel, open Add or Remove Programs.
  2. In the Currently Installed Programs list, click Microsoft SQL Server 2005.
  3. Click Remove.

    The Microsoft SQL Server 2005 Uninstall dialog box appears.
  4. On the Component Selection page, click the instance of Analysis Services in the Select an instance list, and then click Next.
  5. When all the components are removed, click Next on the Setup Progress page to finish the removal process.
Note You must manually remove the Microsoft SQL Server Native Client by using Add or Remove Programs in Control Panel.

Known issues

  • When you install Analysis Services in a cluster group, you must make sure that the status of the group is Online.
  • If you run the Setup program from a terminal session, you must make sure that other users are logged off from cluster nodes.
  • If the installation source files are on a network share location, you must make sure that all the cluster nodes can access the share location successfully.
  • You must be either a member of the Domain Admin group or the owner of the domain group of which you want the cluster service account to be a member. Otherwise, you may receive the following error message:
    You do not have privileges to add account to the domain groups specified for this failover cluster. Ask your domain administrator for privileges to add new accounts to the domain groups, or log on using an account that does have permission.

Modification Type:MinorLast Reviewed:12/12/2005
Keywords:kbsql2005as kbExpertiseAdvanced kbhowto KB910230 kbAudITPRO