Failover cluster resource dependencies in SQL Server

Article translations Article translations
Article ID: 835185 - View products that this article applies to.
Expand all | Collapse all

On This Page

Summary

When you install Microsoft SQL Server on a cluster as a SQL Server failover cluster instance, a specific set of SQL Server resources that have dependencies on other resources in the cluster group are created. 

Important Do not change the default dependency tree except for the changes that are listed in this article or the changes that are listed in the following article in the Microsoft Knowledge Base:
819546 SQL Server support for mounted folders

Example 1 - Default SQL Server failover cluster instance dependencies

Collapse this imageExpand this image
2813773


In this diagram, notice the following:
  • Cluster Disk 1 has no required dependencies.
  • IP Address: xxx.xxx.xxx.xxx has no required dependencies.
  • IP Address: xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx has no required dependencies.
  • Name: SOFTY dependencies are IP Address: xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx and IP Address: xxx.xxx.xxx.xxx.
  • SQL Network Name (SOFTY) required dependencies are IP Address.
  • SQL Server dependencies are Cluster Disk 1 and Name: SOFTY.
  • SQL Server has no required dependencies.
  • SQL Server Agent dependencies are SQL Server.
  • SQL Server Agent has no required dependencies.
Example 2 - SQL Server 2008 Analysis Services failover instance dependencies

Collapse this imageExpand this image
2813774


In this diagram, notice the following:
  • Analysis Services (LOCALINSTANCE) dependencies are Cluster Disk 2 and Name: STANDALONE2008R.
  • Analysis Services (LOCALINSTANCE) has no required dependencies.
  • Cluster Disk 2 has no required dependencies.
  • IP Address: xxx.xxx.xxx.xxx has no required dependencies.
  • IP Address: xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx has no required dependencies.
  • Name: STANDALONE2008R dependencies are IP Address: xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx and IP Address: xxx.xxx.xxx.xxx.
  • SQL Network Name (STANDALONE2008R) required dependencies are IP Address.
  • SQL Server (LOCALINSTANCE) dependencies are Cluster Disk 2 and Name: STANDALONE2008R.
  • SQL Server (LOCALINSTANCE) has no required dependencies.
  • SQL Server Agent (LOCALINSTANCE) dependencies are SQL Server (LOCALINSTANCE).
  • SQL Server Agent (LOCALINSTANCE) has no required dependencies.
Example 3 - SQL Server 2008 failover instance dependencies with a mount point
Collapse this imageExpand this image
2813775

In this diagram, notice the following:
  • Cluster Disk 1 has no required dependencies.
  • Cluster Disk 4, Mountpoint dependencies are Cluster Disk 1.
  • Cluster Disk 4, Mountpoint has no required dependencies.
  • IP Address: xxx:xxxx:c0:xxxx:xxxx:c597:8cb0:49f2 has no required dependencies.
  • Name: SOFTY dependencies are IP Address: xxx:xxxx:c0:xxxx:xxxx:c597:8cb0:49f2 and IP Address: xxx.xxx.xxx.88 .
  • SQL Network Name (SOFTY) required dependencies are IP Address.
  • SQL Server dependencies are Name: SOFTY, Cluster Disk 4, Mountpoint and Cluster Disk 1.
  • SQL Server has no required dependencies.
Note The double dependency on the mount point is to make sure that SQL Server cannot start and load databases without the physical disks being available. This helps prevent database corruption.

The default dependency tree for SQL Server has the following implications:
  • The SQL Server Agent resource depends on the SQL Server resource, and the SQL Server Fulltext resource in SQL Server 2005 depends on the SQL Server resource.
  • The SQL Server resource depends on the SQL network name resource, on the physical disk resources and on mounted folders that contain the database files. 
  • The SQL network name resource depends on the SQL IP address resource.
  • The SQL IP address resource and the physical disk resources do not depend on any resources

More information


For information about how to add dependencies to a SQL Server resource:

Limitations and restrictions

You should be aware that if you add any other resources to the SQL Server group, those resources must always have their own unique SQL network name resources and their own SQL IP address resources.Do not use the existing SQL network name resources and SQL IP address resources for anything other than SQL Server. If SQL Server resources are shared with other resources or are set up incorrectly, you may experience the following problems: 
  • Outages that are not expected may occur.
  • Database corruption may occur.
  • Service pack installations may not be successful.
  • The SQL Server Setup program may not be successful. If this occurs, you cannot install additional instances of SQL Server or perform routine maintenance. 
  • SQL Server may not come online.
  • Disks may not be available for SQL Server use.

Additional considerations

  • FTP with SQL Server replication: For instances of SQL Server that use FTP with SQL Server replication, your FTP service must use one of the same physical disks that the installation of SQL Server that is set up to use the FTP service uses.
  • SQL Server resource dependencies: If you add a resource to a SQL Server group, and if you have a dependency on the SQL Server resource to make sure that SQL Server is available, we recommend that you add a dependency on the SQL Server Agent resource instead of adding a dependency on the SQL Server resource. To make sure that the computer that is running SQL Server remains highly available, configure the SQL Server Agent resource so that it does not affect the SQL Server group if the SQL Server Agent resource fails. 
  • File shares and printer resources: An exception is the file share that is used by the SQL Server FILESTREAM feature. A printer resource should not be in your SQL Server group. File Share or Printer resources require their own Network Name and IP resource on a Windows Server 2003 failover cluster. File shares and printer resources also require their own Network Name and IP resource for a Client Access Point on Windows Server 2008 and later versions. For a failover cluster instance on Windows Server 2008 or a later version, use the Create a Shared Folder Wizard to specify a unique name and other settings for the shared folder.
  • Performance: Decrease in performance and loss of service to the computer that is running SQL Server may occur when the following conditions are true:
    • A File Share cluster resource that does not use the FILESTREAM feature is installed on the same physical disk resource on which SQL Server is installed.
    • A Printer cluster resource is installed on the same physical disk resource on which SQL Server is installed. 

Properties

Article ID: 835185 - Last Review: February 9, 2013 - Revision: 6.0
Applies to
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Standard Edition for Small Business
  • Microsoft SQL Server 2008 R2 Analysis Services
  • Microsoft SQL Server 2008 R2 Express with Advanced Services
  • Microsoft SQL Server 2008 R2 Workgroup
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Standard
  • SQL Server 2012 Enterprise Core
Keywords: 
kbsql2005cluster kbtshoot kbclustering kbpag kbGuidelines kbappnote KB835185

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com