Page History
...
The Audited Activities tab allows you to change which types of SQL Server events you want to audit. IDERA SQL Compliance Manager audits these events at the server level only.
Available fields
...
These settings must be applied on the individual database level. For more information on how to apply this feature on individual databases please see Audited Database Properties - Before and After Data.
| Anchor | ||||
|---|---|---|---|---|
|
These settings must be applied on the individual database level. For more information on how to apply this feature on individual databases please see Audited Database Properties - Sensitive Columns.
| Anchor | ||||
|---|---|---|---|---|
|
...
If you are auditing privileged user activity and the trusted user is also a privileged user, IDERA SQL Compliance Manager will continue to audit this user because of its elevated privileges. For example, a service account that is a member of the sysadmin fixed SQL Server role will continue to be audited even though the account is designated as trusted. Keep in mind that trusted users are filtered at the database level whereas privileged users are audited at the server level.
To omit, or filter, events generated by specific logins and roles from your audit data trail, select the SQL Server login or role you want to trust and click Add.
Available actions
...
When you update audit settings to audit privileged user activities, these changes are not applied until the SQL trace is refreshed. The SQL trace is refreshed when the SQL Compliance Manager Agent sends the trace files to the Collection Server. To ensure an immediate application of your new audit settings, click Update Audit Settings Now on the Agent menu.
Available actions
...