The Bottom Line: By committing itself to the functionality of MySQL and MaxDB in future releases, MySQL is letting customers choose between the two on their merits without fearing that either product will be abandoned.
What It Means: SAP and MySQL formed a cross-licensing partnership a year ago to develop a new open source database targeting SAP and non-SAP customers. SAP conveyed rights to its own database, SAP DB, rebranding it MaxDB to get the initiative going. SAP retains ownership over SAP DB, but MySQL has the right to develop and sell improved versions of MaxDB. SAP currently certifies MaxDB for use in R/3 and other SAP applications. But now, some of the issues raised by the move get resolved.
Lingering questions about MySQL’s products are answered
MySQL and MaxDB have fairly complementary profiles. MySQL focuses on performance, stability, and ease of use and administration through a simple interface, while MaxDB provides advanced features more representative of enterprise-grade databases.
The Takeaway: Until now, whether MySQL would maintain MySQL and MaxDB as separate products, tailored for different needs, or whether it would integrate the two into a single product was an open question.
MySQL sets its sights on R/3
As MySQL aims to fuse the functionality of the two databases, it plans to retain the performance and stability of MySQL while adding the advanced functionality of MaxDB. Instead of undertaking a raw merger of the two codebases, MySQL’s three-phase roadmap was drafted to capitalize on concepts from the two products to develop an integrated codebase.
Here are the three phases:
SAP is committed to MySQL
Several signs point to SAP’s commitment to the MySQL product line:
Recommendations: Although MySQL and MaxDB currently have distinct characteristics, some companies using the products and Independent Software Vendors (ISVs) may find their basic requirements met by either. For those on the fence, we recommend MySQL over MaxDB, since it will change the least in the near term and will probably guide the user experience of the upcoming integrated product. However, those needing the advanced functionality of MaxDB shouldn’t hesitate, since MySQL is committed to ensuring that functionality available today will not disappear.
AMR Research originally published this article on 21 May 2004.