Tuning the eG Database Self-Maintenance Activities
The eG Enterprise manager includes several capabilities that can reduce the maintenance required on the database server.
- Setting the data retention periods: After the eG manager has been installed, set the database cleanup periods according to your requirements (Refer to Administering eG Enterprise's “Configuring the Database Settings” section for details on how these can be set). The cleanup periods indicate how long data is to be maintained in the database. Accordingly, the eG manager automatically purges old data in the database.
Setting the connection pool settings for the eG Manager: The eG manager uses a pool of database connections to optimize accesses to the database – so that a connection is not opened and closed for every request being issued to the database server. By using a connection pool, the eG manager reduces unnecessary load of connection establishment and teardown on the database server. The connection pool setting has a lower and upper bound – the lower limit representing the minimum number of connections that will remain established between the manager and the database, and the upper limit being the maximum number of connections that the eG manager will use to access the database. The maximum number of connections required is dependent on the performance of the database server itself. A rule of thumb for setting the maximum limit is provided in the “Sizing the Hardware and Database required by an eG Manager” document. For configuring the database connection pool settings refer to the Administering eG Enterprise's “Configuring the Database Settings” section.
Since the number of connections needed is highly dependent on the performance of the database and the hardware allocated to it, tuning the connection pool is a trial and error process. Check the file error_log under the <EG_INSTALL_DIR>\manager\logs directory of the eG manager system for messages relating to the connection pool. If the used connections hit the maximum connection pool limit often, it means that the database connection pool may need to be resized or that the database itself may need retuning.
Whenever you add new components/servers to be monitored and whenever you change the cleanup period, please revisit the settings above to ensure that the database server in geared to cope up with the increased load.