Page History
...
| Note |
|---|
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. |
| Note |
|---|
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. |
...
- While enabling Audit Logs from Web or Windows Management console.
- SQL Compliance Manager checks for the following conditions, which all must be met to successfully enable Audit Logs:
- The Agent is reachable.
- SQL Server 2017 or above.
- SQL Compliance Agent 5.5 or above.
- SQL Compliance Manager checks for the following conditions, which all must be met to successfully enable Audit Logs:
| Note |
|---|
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. |
Enable Audit Logs mode using the Windows Management Console
...
For more information about enabling this feature using the Windows Management Console, see Registered SQL Server Properties window - Audited Activities tab.