Versions Compared

Key

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

...

  1. Start the IDERA SQL Compliance Manager Management Console and click New > Registered SQL Server. SQL Compliance Manager displays the SQLcm Configuration Wizard - Add Server.
  2. On the SQL Server window, specify or browse the listener you want to register with SQL Compliance Manager, and click Next
  3. On the SQL Server Cluster page, check This SQL Server instance is hosted by a Microsoft SQL Server Cluster virtual server box, and click Next. This step makes the listener into a virtual SQL Server name.
  4. On the SQLcompliance Agent Deployment page, verify that the Manually Deploy is selected, and click Next. This option is required for all virtual SQL Servers.
  5. On the Select Databases page, check the AlwaysOn database that you want to audit, and click Next.  
  6. SQL Compliance Manager displays the AlwaysOn Availability Group Details page including a list of all nodes where the AlwaysOn database is replicated.

    Info

    This step is valid only if the database selected for auditing is AlwaysOn. The wizard skips this page for regular databases.

  7. If the AlwaysOn Availability Group Details window is displayed, click Next to continue.
  8. In On the Audit Collection Level page, select the desired audit collection level for the database, and click Next.
  9. In On the Permissions Check page, SQL Compliance Manager verifies that all the required permissions are in place on the SQL Server instance you want to audit.
  10. After all operations are complete and all permissions checks pass, click Next. The Summary page displays the audit settings for the SQL Server instance.
  11. Click Finish to close the wizard. SQL Compliance Manager displays the newly-added SQL Server instance and AlwaysOn database in the Explore Activity tree.
  12. Make all necessary audit settings for the listener and AlwaysOn databases, and then update the configuration and begin collecting data. It is recommended to update the configuration before collecting data because users are unaware of  which node is PRIMARY. After updating the configuration, be sure to click Refresh in the node context menu to apply the settings to the displayed information.

...