
Database size spiraling out of control
Anyone else experiencing database 'bloat' in the cloud? I discovered on Friday that my main database had grown to over 3GB with automatic backups taking the team size to 7GB which had the effect of making manual backups (and therefore downloads) impossible. With some assistance from support I have now downloaded the database, and by opening it in the app discovered that history was running 2.9GB..... After deleting this locally and the uploading the database to a new team it's showing a more sensible size of 39MB!! (although since last night 3 automatic backups have taken the team size to 195MB??)
Deleting history in the cloud seems to have little to no effect on overall size.
It's not an acceptable state of affairs to have to periodically download an archive and re-upload to keep the size 'normal'! Not least because any external links from Integromat will have to be reconfigured.
I'll report back when I've heard more from support.
-
I'm using the cloud version and have 5 active databases. One of which has over 600,00 records and my total for the team is 2.3gb. Most of my records have some sort of attachment. I do regularly remove older backups every couple of months - simply because the keep growing and I like Ninox to put a cap on these (or at least give the control to). I do indeed delete history to.
Are you storing large images ?
-
In addition to this topic... https://forum.ninox.com/t/h7hrzg3
I would add that any changes to the database schema also causes bloat. The old schema remains in the database and the new modified schema is just appended to the file.