Date: Thu, 28 Mar 2024 19:48:11 +0000 (UTC) Message-ID: <1413502132.68993.1711655291023@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_68992_515222754.1711655291022" ------=_Part_68992_515222754.1711655291022 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Use the following checklist to help you optimize IDERA SQL Compl= iance Manager performance by fine tuning your auditing settings to prevent = excess data collection.
As SQL Compliance Manager collects audit data and stores this informatio= n in the Repository, the event databases grow. When SQL Compliance Manager = is configured to audit all SQL Server events, the event databases can = grow very large (up to several gigabytes) in a single 24-hour period, espec= ially in larger environments or environments with high-volume traffic. For = more information about event databases in the Repository, see Product components and ar= chitecture.
:tick: | Follow these steps ... |
---|---|
:tick: | Archive or groom stale audit data from the event= databases on a regular basis. Archiving allows you to move older events wh= ereas grooming allows you to delete older events. For more information, see= How archives work an= d How grooming works. |
:tick: |
Re-index and shrink each event database from which you have archived or = groomed data. You can use native Microsoft SQL Server tools or other t= hird-party tools such as IDERA SQL Defrag Ma= nager. |
:tick: | Carefully choose the events you need to audit. T= he growth and overall size of the event databases is a direct result of the= auditing configuration you define. For more information, see Fine tune your audit settings= a>. |
:tick: | Consider configuring Event Filters. Event fil= ters prevent collection and storage of unwanted events. For example, you ca= n use Event Filters to exclude specific applications and operations that pe= rform benign activities, and therefore do not require auditing, from your a= udit trial. For more information, see Event Filters. |
:tick: | Consider configuring trusted user filters. Trust= ed user filters sift out events initiated by specific user accounts on an i= ndividual database. In general, a trusted user filter will be more resource= -efficient than an event filter when excluding non-useful or benign events = from your audit data collection. |