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 ?
-
Mel Charles No - all small images, as the 39MB size illustrates. One useful feature of the desktop app is that it allows you to see how much space each item is using. The database size was c. 27MB, Files c/ 27MB History 2.92GB.....!
-
-
Thats very odd. I've just looked and am ready to purge some backs ups
currently I have 62 automated and 3 manual and it is not bloating me at all. so yours must be an isolated case. Be interesting to know what support say
-
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.
-
Thanks Sean this would perhaps explain why clearing the history in the cloud doesn't help the size - it's still there in the background.
Looks like the now I'm stuck with duplicating the database and re-configuring my Integromat scenarios...
BTW - can you explain the need to "rename" the duplicated database as described in the linked thread? -
simon It isn't necessary. My statement assumed everyone wants their new database to have the same name as the old one. Since the Ninox Mac app won't let you create a duplicate database with the same name, you would have to rename it.
I don't use Ninox in a professional capacity, but I can see why it would be prudent to give the duplicated database some type of version number and keep the original database as is.
-
-
I can vouch that having the restored database added to the pot with (restored) appending its extremely useful ! - as you know exactly where you stand and as sean says it's a easy to rename it too.
-
I restored "VNBC master...." last night – now 15MB instead of 775MB! I have no idea why it still thinks I have back ups of 2GB...
There seems to be something very wrong going on here! -
Simon
Have you tried a screen share with support to see if they can get to the bottom of your issues. I restore files regularly for testing etc. and simply not getting the issues you are experiencing.?
-
hello, do you have an idea to avoid saturating the storage space?