After a MEGA + Advisor RDBMS deployment, the disk dedicated to the SQL motor fills quickly. It has only been a couple of months and the volume is full (25 GB) despite de fact that little modelling has been done. (The database contains few objects.) Data is saved on a SAN disk.
Data purge scripts of temporary and archived objects have been executed on the MEGA SQL repositories, but the database log volume continues to increase.
Do you have suggestions to limit this phenomenon?
Is it due to the absense of log purges in the SQL databases? Is it correct to assume that transaction logs are purged once the transaction is abandoned or dispatched?
If I consolidate in the log management interface in the MEGA Administation tool, does this consolidate in the SQL database or are there additional steps to clean up the SQL database in that regard?
Note that in standard HOPEX installation a certificate is installed with expiration on 3rd of February 2020. If your installation cease to work, please have your administrator sign-in and download the new certificate. Thank you for your understanding. Download Certificate+