Database Administrator at a insurance company with 10,001+ employees
Real User
Aug 5, 2018
Auditing. We mainly use it to follow up on changes to the individual databases. We audit exactly what the database administrators are doing. Those are the main two points. In some situations, we have the need to really audit everything that happens on a certain table, if there is any highly critical information there. We follow no particular regulation criteria. We have an individual catalog of potential issues, and we have a template that we are using. We did a risk assessment, and we identified several points that have to be checked by Compliance Manager and several other tools. We also use SQL Secure from IDERA. We established some custom counters in Diagnostic Manager, for example, to check certain parameters, just to make sure that everything is working as intended by us.
Learn what your peers think about IDERA SQL Compliance Manager. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
SQL Compliance Manager helps database administrators to monitor, audit, and alert on SQL Server user activity and data changes. Unlike its competition, it provides quick configuration of audit settings, a broad list of regulatory guideline templates for audit settings and reports, before and after data values for both regulatory compliance and forensic data investigations, differentiation of data access and between regular and privileged users and applications, easy specification of and...
Our primary use case for this solution is for controls, which we deploy on-premises.
It is mainly used to monitor and audit all SQL Servers, and data is being used by our Internal Audit team for SOX auditing.
We mostly use it so we can audit if a non-admin does something to a database.
We use it for auditing requirements. We also use it to identify activities, see what is going on, who is connecting.
Auditing. We mainly use it to follow up on changes to the individual databases. We audit exactly what the database administrators are doing. Those are the main two points. In some situations, we have the need to really audit everything that happens on a certain table, if there is any highly critical information there. We follow no particular regulation criteria. We have an individual catalog of potential issues, and we have a template that we are using. We did a risk assessment, and we identified several points that have to be checked by Compliance Manager and several other tools. We also use SQL Secure from IDERA. We established some custom counters in Diagnostic Manager, for example, to check certain parameters, just to make sure that everything is working as intended by us.