January 26, 2006
SAP, MaxDB, and MySQL, updated
I’ve had a chance to clarify and correct my understanding of the relationship between SAP, MaxDB, and MySQL. The story is this:
- MySQL has the right to sell MaxDB, but apparently isn’t focusing much on that.
- The MySQL and MaxDB code lines are NOT merging, for technical reasons. For example, the older MaxDB does a lot of its own thread management, while MySQL relies on the operating system for that.
- When SAP thinks a DBMS is capable of running SAP’s apps, it adds the DBMS to its product catalog and resells it. Yes, even Oracle. That’s why all my discussions with SAP of MySQL’s enterprise-readiness quickly come back to an exhaustive multi-year certification process.
- My personal best guess as to when MySQL will be in SAP’s product catalog is 1 1/2 – 3 years from now.
And by the way, MaxDB’s share in SAP’s user base is about the same as DB2’s (at least DB2 for open systems). MaxDB is being aggressively supported, and nobody should get any ideas to the contrary!
Comments
6 Responses to “SAP, MaxDB, and MySQL, updated”
Leave a Reply
[…] With Oracle acquiring first Innobase and now Sleepycat, MySQL has been under the gun to position itself more sharply. In response, their CEO reportedly disclaimed interest in the ERP market. That surprises me, as it contradicts what I hear from SAP, and have heard from the company in the past. […]
[…] As I’ve previously noted, the expectation is that MySQL will wind up getting share in SAP’s customer base. At least, the expectation is that their technology will be good enough to do so. The business reasons for SAP to favor this outcome are of course pretty obvious. Almost the only remaining question is whether SAP will back MySQL with great force, or whether it will divide its love between MySQL and its own inhouse DBMS product MaxDB. • • • […]
SAP has ended their relationship with MySQL as of Nov. 2007. This has been a big disappointment for our client. Instead of paying MAXDB database as needed for each production database instance, SAP is now requiring them to pay the full 3% fee of SAP licensing to use MAXDB.
Thomas Pham
http://www.pandainc.net
Thomas,
How much money are we talking about? And how does the price compare to that of Oracle or DB2 or other DBMS that can be bought off of SAP’s price list?
Thanks!
CAM
[…] 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, […]
[…] MaxDB has been a low-cost DBMS option underneath SAP for a very long time. […]