aspose file tools*
The moose likes JDBC and the fly likes MySQL or HSQL ?? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "MySQL or HSQL ??" Watch "MySQL or HSQL ??" New topic
Author

MySQL or HSQL ??

Vikas Solegaonkar
Greenhorn

Joined: Oct 17, 2011
Posts: 8

Need an advice from all the experts out there!

I am working on a client server based application - that needs to accumulate data over time ~ 100 MB per month. Do not foresee any cleanup of the data - it will just accumulate, and only the latest data will be used more frequently, older data would be required only occasionally. I am not able to decide which database should be good for such an application? Traditional MySQL? Or the Java based ones like HSQL / H2 / Derby?

I checked out many discussions on the related topics that discarded H2 and Derby as not up to the mark - leaving me with MySQL and HSQL. For these, I found a lot of contradictory points - some say that MySQL is sturdy and has a lot more capacity while others promise HSQL is a lot more fast and sleek - easy to package and deploy, etc. Some crib about HSQL hogging RAM.

Basically I am confused if my requirement of 100 MB per month classifies as huge data or small? How bad is the HSQL Ram usage? Is there a way to neatly package MySQL with an application? Or make HSQL digest more data? Is there any other criteria to decide? Or any other alternative?

Do let me know your views
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: MySQL or HSQL ??
 
Similar Threads
Tomcat & Memory
A Bit Of Guidance Please
Issues around unit testing MySQL DAO code using HSQLDB.
I'd like to host an application (Java)...
Choosing Database to a Java Swing Standalone Application