SQL database choice

[Ramón Retamar]

Hi.
The dcm4che works with Firebird, MYSQL and PosgreSQL. Them what is the most appropriate for use iwth dcm4chee for a large database ?.

Thanks
Ramón

[Rady]

Hi,

Technically speaking there could very little difference between the three database engines you have mentioned. Take a look at this link. 

My recommendation are as follows...

1. MySQL widely used across and among the three it is most popularly used and is ranked as No 2. We have used MySQL/DCM4Chee for over million studies/images and have no problem. Works on various platforms, Windows, Mac, Linux. 

2. PosGreSQL, when you need low foot print compared to MySQL this could be an option. Takes Lesser Memory and equally robust. 

3. FireBird, Inherited from Interbase from Borland products - very robust engine. From Popularity point of view could be the least among your list. I have not used it but have a good review on the internet. 

Hope this helps...

with regards

Rady

[Ramón Retamar]

Firebird SQL Server is a good choice ? In theory is more robust than MYSQL.

[Suresh Viswanathan]

For large installations I would recommend PostgreSQL. I've used it successfully in several large commercial installations without any issues till date. 

What is your definition of large?

Suresh

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at http://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

[Alvaro [Andor]]

Hola Ramón,

Both are very professional and capable database engines.

MySQL is more popular or common, specially on OpenSource projects. Maybe simpler or easier to begin with.
PostgreSQL is more ACID compliant, has more 'enterprise features' and maybe is more similar to Oracle.

It would be nice if you define what is a 'large database' for you but, frankly, I would chose the one you are more familiar with, or you get the better DBA for it, 'cos chances are you're going to need to fix a failure one day, or maybe make and restore backups and so on...

Thanks.