Starting IDERA SQL Compliance Manager 6.0 and above, the SQL Compliance Manager default Event Collection method is SQL Server Audit Specifications. Use the SQL Server Audit Logs feature to track specific events occurring in your monitored environment. SQL Server Audit Logs is an event-handling system that helps you reduce the size of data gathered and deliver performance gains over the default SQL trace method. In SQL Compliance Manager 5.5 and later, only SELECT and DML events for SQL Server 2017 and later versions are supported by this feature.
Upon version upgrade or new installation, the SQL Compliance Manager Event Collection method setting changes to "SQL Server Audit Specifications" by default. Users can manually change the collection method. |
Before and After Data is not supported on the RDS instance due to the limitation of creating trusted assemblies using SQL script. BAD operations are removed from the properties, reports, alerts, and summary tabs. |
To manually change the capturing events method, go to:
IDERA SQL Compliance Manager supports Audit Logs based auditing for SQL Server 2017 and above. The following prerequisites and conditions are required to switch auditing based on Audit Logs.
When using SQL Server Audit, due to a technical limitation, it's recommended to limit the number of Trusted and Privileged users included in audit configurations. Exceeding certain thresholds may prevent audit rules from being applied as expected. |
Users wanting to take advantage of SQL Server Audit Logs auditing capabilities can do so by completing the following steps:
For more information about enabling this feature using the Windows Management Console, see Registered SQL Server Properties window - Audited Activities tab.
|