An interesting development. I have reduced all graph "Keep" durations to minimal amounts, I left it till the graphs updated with basic graphing, did a vacuum on the db and it reduced it to 50Mb, I then copied it over to my running Dude data folder and when I brought the service back online it expanded the db back up to 1.9Gb!! Can anyone @ Mikrotik clarify that the db will always try to run at full size and fill in the white space as it continues to commit data? If this is the case can anyone also tell me what the optimum "Keep" values for Raw, 10min, 2hour and 1day intervals are, as I get the feeling the "approximate size required" is not close to what it thinks it needs. As I originally raised my Raw data keep duration to 7d which caused the db to hit its limit.