IDERA SQL Compliance Manager 5.4 and later allows you to take advantage of the SQL Server Extended Events (XEvents) feature to track and archive specific events occurring in your monitored environment. SQL Server Extended Events is an event handling system that offers lower overhead and delivers performance gains over the default SQL trace method. In SQL Compliance Manager 5.4 and later, only SELECT and DML events for SQL Server 2012 and later versions are supported by this feature. All functionality that works on top of these events, such as DML/Select filtering, Before-After data, sensitive column auditing, and more, work with this new method of capturing event data.
When Extended Events mode is enabled, events generate XEL files instead of trace files (.xel rather than .trc) but the files still are located in the Agent trace directory.
There are two ways to enable Extended Event capture:
Extended Events captures extra Execute events
Due to differences in how Microsoft has implemented Extended Events compared to other auditing methods, when auditing via Extended Events the user will see extra Execute events as compared to the same data captured by other auditing methods.
IDERA SQL Compliance Manager supports Extended Events based auditing for SQL Server 2012 or above. The following prerequisites and conditions are required to switch auditing based on Extended Events.
To enable Extended Event mode using stored procedures, go to the location where the IDERA SQL Compliance Manager Console application is installed, and then execute the stored procedure
EXEC [dbo].[sp_enable_ExtendedEvents] <SERVER_NAME>,<YES/NO>
Users wanting to take advantage of SQL Server Extended Events auditing capabilities can do so by completing the following steps:
For more information about enabling this feature using the Windows Management Console, see Registered SQL Server Properties window - Audited Activities tab.