According to a letter republished in The Register, Oracle is dropping their Basic and Silver level support for MySQL. Not much is really lost; at the basic level you don’t get much more than a couple of support incidents per year, while silver adds some basic monitoring tools. The stuff people normally associate with production-grade databases such as performance monitoring isn’t available until you hit the gold level at $2,999 per server per year. For the full set of tools you can expect to pay $4,999 per server per year.
Keep in mind that these are prices inherited from Sun. There is speculation that prices will be increased so that they are comparable to Oracle’s Berkeley Database line. The transactional version of Berkeley DB is currently going for $5,800 per processor, while the “High Availability” version will set you back $9,800 per processor. With some exceptions, Oracle considers a “processor” to be a single or dual-core chip. On the other hand, one could always stick to the free version of MySQL and find tools from one of the many third-party vendors.
Meanwhile IBM has recently cut the price of its entry level database by half. Like all major vendors, DB2 comes in a free “express” edition. Their version, DB2 Express-C, supports 2 GB of RAM and 2 cores. For an extra $1,500 per year you can upgrade to the “DB2 Express Fixed Term License” version. This doubles the cores/RAM allowed and adds features expected in production environments such as active-passive clusters, replication, and backup compression. Also included in the paid version are the Optim Development Studio and Optim Database Administrator products.
/filters:no_upscale()/sponsorship/topic/c1372aee-0449-48ce-bab0-1b645fe8025e/QConLonndonLogoRSB-1667564544484.png)
/articles/oracle-to-mysql-aws-database-migration-service/en/smallimage/logo-1662492103321.jpg){kind=logo}
/articles/Dotnet-Seven-MSMQ-Alternatives/en/smallimage/logo-1670585778128.jpg){kind=logo}
/articles/polygot-microservices-dapr-aks/en/smallimage/logo-1666079703389.jpg){kind=logo}
/articles/dotnet-trends-2022/en/smallimage/InfoQ-Trends-Report-1663778620252.jpeg)
/minibooks/2022-infoq-trends-reports/en/smallimage/LOGO-1672051527011.jpg){kind=logo}
/presentations/jfr-observability/en/smallimage/qcon-plus-s-1674841495350.jpeg)
/articles/secure-kafka-cluster-strimzi/en/smallimage/securing-a-kafka-cluster-in-kubernetes-using-strimzi-small-1671647644310.jpg)
/articles/graalvm-java-compilers-openjdk/en/smallimage/small-image-jdk-2023-1671096273181.jpg)
/articles/java-jvm-trends-2022/en/smallimage/InfoQ-Trends-Report-small-1670863712433.jpeg)
/presentations/java-shared-memory-files/en/smallimage/peter-lawrey-s-1669107216422.jpg)
/articles/josh-long-spring-6/en/smallimage/logo-1669141674434.jpg){kind=logo}
/presentations/devops-java-devs/en/smallimage/Ix-chel Ruiz-s-1669107288266.jpg)
/presentations/java-upgrade-path/en/smallimage/Andrzej Grzesik-s-1667476313077.jpg)
/presentations/log4shell-security/en/smallimage/Simon-maple-s-1665986617483.jpg)
/presentations/loom-java-concurrency/en/smallimage/Tomasz Nurkiewicz-s-1665739004716.jpg)
/presentations/jit-aot-tradeoffs/en/smallimage/qcon-plus-s-1665738630666.jpeg)
/articles/shift-left-api-standardization/en/smallimage/GettyImages-1059510610-1664896147152.jpg)
/articles/strimzi-the-gitops-way/en/smallimage/strimzi-gitops-small-logo-1664297048552.jpg){kind=logo}
/articles/java-virtual-threads/en/smallimage/logo-1663737114685.jpg){kind=logo}
/presentations/jit-optimize-decompile-shopify/en/smallimage/chris-seaton-s-1661502009546.jpg)
/articles/james-ward-java-jvm-languages/en/smallimage/james-ward-on-the-state-of-java-and-JVM-languages-small-1661766435546.jpg)
/presentations/java-performance-tornadovm/en/smallimage/juan-fumero-s-1661160969043.jpg)
Community comments
I could be mistaken
by peter lin,
Re: I could be mistaken
by Diego Visentin,
Re: I could be mistaken
by hong l,
Re: I could be mistaken
by Leon Katsnelson,
I could be mistaken
by peter lin,
Your message is awaiting moderation. Thank you for participating in the discussion.
I thought DB2 express C was only meant for development purposes and isn't really meant for production. I'm sure there are people who deploy DB2 express c in production, but it's not officially recommended. IBM would prefer you buy a full DB2 license for production.
Re: I could be mistaken
by Diego Visentin,
Your message is awaiting moderation. Thank you for participating in the discussion.
You can use DB2 Express-C in production environment:
"Q:Are there any limitations such as number of instances installed per server or database size prohibiting full use of DB2 Express-C in production environment?
A:Unlike other free databases, DB2 Express-C does not impose any artificial limitation. There is no database size limit, no limit on the number of instances or databases per server and no restriction on the number of users."
For more info:
www.ibm.com/developerworks/wikis/display/DB2/DB...
www-01.ibm.com/software/data/db2/express/
PS: DB2 Express-C already runs on Amazon Cloud and it's in beta for MacOSX
Re: I could be mistaken
by hong l,
Your message is awaiting moderation. Thank you for participating in the discussion.
When talking about the Mac meta, I am really feel pity the Mac version is tricky to install and hard to use - especially the command line tools. For contrary, MySQL for mac is very easy to install and use.
Re: I could be mistaken
by Leon Katsnelson,
Your message is awaiting moderation. Thank you for participating in the discussion.
DB2 Express-C can be used for anything you want to do with it without any restrictions. You can use it in development, production and even redistribute it as part of your application without pesky GPL viral issues and without paying any royalties to IBM. And there are no restrictions on the size of the databases, number of users, number of databases etc. Read more at freedb2.com/2010/10/05/comparing-free-databases...