When a high level of CPU utilization is identified by the FireBird SQL Server process, this signals a need for maintenance operations on the GSX Analyzer database. The FireBird SQL Server process manages the GSX Analyzer database and an unmaintained GSX Analyzer database can cause an increase in its CPU resource needs.
Follow this article to learn how to maintain your GSX Analyzer database to lower the CPU resource needs and improve efficiency and functionality in GSX Analyzer.
GSX Analyzer houses an abundance of alerts, statistics, and reports in its database and over time this can grow substantially. The database growth depends on the configured options in GSX Monitor and Analyzer.
Causes of high database growth in GSX Analyzer and the respective solutions:
- A large number of alerts arriving regularly from GSX Monitor.
- Check the health, maintenance and alerting thresholds for the corresponding source of the alert.
- When automated deletion of log reports, alerts, and replication reports are not set.
- See "Documents Deletion in the Database" here in our Online Help.
- Not enabling automated database compaction.
- See "Enable Compact" here in our Online Help.
GSX Analyzer will be unavailable until the compaction process is complete.
The quickest immediate method to lower the FireBird SQL Server process is to compact the GSX Analyzer database as soon as possible:
- Launch the GSX Analyzer Manager.
- Program Location: \GSX Analyzer\AdminTools\AManager\GSXAnalyzerAManager.exe
- Select Database - Compact Database:
- Click Yes, verifying you want to compact the database to initiate the backup process:
- Once the compaction process is completed you can choose to keep or remove your precompacted database:
- Select No.
- We recommend, at least temporarily, keeping the database in case restoring the original database is necessary.
- Click Close.
The GSX Analyzer database compaction is complete and the FireBird SQL Server process will reduce in CPU utilization.