Thomas & H2 team, As with all the other posters, I share the same respect and impression of the H2 database. Fantastic to get all of this out of roughly a megabyte jar.
I am working on a project for the US Coast Guard. We are setting up a Java-based enterprise service bus. The demands for a database that helps the ESB run are high; we need 99.999% up-time, and we need it to be able to handle thousands of inserts per second. We love the performance of H2 in these regards, but we've hit a major obstacle. The current compaction method (SCRIPT) is not really acceptable for us, due to our uptime requirements (it also is hard to work in the context of a trigger, but that's another matter). It appears that it takes the database offline, and as often as we would have to do it to maintain performance, that would be too much downtime. I thought about clustering - just taking down and re- clustering one of the servers will achieve the same thing as the current compact method, I think, but our distributed computing model means that we would have one application and two databases running on the same server at that point - not ideal. I've seen in previous posts that you are working on a built-in compaction method. Is that something you anticipate for the next release? Or is it more of a long-term kind of goal? Thanks and keep up the great work! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
