Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You can use only one scenario at a time and it is not possible to use them at the same time on cluster.

Info

Each node of the SQL Server instance used in the AlwaysOn Availability Group must have a license.

 

Anchor
listener
listener
Configuring the Listener scenario

...

Users can select all of the appropriate audit settings for each AlwaysOn database and export these settings as XML files. You then can import the files into the remaining instances or nodes in the group.

 

To import the audit settings to each node, click Import on the Summary tab. Choose the exported XML file, the information you want to import, and the servers to which you want to apply the settings. Select all the other servers in the availability group as the target for audit settings. After users apply the settings from the file, each member of their availability group is set to audit in exactly the same way as noted in the exported file. This process also allows you to add additional databases that are the part of an availability group on these servers.

Removing an AlwaysOn node from SQL Compliance Manager

To remove an AlwaysOn node from SQL Compliance Manager, first stop the agent service using the Failover Cluster Manager before attempting to remove a node instance from SQL CM. This step must be performed if you may want to add back to SQL CM the removed node using the Manual Deployment option without any agent deployment. In this case, ignore the error message that appears after you remove the node.

 

SQL Compliance Manager audits all activity on your server. Learn more > >

...