There's a big Open Source (MySQL) v commercial (Oracle) debate. Here are some interesting facts behind the mask.
The financial decision should be based on TCO (Total cost of ownership) rather than on license fees. It's always nice to get "something for nothing" but newcomers fear that they'll spend more in the long term on supporting a product that's open source, and there are a number of scary rumours around.
Typically, licensing fees on a commercial product account for some 25% to 35% of the total cost of ownership. So the license fee in a MySQL v Oracle decision is not as vital as you might think. However, TCO for a MySQL system tends to be anywhere from 75% to 90% less than the Oracle equivalent. I have no proof of these figures, but I can believe them because of
THE EASE OF INSTALLING MYSQL
THE EASE OF MAINTAINING MYSQL
THE LOWER DBA COSTS (TRAINING, SALARY, NUMBER OF STAFF)
In justification of a commercial route, conservative buyers often talk about responsibility for code and support - if you want that, you can buy a commercial license for your MySQL. At the top of this market, a 24x7 contract with a 1 hour response time will cost you $50k per year, or if you pay $250k you'll get that plus your own assigned engineer who knows your setup in great detail and can be reached at any time by pager. Regular visits, etc. ... this isn't the sort of thing the typical customer needs, but it's something that the big NYSE companies require where their systems are trading billions.
Licenses available are
ELA Enterprise License Agreement
VAR Value Added Reseller
OEM Typically an integrator who includes MySQL in commercial product
EULA End User License Agreement
GPL Open Source License
Typically, the GPL works fine for most end users, but it's largely untested in courts or law and if lawyers get involved with bigger companies, they typically prefer to go for the EULA even though it costs.
The general answer to the question "do I need to buy a license" is - if you're for free, then it's free. If you are using it in your proprietary system, then you need a commercial license
See also
SQL and MySQL training courses
Please note that articles in this section of our
web site were current and correct to the best of our ability when published,
but by the nature of our business may go out of date quite quickly. The
quoting of a price, contract term or any other information in this area of
our website is NOT an offer to supply now on those terms - please check
back via
our main web site
Introduction to SQL and MySQL [84] - ()
[85] - ()
[175] - ()
[382] - ()
[444] - ()
[515] - ()
[591] - ()
[691] - ()
[918] - ()
[924] - ()
[2134] - ()
[2561] - ()
[2567] - ()
[2786] - ()
[3269] - ()
[3928] - ()
Sourcing, Running and Configuring MySQL [192] - ()
[334] - ()
[489] - ()
[515] - ()
[535] - ()
[591] - ()
[907] - ()
[1095] - ()
[1123] - ()
[1131] - ()
[1689] - ()
[1731] - ()
[1771] - ()
[1935] - ()
[2085] - ()
[2209] - ()
[2426] - ()
[2444] - ()
[2445] - ()
[2458] - ()
[4390] - ()
[4406] - ()
[4487] - ()
resource index - MySQL
Solutions centre home page
You'll find shorter technical items at
The Horse's Mouth and
delegate's questions answered at
the
Opentalk forum.
At Well House Consultants, we provide
training courses on
subjects such as Ruby, Lua, Perl, Python, Linux, C, C++,
Tcl/Tk, Tomcat, PHP and MySQL. We're asked (and answer)
many questions, and answers to those which are of general
interest are published in this area of our site.