Page History
| Note |
|---|
In SQL Compliance Manager version 5.6.1 the Row count functionality may show as “Not Applicable”. The issue occurs when you execute large query and during execution the start and the end of the SQL Statement get captured in different trace files. Since both events are located in different trace files, SQL CM is not able to map these events and therefore displays that Row count is “Not Applicable”. Users can increase the time of collection (default is set to 60 seconds) to capture Row count correctly |
| Note |
|---|
This feature is only available for SQL Server 2008 and above. |
| Note |
|---|
To capture row count information, update the SQL Compliance Manager Agent to version 5.5 or above. |
IDERA SQL Compliance Manager audits and reports on the frequency that users access sensitive data, alerting about suspicious behavior.
...
The row count information is available in the General tab of any event properties, as well as the Audit Events tab in the Explore Activity viewView.
For select statements with sensitive columns, event properties contain a Sensitive Columns tab which shows the row count value for each audited sensitive column.
When you expand the audit events, the Audit Events tab shows the row count information in the event details.
| Info |
|---|
If you use SQL statements with joined queries, SQL Compliance Manager displays multiple (equivalent to the number of distinct queries joined) events, however, row count information is available only with the primary statement and not applicable with other statements. |
...
For more information, see Alert on Audit Data and Status.
| Info |
|---|
If you use SQL statements with joined queries, only the primary statement triggers any alert set for row count. |
...
For more information, see Report on Audit Data.
...