Hello Darrell, all, this is a question which cannot be answered completely IMO. Also, as people's backgrounds differ, I may fail to find words which you understand the way I meant them - please take this into account.
Am Do, den 10.03.2005 schrieb Darrell A. Sullivan, II um 17:17: > Hello, > > I am planning to port some systems that are currently using proprietary > database management to an SQL environment. > > In looking at the MySQL web site it appears that they have two different SQL > database servers. I am trying > to determine how to choose between the two. [[...]] Yes, these are distinct products: Both are DBMSs which "speak" SQL, but coming from separate code bases they have different properties / features and were (originally) targeted at different environments. > > Can anyone tell me what the practical day-to-day differences between the two > products would be? MaxDB was targeted at the enterprise market from the start, with trained administrators, pre-planning of capacity, regular backups etc, whereas MySQL originally targeted fast application development, integration into Web servers, and embedding into applications. MySQL is now adding features which are essential for the enterprise market, whereas MaxDB is getting integrated into PHP etc. Still, both systems have their history and maybe never will be really "similar". > > I looked at the documentation page that listed the differences between the > two and it basically seemed > as though MySQL was playing cath-up to MaxDB. In the sense that MaxDB already has some SQL features which MySQL is currently (or will be) adding, you are right. It is for you to check and decide how urgently you need these. Do not use older DBMS comparisons based on the status of MySQL 4.0 (or even 3.23), for any new setup you should take 4.1 (production) or even 5.0 (test, development - still "alpha" status). OTOH, MySQL has some properties that MaxDB does not have and IMO never will have - let me list just these: - different table handlers to choose from - the myisam table handler is extremely fast (no logging) and optimised for read-mostly situations - the multiple-version properties of InnoDB - various character sets and collation sequences, settable at DB, table, and even column level - replication (a former version of MaxDB offered distribution, and that was removed intentionally) > However, considering how many > people > use MySQL there must be some driving reason behind that choice. I tried to give these above. The choice is for you to make. Regards, Jörg -- Joerg Bruehe, Senior Production Engineer MySQL AB, www.mysql.com Office: (+49 30) 417 01 487 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
