DATA MANAGEMENT - DATABASE SETTINGS
To configure the settings for the database that the eG manager uses, click on the 
icon available in the Admin tab. Then, select the Database option in the Settings tile.
The eG database stores:
The instantaneous measurements reported by the agents
Hourly, daily and monthly trends that summarize the measurements made in the past
The measure data used for generating the eG reports
Detailed diagnosis measures (if applicable)
Audit logs
Configuration data and details of configuration changes (if the eG license enables Configuration Management)
To ensure that database size does not grow continuously, the eG manager automatically deletes old entries from the database. The DATABASE PURGE PERIODS section governs when the manager deletes entries in each of the eG database tables. You can also schedule day-end activities such as trend computation, scheduled mail generation, and cleanup, by specifying the time in the Day-end activities start at this time field.
Note:
- The DATABASE PURGE PERIODS configured for the hourly, daily, and monthly trend data automatically applies to hourly, daily, and monthly capacity computations as well.
- Typically, capacity computations are performed for a test only if the Capacity Planning flag is explicitly enabled for that test using the CUSTOM SETTINGS - CAPACITY PLANNING page of the eG administrative interface. By default, whenever the eG database cleanup process runs, it checks the status of the Capacity Planning flag of tests and cleans up the old capacity computations of only those tests for which Capacity Planning is enabled at the time of database cleanup. Sometimes, this flag could have been turned on for a few tests for a while, and later turned off. If say, the flag had been turned off before the database cleanup process runs, then the capacity values calculated during this period will remain in the database until the Capacity Planning capability is switched on again for those tests; this is because, cleanup will ignore the old capacity computations for those tests for which the Capacity Planning flag is set to Disabled at the time of cleanup. This stale data therefore may end up occupying critical database space for an infinite period of time! To avoid this, the eG Enterprise provides you with the option to ‘force the cleanup of old capacity data’. By default, this capability is disabled. This is why, by default, the CanForceCapacityCleanup flag in the [MISC_ARGS] section of the eg_services.ini file (in the <EG_INSTALL_DIR>\manager\config directory) is set to false. To enable this capability, set this flag to true and save the eg_services.ini file. Once this is done, then, the next time the database cleanup process executes, it will automatically delete the old capacity computations of all tests, regardless of the current status of the Capacity Planning flag - i.e., regardless of whether/not Capacity Planning is Enabled for those tests.
To optimize accesses to the database, the eG manager uses connection pooling. By using a pre-established set of connections and multiplexing requests over these connections, the eG manager ensures that individual connections are not established and closed for each request. The DATABASE CONNECTION POOL SETTINGS section governs the initial and the maximum number of connections in the connection pool. By default, the Maximum Connections parameter is set to 100.
Clicking the Update button will register the changes made to the system.
If you want to configure cleanup frequencies for the detailed diagnosis data reported by specific tests, click on the Advanced Settings button in this page.
Note:
By default, the eG Enterprise permits trend logging - i.e., the ability to log the activities of the trend manager to a log file. The trend_log file in the {EG_INSTALL_DIR}\manager\logs directory, is the file to which the activities of the trend manager are logged. However, if need be, trend logging can be disabled by setting the Log data trending activity flag in the LOG SETTINGS section of the MANAGER SETTINGS page to No (by default, this will be Yes).
The eG manager keeps track of all the tables that it has created in its database in the eg_db.ini and eg_dbase.ini configuration files. If these files are truncated during the operation of the eG manager (e.g., because the eG manager system ran out of disk space and the configuration files could not be written to disk), the eG manager recreates the measurement tables in the database. The RecreateTables flag in the eg_dbase.ini configuration file in the {EG_INSTALL_DIR}\manager\config directory controls this operation. If this flag is yes, the database tables are recreated. If this flag is no, the tables are not recreated. The RestartOnCorruption flag controls how the eG manager functions when it detects a table in its database for which entries are missing in the eg_db.ini configuration file. If this flag is set to yes, the eG manager automatically restarts itself when it detects a table in the database but entries for the table are missing in the eg_db.ini file.
If the eG manager has not run the data purging/cleanup operation for a long time, or if the data retention period has been reduced and a significant amount of data needs to be cleaned up from the eG database, cleaning up a lot of data at one time can impose a lot of stress on the eG database, slowing down user accesses and the performance of the eG manager. Administrators can control the number of days of data that the eG manager can purge during one run of its day-end data purging process. The MaxDaysToCleanOnce setting in the [MANAGER_SETTINGS] section of the eg_db.ini file controls the number of days of measurement data that is purged during one run of the day-end data purging process. A value of 10 indicates that at most 10 days of data is purged during one run. A value of -1 indicates that there is no limit on the amount of data that can be purged during one run.