Using a virtual Microsoft SQL Server cluster instance to host the Configuration Manager 2007 site database is supported. Clustered SQL environments allow for failover support for the virtual SQL server, and therefore, they provide greater reliability for the site database. Hosting the site database on a clustered SQL server configured for failover support does not provide additional processing or load balancing benefits. Only active/passive SQL Server cluster configurations are supported for hosting the site database. Configuring the SQL Server cluster in an active/active cluster configuration or in a Network Load Balancing (NLB) cluster configuration is not supported.

Configuration Manager 2007 Setup will not create or configure the SQL cluster. The clustered SQL environment must already be configured, and functional, before it can be used to host the site database. Configuration Manager 2007 will automatically check once an hour for SQL cluster node configuration changes. Changes in the SQL node configuration affecting Configuration Manager 2007 component installation, such as a node failover or the introduction of a new node to the SQL cluster, will be managed by Configuration Manager 2007 with no action by the administrator necessary.

When using a clustered SQL Server instance to host the site database, TCP/IP network protocol communication is required for each SQL Server cluster node network connection to support Kerberos authentication. The named pipes communication protocol is not required, but can be used to troubleshoot Kerberos authentication issues. When using SQL Server 2005 to host the site database, the network protocol communication settings are configured in SQL Server Configuration Manager under SQL Server 2005 Network Configuration. For a list of supported SQL Server versions, see Configuration Manager Supported Configurations.

Performance Considerations

When using a clustered SQL database to host the Configuration Manager 2007 site database, degradation in performance often occurs. This is because the site server must find the active node of the SQL cluster before it can connect to the site database. For Configuration Manager 2007 sites supporting a large number of clients, or if the primary site server CPU usage is too great, the site database can be moved to a remote SQL Server, or SQL Server cluster instance to reduce primary site computer CPU usage. Although Configuration Manager 2007 supports using a SQL cluster for hosting the site database, it will not support using SQL database mirroring technology or peer-to-peer replication.

SMS Provider Considerations

When using a clustered SQL Server database to host the site database, the SMS Provider should be located locally on the site server or on a third machine not hosting a SQL cluster node. Installing the SMS Provider on a SQL Server cluster or a computer acting as a clustered SQL Server node is not supported.

See Also