PostgreSQL To Benefit From MySQL Price Hikes?

Oracle Up The Price of MySQL?

Jessica Thornsby

Oracle customers receive letters warning of imminent price increase.

According to a report by PostgreSQL support provider Command Prompt, Oracle’s MySQL customers might be about to pay a whole lot more for licensing. Not only has the support pricing for MySQL disappeared from the Oracle website, but Oracle have begun sending letters to current clients warning them to expect some changes in MySQL’s pricing.

“We have not had a price increase for over 6 years but there will be an increase in the next price list that will be available soon. We’ve been expecting the increase for the past couple of months but I’m told it the new price list will be released soon,” reads the alleged letter. It then goes on to explain that Basic and Silver support will no longer be available, although existing Basic and Silver customers will have the option of signing up for a multi-year agreement, which will entitle them to keep using these support packages for “up to” another three years. A Basic license is currently priced at £369, and a Silver license at £1249. However, if these two options are removed, customers will be left with paying either £1849 for Gold or £3099 for Platinum license. On the positive side, the letter does promise a discount of up to 30% for a three year pre-paid subscription.

Although no exact details regarding pricing are available at the moment, Joshua Drake at Command Prompt argues that the pricing for Oracle’s BerkeleyDB is a good indication of the sort of prices MySQL customers can expect to pay. This has led him to conclude that a quad core machine could cost a MySQL customer 11,600.00-23,200.00 per year.

Some are already speculating that the price hikes could benefit open source database alternative PostgreSQL, with Joshua Drake pitching PostgreSQL at the end of his report: “moving to PostgreSQL with support from a long standing, transparent support and pricing schedule can do nothing but benefit you in the future.”

Inline Feedbacks
View all comments