Date: Fri, 29 Mar 2024 00:33:43 +0000 (UTC) Message-ID: <1242466398.69507.1711672423946@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_69506_544497656.1711672423944" ------=_Part_69506_544497656.1711672423944 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
IDERA SQL Compliance Manager allows you to audit speci= fic types of SQL Server event data, and distinguish between successful oper= ations and failed operations. Whether an operation succeeds or fails is dep= endent upon whether the login permissions are correct.
SQL Compliance Manager captures the following types of event d= ata.
Data Type | Events Audited | Description |
---|---|---|
Logins |
|
Audits login activity if an access check is perf= ormed and the event status is recorded (success or failure) at the server l= evel |
Administration |
|
Audits common administrative tasks on the SQL Se= rver instance |
Security |
|
Audits all SQL security model activity |
Database Definition (DDL) |
|
Audits create, drop, and alter operations perfor= med on SQL Server objects, database objects, and schema object |
DML | Object permissions | Audits common database operations, such as:= p>
|
Select | SELECT | Audits all SELECT statements executed on databas= e table |
Privileged User | All | Audits all privileged user activity at any level=
If the privileged user is also a trusted user , SQL Compliance Manager continues to audit this user because of its elev= ated privileges. For example, a service account that is a member of the sys= admin fixed SQL Server role will continue to be audited even though the acc= ount is designated as trusted. |
User defined | All | Audits all custom events generated using the&nbs=
p;sp_trace_generateevent stored procedure |
You can capture different event data at one or more of the following lev= els:
This flexibility allows you to achieve precise and granular compliance. = For example, you can configure different audit settings for multiple databa= ses hosted on a single registered SQL Server instance.