Hi, So the initial database is about 10 times smaller than the database with around 6 days of data. However, as far as I understand your use case, the database should be the same size, right? Could you run SCRIPT TO 'fileName' at the first day and after 6 days, and post the file sizes of the script?
The fill ratio of the pages is a bit better at the beginning, however it looks like the database just contains more data (more rows or larger rows) after 6 days (around 400 MB instead of 52 MB). I wonder how this can happen. So far I can't reproduce the problem. It would be great to have a reproducible test case! In any case, it sounds like it would be a nice feature to run defragment at runtime, possibly in a background thread. I will add a feature request for this (but I will not implement it right now). I think in your case it's a different problem, and defragmenting the database is / would be just a temporary solution. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
