To ensure ApexSQL Audit Central performance there are some best practicesthat should be followed. Failure to follow these best practices may result in underperformance.
Place ApexSQL Audit Repository on a dedicated datastore when possible, if not, then place Repository on one with the most available I/O
Ensure that only minimal number of events are being audited by following recommendations and best practices described in this article
Setup more aggressive auditing configuration filter using Advanced filter
Consider adding more ApexSQL Audit Central servers into environment and redistributing auditing SQL Servers by following the instructions in this article
Additional optimization options
Ensure that Repository integrity checks not occur during peak hours. Default Repository integrity check occur on one hour interval
Change Repository archiving schedule to trigger more frequently. Default schedule archiving will occur when Repository size exceeds 20 GB or Repository is older than one month.
Quick sizing reference In the chart below you can find quick reference that combines multiple guides in one that can be handy to size your ApexSQL Audit Central server
From the tables and charts above, you can see that ApexSQL Audit Central sizing is not conditioned by the number of audited SQL Servers but by the amount of daily audited data. This means you can audit up to 10 heavy loaded or up to 50 medium loaded or up to 100 small loaded SQL Servers. In theory, only one SQL Server with an extremely heavy load can reach the limits of some ApexSQL Audit Central size and you should consider adding more hardware resources to it.
For more information please visit the ApexSQL Audit sizing and system requirements article (add link once the mentioned article is published)
