Should I use HSQL or another DBMS like SQLserver?
18 October, 2010
Hi,
I just installed Yellowfin with the HSQL database, as I was testing the application.
I have now deciced to purchase the software and was thinking of benefits using HSQL against other DBMS. It was easy to install and just thought if it is just as good as SQLserver or Oracle then I wouldn't have to re-install Yellowfin etc..
Can you give me some information on the 'pros' & 'cons' of HSQL?
Thanks
I just installed Yellowfin with the HSQL database, as I was testing the application.
I have now deciced to purchase the software and was thinking of benefits using HSQL against other DBMS. It was easy to install and just thought if it is just as good as SQLserver or Oracle then I wouldn't have to re-install Yellowfin etc..
Can you give me some information on the 'pros' & 'cons' of HSQL?
Thanks
The HSQL db is generally only used for evaluating the software, or for a POC, it?s not recommended in a production environment.
HSQL doesn?t have a GUI for backing up/restoring etc, so it makes it difficult to maintain the DB.
In terms of performance, it can be extremely fast, though tends to get pretty slow with larger databases.
We wouldn?t say it?s very robust or scalable. It may be fine for a few users, though having multiple simultaneous transactions will decrease the performance and may even cause data corruption.
If you do experience database corruption, there is no easy way to resolve this, and a database restore will mostly likely need to be done.
As you can see, the ?cons? far out way the ?pros? comparing HSQL against other DBMSs.
HSQL is easy to install with Yellowfin, and may even be a little faster in some cases, but lacks many other areas like robustness, scalability & usability.
Using a full-fledged DBMS like Oracle/SQLserver is highly recommended.
HSQL doesn?t have a GUI for backing up/restoring etc, so it makes it difficult to maintain the DB.
In terms of performance, it can be extremely fast, though tends to get pretty slow with larger databases.
We wouldn?t say it?s very robust or scalable. It may be fine for a few users, though having multiple simultaneous transactions will decrease the performance and may even cause data corruption.
If you do experience database corruption, there is no easy way to resolve this, and a database restore will mostly likely need to be done.
As you can see, the ?cons? far out way the ?pros? comparing HSQL against other DBMSs.
HSQL is easy to install with Yellowfin, and may even be a little faster in some cases, but lacks many other areas like robustness, scalability & usability.
Using a full-fledged DBMS like Oracle/SQLserver is highly recommended.
I was thinking since i have already got it installed, I could move my HSQL database into a more common DBMS ?
We haven?t dealt with anyone wanting to migrate the HSQL database to another DBMS.
We simply suggest re-install of Yellowfin and point to their production database.
Though if you did want to try and migrate the database, there are many articles on migrating to MySQL, once you have the database in MySQL you can migrate to another DBMS.
I did manage to find this article which may be useful to you:
http://wiki.alfresco.com/wiki/Migrating_from_HSQL
We simply suggest re-install of Yellowfin and point to their production database.
Though if you did want to try and migrate the database, there are many articles on migrating to MySQL, once you have the database in MySQL you can migrate to another DBMS.
I did manage to find this article which may be useful to you:
http://wiki.alfresco.com/wiki/Migrating_from_HSQL