Hello, I was wondering whether it is possible to force H2 to create smaller DB files. I understand this would happen at the cost of performance but perhaps the cost would not be that big. I found SHUTDOWN COMPACT but that is a little too late.. DB already has 15GB (where SQLAnywhere with exactly the same schema and data is just around 700MB). 7z brings the DB file down to 500MB but that takes several hours and very long to extract as well...
So the questions I guess are - is this size ratio compared to SQLAnywhere expected? I mean the size difference is more than 20:1 - are there any settings I could use to connect to DB in some "compact" mode where DML would result in limited growth of DB file? I was thinking that perhaps the process pre-populating the DB would run slower and produce small DB file. The app which uses the DB later on would benefit from H2 performance and start with smaller DB file then - are there some recommendations as how to insert data to DB to limit DB file growth? I can think of factors like order of data, number of tables in a transaction, commit frequency (after every row vs once in a while). Perhaps there are other? - I briefly experimented with SHUTDOWN COMPACT where it failed for me. I will give it a shot again along with the re-build of DB described in http://www.h2database.com/html/features.html#compacting and post my results here later on thanks Tono -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
