BT

InfoQ Homepage News MySQL Changes: More Expensive and No InnoDB for the Classic Edition

MySQL Changes: More Expensive and No InnoDB for the Classic Edition

Bookmarks

Oracle has published a new comparison table for the MySQL Editions offered with support. Major changes include a rise of the price and InnoDB is removed from the Classic Edition.

Previous prices for the Enterprise edition of MySQL as offered by Sun a year ago ranged from $599* to $4,999* per server per year. Oracle is currently offering four editions: Classic, Standard, Enterprise, and Cluster Carrier Grade. Standard, Enterprise and Cluster come with support at prices starting at $2,000 for a server with 1-4 sockets/year, and going up to $5,000 and $10,000. A socket is basically a processor that can have multiple cores. Prices for servers with more than 5 sockets  are not disclosed.

The price for Classic is also not disclosed, those interested being directed to contact the MySQL Embedded Sales Team. Classic is available only for “ISVs, OEMs and VARs to license as an embedded database”, and it no longer contains the InnoDB transactional storage engine. InnoDB was created and it is developed by Innobase Oy, a company acquired by Oracle back in 2005, so practically it belongs to Oracle.

According to a tweet posted by MySQL, the free MySQL Community Edition is still available with InnoDB:

MySQL/InnoDB still available for download under the GPL from http://mysql.com/download/ and http://dev.mysql.com/ - no change here.

While the Community Edition is untouched by the latest price changes, a question can be asked: “Is Oracle going to continue to invest in the GPL version of MySQL, keeping it a viable option, or will everybody have to choose a paid edition or move to another database?” 

Rate this Article

Adoption
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • I moved to PostgreSQL

    by Davi Tavares /

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I've decided to move to PGSQL, two years ago....

  • Move away

    by Oyku Gencay /

    Your message is awaiting moderation. Thank you for participating in the discussion.

    No matter how much you love MySQL, it is time to move away...

  • Re: Move away

    by Vladimir Vlach /

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I agree. We are slowly moving to something else. Perhaps NoSQL where possible. Can't predict future and things are not looking good.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.