This is the second blog post in a series designed to assist companies who wish to migrate their code from Oracle to MySQL.

In the first post of the series I tried to explain why you would like your web platform to run on a MySQL database, and not on an Oracle database. In this post, I’ll try to focus on the changes that you need to plan for when migrating from an Oracle environment.

Code

Probably the most obvious change is in code. There is no way around it – you’ll have to change your code.

1. SQL statements.
   While ANSI SQL 92 is a standard, Oracle offers extensions to the spec – and those are used by most developers, sometimes without their being aware of it.
   Of course, when moving to MySQL, those SQL statements will need to change. Some will require only minor …

Here are the slides to my first talk at Percona Live UK 2011: Choosing a MySQL High Availability solution.1

1. 1. See this for a review of the conference as a whole: http://openlife.cc/blogs/2011/october/thanks-percona-and-attendees-great-percona-live-uk-2011

read more

Linux, Apache, MySQL and PHP — altogether they mean LAMP. I’m not talking about watts and bulbs.

And if you desire is for a comprehensive, robust server, your IT infrastructure has to include all of these systems.

Monitis has put together a checklist of 101 actions you can take to maximize security around LAMP.  Hopefully we’re shedding a little light around this issue for you to give you some new ideas on how to make administering your system easier — so that, in turn, you can focus on more strategic tasks. You …

So far we've looked at many aspects of MySQL, not in any great depth, but hopefully with enough information to get you started and whet your appetite for more.  Now we start to look into areas that aren't in the basic tutorials.

Replication is the technology that allows data to be stored on multiple servers. Typically this is used in "scale out" applications.  "Scale out" is used in contrast to "Scale up" where to scale a solution you buy a bigger box to run it on, where "scale out" means you buy more boxes.  Each has its benefits and drawbacks, with the usual benefit of scale out being that you get more bang for your buck.

The way replication works in MySQL is pretty simple.  One server is identified as the master, and writes every transaction to a file, the binary log.  Other servers (and there may be many) act as slaves and request information from the master. The slave keeps track of where it got up to …

I recently upgraded MySQL to the DMR release of 5.6.3.  Available here :http://dev.mysql.com/downloads/mysql/5.6.html#downloads 
I was reminded of a some questions about mysql_upgrade I have gotten lately. While it is easy to skip, do not forget to run
/usr/bin/mysql_upgrade  after you upgrade.

Yes it is typical to see clean tables.

Simple example:
employees.departments                              OK
employees.dept_emp                                 OK
…

If you have been waiting for Percona’s highly rated MySQL courses to be taught near you, your wait is over. We will be holding our Developer, DBA, InnoDB, and Operations training in the following cities:

• Dublin, Ireland – December 5 – 8, 2011
• San Diego, CA – December 12 – 15, 2011
• New York, NY – January 9 – 12, 2012
• Washington, DC – January 16 – 19, 2012

Full details on the courses can be found on the Percona website. We are providing a special discount code to our MySQL Performance Blog readers. When you purchase your ticket, enter discount code PBLOG to receive 10% off. Act now while early registration is open to save even more.

Read the original article at The market for Cloud Computing

Saw this awesome infographic by Cloud Spectator on twitter today. A great snapshot of the expected growth in Cloud Computing. If the Cloud Computing market was stacked up against world economies it would be the 51st largest in the world with massive inequality - Amazon has half the share.

For more articles like these go to MySQL Expert, Linux, EC2 & Scalability Consulting NYC

Tungsten parallel apply on slaves, or parallel replication for short, has been available for about a year.   Until recently we did not have many formal benchmarks of its performance.  Fortunately the excellent Percona Live Conference in London accepted my talk on Tungsten parallel replication (slides available here), so Giuseppe Maxia and I finally allocated a block of time for systematic performance testing.

In a nutshell, the results were quite good. In the best cases Tungsten parallel apply out-performs single-threaded native replication by about 4.5 to 1.  Both Giuseppe and I have verified this using slightly different test methodologies, which …

Many people have asked me what do I think was the best thing about Percona Live UK. I always answered: that it happened in the first place! This was the first time we had such a large and high-quality MySQL conference in Europe, and many well known bloggers and speakers that can't always travel to Santa Clara were present.

More importantly, many MySQL users who don't travel to Santa Clara could now see them speak and meet with them. I met at least 4 hard core MySQL DBA's from Helsinki that I've never met before. We had to travel to London to meet each other! (But if you are in Helsinki, we have our first MySQL user group tomorrow, this should fix things!)

When I walked into the conference venue, I introduced myself to a person that stood there talking to Baron Schwartz. He introduced himself as Schlomi Noach. Then we …

I deal with all shipes and sizes, and distributions, of Linux. Each Linux distribution has quirks. Particularly with package management. There are some people who are religious about RPM (Redhat, Centos, Fedora, Suse, etc.) or APT (Debian, Ubuntu, etc). I see both good and bad points of each. In my daily tasks, I just want “Things to Work (TM)”. I had an interesting problem the other day that I found a solution for that I thought I would share.

The problem was on a server that I was trying to install Percona 5.5 on that already had a stock Centos MySQL 5.1 install. I need to uninstall the existing packages:

[root@host]# rpm -e mysql-5.0.77-4.el5_6.6
error: "mysql-5.0.77-4.el5_6.6" specifies multiple packages

Hmm, this is very odd. I’ve never seen this. There is a way to reveal exactly what the problem is:

[root@host]# rpm -q --queryformat "%{name}.%{arch}\n" mysql
mysql.x86_64
mysql.i386

Interesting! …