I see a lot of talk about database size on this list, but seriously, how often do you really use a 256GB database ? There are millions of applications that require far smaller database solutions, and this is where H2 beats the competition. If you are looking at a DB of that magnitude, go for a clustered solution. If, however, you want to kick MySQL's hiney for real-world business applications, go for H2.
The new Java-based Mobilisr project (an Aids messaging initiative developed by Cell-Life in South Africa) project would not have happened if it were not for the H2 database. We had serious performance issues with MySQL, especially inserting thousands of new records into a database from a CSV file. The lead developer flipped head of heels when I showed him the H2 database and the fantastic responses I got from the embedded DB. We went from 40 minutes for the import to under 40 seconds for the same data! The embedded nature of H2 (on Tomcat) meant that all communication was in the same VM, making it blazingly fast and easy as pie to administrate. Give H2 a decent try, especially in a servlet container like Tomcat, you will be surprised at how well it works. If you really need a 256gb or larger database, consider running two H2 sessions, possibly on seperate servers. Explore H2, it's full of awesomeness :) Regards Ewald --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
