Page History

...

1. Start the SQL CM Management Console, and then click New > Registered SQL Server.
2. In the SQL CM Configuration Wizard, specify or browse to the listener you want to register with SQL Compliance Manager, and then click Next. In this example, use the virtual SQL Server name AOAGLISTENER.
   
3. In the SQL Server Cluster window, check This SQL Server instance is hosted by a Microsoft SQL Server Cluster virtual server, and then click Next. This step makes the listener, in this example AOAGLISTENER, into a virtual SQL Server name.
   
4. In the SQLcompliance Agent Deployment window, verify that the Manually Deploy is selected, and then click Next. This option is required for all virtual SQL Servers.
   

...

1. Image Added

1. Select always on database (in this case ‘TestBase’). Press ‘Next’ button.

1. Users should see the information about all nodes where always on database will be replicated (see the screenshot below). If database is not always on, this screen will be skipped.

1. In the Select Databases window, check the AlwaysOn database that you want to audit, and then click Next. In the following example, the AlwaysOn database is TestBase.
   Image Added
   SQL Compliance Manager displays the AlwaysOn Availability Group Details window including a list of all nodes where the AlwaysOn database is replicated. Note that this window appears only if the database selected for auditing is AlwaysOn. The wizard skips this window for regular databases.
   Image Added
2. If the AlwaysOn Availability Group Details window is displayed, click Next to continue.
3. In the Audit Collection Level window, select the desired audit collection level for the database, and then click Next.
   Image Added
   In the Permissions Check window, SQL Compliance Manager verifies that all the required permissions are in place on the SQL Server instance you want to audit.
   Image Added
4. After all operations are complete, click NextChoose audit collection level and follow all necessary steps.

1. Ensure that all permissions checks are passed (see the screenshot below).

...

The Listener scenario is recommended for users who want to audit only AlwaysOn databases on the Primary node using LISTENER. If you want to audit read-only Secondary nodes , use the Nodes scenario.