Date: Fri, 29 Mar 2024 10:53:33 +0000 (UTC) Message-ID: <520487169.69915.1711709613045@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_69914_1321010371.1711709613041" ------=_Part_69914_1321010371.1711709613041 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
IDERA SQL Compliance Manager 5.4 and later allows you to take ad= vantage of the SQL Server Extended Events (XEvents) feature to track and ar= chive specific events occurring in your monitored environment. SQL Server E= xtended Events is an event handling system that offers lower overhead and d= elivers performance gains over the default SQL trace method. In SQL Complia= nce Manager 5.4 and later, only SELECT and DML events for SQL Server = 2012 and later versions are supported by this feature. All functionality th= at 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 ca= pturing 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 t= he 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 Exte= nded 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.
Extended Events does not Support Audit= ing a specific table/object
Due to technical limitations, Extended Events does not support auditing = for a specific table/object. To audit a specific table/object please audit = using SQL Tra= ce or SQL= Server Audit Logs.
IDERA SQL Compliance Manager supports Extended Events based auditing for= SQL Server 2012 or above. The following prerequisites and conditions are r= equired to switch auditing based on Extended Events.
To enable Extended Event mode using stored procedures, go to the locatio=
n where the IDERA SQL Compliance Manager Console application is installed, =
and then execute the stored procedure
. For example:
[dbo].[sp_enable_ExtendedEvents]
EXEC [dbo].[sp_enable_ExtendedEvent=
s] <SERVER_NAME>,<YES/NO>
Users wanting to take advantage of SQL Server Extended Events auditing c= apabilities can do so by completing the following steps:
For more information about enabling this feature using the Windows Manag= ement Console, see Registered SQL Server Properties window= - Audited Activities tab.