Hello. I can't reproduce such issue with SCRIPT, SCRIPT TO, or BACKUP commands with large database and different settings. May be your database schema contains something special. You can try to create a some standalone test case for this issue and share it with us.
H2 had a long-standing problem if you use queries with a lot of rows in result (more than 40,000 rows per gigabyte of maximum Java heap size by default). Such results are buffered into database. This problem is less noticeable in PageStore mode, but in MVStore mode database size may be 10 or more times larger that expected. LAZY_QUERY_EXECUTION may help and may not help depending on queries. This problem was resolved recently for MVStore mode, you can build database for yourself from the current sources available on GitHub and test it. https://github.com/h2database/h2database You need a jar target: http://www.h2database.com/html/build.html#building There are other problems with database size, but they all are also specific to some usages of database, so without a test case it's not easy to say what happens in your situation. Also you can continue to use PageStore backend, it is still supported. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
