Page History
...
There are two scenarios of how SQL Compliance Manager can work with AlwaysOn availability group databases:
- Listener. Use this scenario when you want to audit a listener (virtual SQL server instance) that works only with a node in the PRIMARY role.
- Nodes. Use this scenario when you want to audit every node that can be in PRIMARY or SECONDARY roles. Note that the secondary role is read-only.
| Warning |
|---|
You can use only one scenario at a time and , it is not possible to use both of them at the same time on a cluster. |
| Info |
|---|
Each node of the SQL Server instance used in the AlwaysOn Availability Group must have a license. |
Review the following links to configure AlwaysOn Availability Groups:
Configuring Listener scenario Listener scenario:
- Install cluster agent services on all Listener nodes using the SQL Compliance Manager Cluster Configuration Console
- Install cluster agent services on all Listener nodes using the Failover Cluster Manager
- Add the Listener to SQL Compliance Manager
Configuring Nodes scenario:
- Manually deploy the SQL Compliance Manager Agent
...
- Removing a Listener from SQL Compliance Manager
- Exporting/importing audit settings for all AlwaysOn nodes
- Removing an AlwaysOn node from SQL Compliance Manager
| Scroll pdf ignore |
|---|
SQL Compliance Manager audits all activity on your server. Learn more > > IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal |
...