Page History
...
On each registered SQL Server instance, the SQLcompliance Agent starts a SQL Server trace to copy SQL event log entries, called audit events, to trace files. Trace files are temporary files that store audit events until these events can be sent to the Collection Server. Trace files are located in a trace file directory on the audited SQL Server computer. For more information, see How the SQLcompliance SQL Compliance Manager Agent works.
SQL Compliance Manager collects all events in the SQL trace that are related to the activity you want to audit. When choosing the activities you want to audit, be aware that activities performed through the SQL Server client tools, such as Management Studio, may log multiple events. For example, when you add a login to a role, the SQL trace records one event for the add login action and another event for changing the default language. In this case, SQL Compliance Manager collects each event as separate audit data according to the SQL trace.
Using SQL Server Extended Events
IDERA SQL Compliance Manager 5.4 includes support for event handling with SQL Server Extended Events. This optional feature is available for use in auditing instead of using SQL Trace. Running Extended Events offers a performance improvement over the default SQL Trace audit event gathering system and is available for instances running SQL Server 2012 and later. For more information about using the Extended Events option, see Using SQL Server Extended Events.
Using the Collection Server
...
| Note |
|---|
It is important to note that the Before-After Data capture feature modifies the application schema by creating triggers on any table for which such data collection is enabled. |
| Excerpt |
|---|
SQL Compliance Manager audits all activity on your server. Learn more > > |
...
| Products | Buy | Support | Community | About Us | Resources | Legal