Active Roles provides the option to store the Management History data in a separate database. If you use this option, then you have two databases, the Configuration database and the Management History database, each of which (or both) can belong an availability group. In this case:
To specify the listener
You can start Configuration Center by selecting Active Roles Active Roles Configuration Center on the Apps page or Start menu, depending upon the version of your Windows operating system. For detailed instructions, see Running Configuration Center.
Active Roles can use the Microsoft SQL Server database mirroring technology to improve the availability of the Administration Service. Database mirroring provides a standby database server that supports failover. Once the current database server fails, the Administration Service can recover quickly by automatically reconnecting to the standby server.
Database mirroring increases database availability by supporting rapid failover. This technology can be used to maintain two copies of a single Active Roles database on different server instances of SQL Server Database Engine. One server instance serves the database to the Administration Service; this instance is referred to as the principal server. The other instance acts as a standby server; this instance is referred to as the mirror server.
Within the context of database mirroring, the mirror server acts as the failover partner for the principal server. In the event of a disaster, the mirror server takes over the role of the principal server, bringing the mirror copy of the database online as the new principal database. The former principal server, if available, then assumes the role of the mirror server. This process, known as role switching, can take the form of:
In any role-switching scenario, as soon as the new principal database comes online, the Administration Service can recover by automatically reconnecting to the database.
For more information about the database mirroring technology, and instructions on how to set up and administer database mirroring on SQL Server, see the “Database Mirroring” topics in the SQL Server product documentation at http://msdn.microsoft.com/en-us/library/bb934127.aspx.
NOTE: The Active Roles replication function is not supported for the databases that have mirroring set up. If you attempt to perform the “Promote to Publisher” or “Add Subscriber” operation on such a database, you receive an error.
Here we assume that mirroring for the database of Active Roles is already set up on the SQL Server side in accord with the recommendations and instructions found in Microsoft’s documentation, so that the following conditions are fulfilled:
Under these conditions, the Administration Service can be instructed to automatically connect to the new principal database in the event of database server role switching. On the computer running the Administration Service, add a string value to each of these two registry keys, and then restart the Administration Service:
If the default instance is used, the value data is the short name of the computer running SQL Server. Otherwise, the value data is the short name of the computer, followed by a backslash, followed by the name of the instance (such as ComputerName\InstanceName).
By default, the same database is used for the Configuration and Management History data; therefore, the value data would be the same in the DatabaseConnectionString and CHDatabaseConnectionString keys.
To restart the Administration Service, open Configuration Center and click the Restart button at the top of the Administration Service page in the Configuration Center main window. For instructions on how to run Configuration Center, see Running Configuration Center later in this document.
In the Active Roles console, you can view the mirroring status of the Configuration or Management History database that is used by a particular instance of the Administration Service:
If no information is displayed in the Database Mirroring area, then database mirroring is not configured.
You can also view the mirroring status of a Configuration database or a Management History database on the General tab in the Properties dialog box for the object representing that database in the Configuration/Server Configuration/Configuration Databases or Configuration/Server Configuration/Management History Databases container, respectively.