Oracle DB Vs MySQL for Enterprise DataBase Deployments

Oracle DB is big, and expensive, but it brings a lot to the "table" when compared with MySQL.

MySQL has limited ability to audit.

MySQL's security is unsophisticated. There are no groups or roles, no ability to deny a privilege (you can only grant privileges). A user who logs in with the same username and password from different network addresses may be treated as a completely separate user. There is no built-in encryption comparable to Oracle.

MySQL's Authentication is built-in. There is no LDAP, Active Directory, or other external authentication capability.

MySQL has no MPP (massively parallel processing ) support.

Unlike Oracle MySQL has no fractional-second storage type for times, dates, or intervals.

There is no RAC (Real Application Cluster) support in My SQL, and no failover or server promotion either. These are strong features in Oracle

MySQL's number of joins per query is limited to 61. Oracle's limit is much larger.

MySQL Replication is asynchronous and has many limitations and edge cases. For example, it is single-threaded, so a powerful slave can find it hard to replicate fast enough to keep up with a less powerful master.

---

Closed Caption:

oracle DB vs my ask you out
a friend of mine recently published an
article about why mysql is the right
choice if you're doing development of a
web platform and that you have to be
nuts to use oracle DB i pointed out to
this friend there are a lot of cases in
which it actually makes a lot of sense
to use oracle DB for your web platform
but just in general
oracle has some advantages / mysql i use
mysql for a lot of things hours my
wordpress sites a lot of the custom dead
work that I do is build on mysql so I'm
by no means an Oracle fanboy just an
objective observer there are a lot of
things that buying oracle gets you one
of the first and most important is
auditing mysql has very limited
functions and auditing and auditing is
important if you need to guarantee that
the transactions that you tempted to
write to the database actually happen
auditing provides a trailed did that
allows you to determine the differences
between what's in the database and
what's supposed to be the database
without this you can't do some of the
recovery you can't guarantee that the
data is always accurate and you can't do
some of the other checking against
native is to make sure that everything
that happened and all the data that's
there should be or the database has been
tampered with the security and my sequel
is pretty unsophisticated you're only
able to use the built-in security that
comes with mysql it doesn't have
connected services for LDAP or Active
Directory services without these
functions is much harder to manage an
enterprise-level database with lots of
users while a web application mostly is
going to receive rights from a single
user the program as it were active
directory services in oracle allow you
to set such rules as this is a person in
accounting
they have access to all the accounting
databases and queries that wrong and
Jen's accounting database
this person is in engineering and has
access to engineering databases but does
not have access to accounting and
because you can use the groups that you
set up in active directory services when
HR hires a new accountant they just
automatically have access to that
particular database and the audit trail
will show you which specific user wrote
something to the database so you can see
where something broke and how to fix it
based on the transaction look
scalability is also an issue with mysql
and people have argued that mysql 5.5
makes my sequel as scalable is any other
platform but the truth is that there is
no support for MPP or massively parallel
processing in mysql so while you can
scale certain types of transactional
bits of database interaction large
amounts of computational actions cannot
be easily scaled if for example you have
a query that needs to go through and
update everybody with seven percent
interest or needs to do a large
calculation for searching authority
because you're building a who has the
most authority in a tiered search system
and you need to say this person has the
most contacts and after you get to the
end the next thing you need to do is go
back to the beginning and say based on
the values that everybody has what is
the new value but they have much like
what Google we do with their search
engine you can't build those things
easily on a mysql because the
scalability of the processing is not
there
mysql also is missing
fractional second transactions you can
store a timestamp in the log for an
entry that says this new entry was
created and here's the time or here's
the last modified but it's only accurate
to the same
and not to fractional seconds this
starts be an issue if you're doing
things like world of warcraft databases
or if you are doing bank transactions
and it could in fact matter whether or
not you deposited a item before you
removed an item or for detecting
duplicate items based on time stamps for
when things happened
one of the biggest features of oracle is
a thing called Rach real application
clusters and it does more than just
scale it manages failover when a server
dies rack allows you say automatically
promote a new server to be the master
and find some other server to be a slave
or take all the load that was on this
server and transferred to another server
as a result article databases are very
fault-tolerant you can lose several
servers in cluster and everything will
stay up and make it a little slower but
it will in fact stay up with mysql you
don't have that automatic failover so if
you lose a master the slave will not
automatically step up and replace it and
it wont prior tries the types of queries
that are being run against for the
processes that are being run in order to
make the entire system stay up you may
lose partial functionality rather than
just degrade the overall performance
there are some other differences between
mysql and oracle that are more about
programming the necessarily scale of the
infrastructure one of those is that
mysql only support 61 joins and oracle
support over 200 joins in a single query
as someone who works in my and Google's
data store gql I'm used to working with
no joints at all so as a developer I've
learned to get around using joints but
there are definitely times when using
enjoying to take
information from several queries and
combine it becomes critical and this is
one of the places that oracle really
excels is that the complex queries can
be executed and the built-in
optimizations that Oracle uses in order
to make those queries take his few
cycles as possible and perform as
quickly as possible means that it's
easier for the developer to create
well-performing queries without having
to test hundreds of possible
combinations of ways to run that query
lastly is replication mysql has some of
the worst replication ever many of the
databases that are out there the
replication service is single threaded
and so if you've got 200 cords running
in your main database replication is
pretty much impossible because the
replication is going to go through a
single threat so if you're doing a large
number of Rights transactions the
replication server is not going to be
able to keep up with those transactions
ever and you're going to have to have
scheduled downtime or offset those or
you're going to have to come up with a
different method for doing replication
and there's no snapshotting in mysql you
can't just snap shot something and say
is replicated as of this time it's truly
is a this is you know always running in
the chase mode and if you have to catch
up you have to catch up it just it
doesn't really work well or scale or
failover as well as oracle does you're
not doing mission-critical hundred
percent of time stuff
mysql is great and it doesn't cost
anything which is a huge advantage over
oracle it doesn't require specialized
hardware the way oracle does for scaling
but overall oracle is much more
enterprise solution and has a lot more
thought process put into how it's been
developed and addressing administration
issue
scale issues and usability issues