Page History
IDERA SQL Compliance Manager provides flexibility for your audit settings, allowing you to collect a wide range of SQL Server events. However, extensive auditing requires sufficient disk space, processing time, and a very stable network connection. Your environment may not provide the resources necessary to audit every event that occurs on a particular SQL Server instance.
The following auditing options possibly are resource-intensive and can cause significant growth in the Repository databases, thereby decreasing SQL CM Compliance Manager performance. For more information about avoiding performance issues, see Reduce audit data to optimize performance.
...
Gathering events directly from the system databases is useful only under very specific circumstances in an audited environment. Accidental collection of SQL Server internal operations can occur when you audit DML or SELECT events, resulting in the storage of unnecessary data. If you want to continue auditing system databases, consider routinely archiving or grooming your event databases.
...
| Note |
|---|
Auditing the Login Failed event category does not result in the collection of the same level of data. You can leave this action enabled. |
| Scroll pdf ignore | ||||||
|---|---|---|---|---|---|---|
Newtabfooter |
|
...
SQL Compliance Manager audits all activity on your server. Learn more > >
...
...