October 4, 2007

SAP takes back MaxDB from MySQL

Way back in January, 2006, I wrote that MaxDB was not getting merged into MySQL. Given that, it makes sense for SAP to take back control of the product. As The Reg reports, that’s exactly what’s happening.

The bigger question is — how’s MySQL’s SAP certification coming along? Whether or not MySQL gets SAP-certified and included in the SAP product catalog will be a huge indicator of whether it’s ready for OLTP prime time.

Anybody want to place bets on which midrange OLTP DBMS gets certified for SAP first, MySQL or EnterpriseDB? MySQL has a large head start, but if my clients at EnterpriseDB have their priorities straight, they might wind up lapping MySQL even so.


4 Responses to “SAP takes back MaxDB from MySQL”

  1. pabloj on October 4th, 2007 4:14 am

    MySQL is still a joke in the real OLTP market, EnterpriseDB is shurely closer to prime time, but the real question is if there’s a demand for this? It could be a move by SAP against Oracle but a difficult one as SAPDB has never been a contender in this field

  2. Curt Monash on October 4th, 2007 5:13 am

    I think there are actually a lot of MaxDB installations out there running SAP apps.

    How many NEW ones there are is perhaps a different matter.

    As for MySQL in hardcore OLTP — MySQL 4 was an absurdity. MySQL 5 fills most of the important checkboxes, however, so now it’s a question of implementation, maturity, smoothing of rough edges, etc.

  3. LewisC on October 4th, 2007 12:50 pm

    Interesting thoughts. I’m sure EnterpriseDB is pursuing the certification if SAP is willing to work with them. They are pretty proactive that way.

    Falcon (MySQL 6) is looking pretty good though. Even 5.2 is adding some additional enterprise requested features (like partitioning).

    It’ll be interesting to see how this turns out.


  4. SecretSQL on October 5th, 2007 7:02 am

    I don’t think MySQL ever cared much for SAP-DB/MaxDB. They probably got some cash out of the deal, then purposely neglected it. Speaking to senior guys from MySQL, they did not seem that interested in MaxDB. Speaking to senior guys from SAP, I know the MaxDB developers were not too happy about the arrangement either.

    SAP-DB/MaxDB was far ahead of other open source databases in terms of performance and stability a number of years ago. MySQL and PostgreSQL (in particular) have caught up. SAP had a chance to make an impact here, but that window is closing.

    At this point, their original thought of getting out of the database market probably makes sense, though working with MySQL was not a good choice. Of the other open source databases, PostgreSQL is the best option. The license gives them flexibility, and they can partner with a company like EnterpriseDB, with whom they share a common enemy: Oracle.

Leave a Reply

Feed: DBMS (database management system), DW (data warehousing), BI (business intelligence), and analytics technology Subscribe to the Monash Research feed via RSS or email:


Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.