Size reduction
Our app has a steady growing database and we frequently have to decrease the disk size by a restore and rebuild, which only temporarily helps. If we don't restore and backup our app performance serious suffers. On the mendix support page about database size reduction the following is written:
The only reason to use either the VACUUM FULL or restore and backup option is to physically reclaim lost space of a table (records of the same entity) that was once very large but has drastically been reduced in size (deleted records) and which you do no longer expect to grow back to (nearly) its previous size in the future. As in that case, and in that case only, leaving the deleted records in place to be reused makes no sense anymore.
source: https://docs.mendix.com/howtogeneral/support/database-maintenance-size-reduction
As i started, our database grows steady in size and we frequently do a restore and backup to reclaim database size. However, on the mendix support page is explained only to restore and backup if the database is not expected to grow to it's previous size.
It's seems that our actions contradicts with the support page. Can this have any consequences?
Table/index size ration
Furthermore, we can clearly notice that after a restore and backup our database size steady grows again. Just after restore and back up the index/table ratio is close to 1, but as the size increases again the index size is four times as big than the increase in table size (see figure).
Can this strong increase in index size have any effects? What could be the cause of this relative big increase in index size?