This article explains how to resolve the problem when the reports in ApexSQL Audit show no records for a specific event type or a specific SQL database object; what to check and how to fix it.
The reports in ApexSQL Audit show no audited information for a specific event or a specific object (for example no executed SELECTs are shown, although SELECT is checked in the report).
The situation is similar when the events are shown only for some SQL objects (tables, views, functions, and procedures). For example, INSERTs, DELETEs, and UPDATEs are shown for the Person.Person table, but not for Person.AddressType.
The reason that some of the events are not shown in the reports is that these events are not captured, as they are not selected for auditing in ApexSQL Audit GUI.
To prevent rapid growth of the ApexSQL Audit central database repository, ApexSQL Audit, by default, does not audit all events that can be audited. Two types of events unchecked by default are Queries (SELECT statements) and Warnings. The SELECT statement execution and warnings are among the most common events in a database, and generally not required to be audited. Therefore, these events will not be audited unless a user selects them manually.
- In ApexSQL Audit GUI, select the SQL Server instance and database for which the events are not appearing in the report.
In the Operation types list, select the Query option to audit SELECT statements and Warning to audit warning messages.
If ApexSQL Audit reports show no audited information for a specific object, check it in the Objects list.
In the notification that appears above the settings section click Apply.
The new filtering settings will be applied to all upcoming events, which will then be audited and displayed in the reports.