The MyQl 5.1 DAB exam is series of tasks. The material was divided into a mandatory section and an optional section. The mandatory section is a test of core MySQL DBA skills and you must pass all five. The option section, to be detailed in the next post, is made up of ten tasks and the candidate must past at least five of them. This may sound simple but try cramming a full day of DBA work into two hours and you will have a good idea of what taking this new exam is like.

The Mandatory Tasks

1. 
   
2. Account maintenance
   

• 
  
• Add, delete and modify accounts using the mysql database.
  
• Assign privileges for a user on a table and column basis.
  
• Reset passwords
  
• Locate 'anonymous' accounts (where password AND user are both = '')
  

Index management

The #mysql-dev irc channel on freenode was created with the idea of getting the community people more involved in active discussion about mysql internals and development. When the channel was first created this happened for a few weeks and I was pretty happy to be able to observe and participate in the discussion. Now it’s mostly idle.

It seems that some people at Sun think there is still active discussion or internal developers paying attention to the channel because the GSoC web page directs people to #mysql-dev as a point of contact. The problem is there isn’t anyone there answering questions. I’ve seen quite a few people over the past few weeks ask questions that have gone unanswered. I think it’s time to restart the movement to open development and using #mysql-dev for discussion.

I’m excited to announce that Paul Vallée, Pythian Founder and Executive Chairman, will be on-the-air online this week with a free webinar — Database Platform Migration: when is it strategically appropriate to migrate existing applications to an open-source platform? It’s based on our 10+ years experience supporting proprietary databases, such as Oracle and SQL Server, and open-source MySQL databases on the other hand and what we learned on the numerous migrations.

One of the recent projects completed with one of our Australian clients — 1 TB Oracle RDB on OpenVMS migrated to MySQL on Linux with Heartbeat cluster for high availability.

On the other hand, one telco client in Sydney, which we provide Oracle support for, notified me that they recently migrated a MySQL database to Oracle because they couldn’t find high quality enterprise level support for it. I wish we were engaged with them earlier but they seem to be …

This week, I'm finishing up my book "Developing Web Applications using Perl, memcached, MySQL and Apache". I just finished up Chapter 1, which is the first chapter where I discuss several things such as how much things have changed in the last ten years with web development and Open Source in general. This lead me to write a small section about the future. I was pondering -- where are we going to be in ten years from now? What projects will be popular? This lead me even to a more specific question, and one that I would ask here: what is to become with the development of MySQL? What will be the official development branch of MySQL, and where is all the energy and excitement going to be around?

There is now one fork and one major branch of MySQL now that I will mention, both are exciting projects-- and neither of them is coming from official MySQL/Sun:

(The order of these is strictly alphabetic and not priority!)
…

It’s always the little things in life. One of the things that has been a very “little thing” that causes a lot of frustration while writing The MySQL Administrator’s Bible is the prompt. Specifically, the fact that you can only change the first line of the prompt, but not the subsequent lines.

The default prompt that appears on the first line of the prompt is:
mysql>
The default (and unchangeable) second line of the prompt is four spaces followed by an ASCII arrow:

    ->

The second line of the prompt is hard-coded to match up very nicely with the first line in a fixed-width font:

mysql> SELECT
    -> 1+2;

However, you can change the prompt, which is pretty handy:

mysql> prompt \d:
PROMPT set to '\d: '
(none): use test;
Database …

One of the things that has made MySQL grow a lot is the easy setup of replication on Internet sites. This has allowed them to grow from one database server to many reasonably easily. Configuration of replication is quite simple and replication itself is extremely fast. That makes it ideal for most people.

However at a point in time you begin to notice some of the weaknesses in the current design. Here are a few comments providing ideas on what I would like to see in MySQL replication and why they are features which are important to anyone who’s database requirements grow outside of a single database instance.

My list of current issues is as follows:

1. MySQL only allows replication from 1 to N servers.
2. Some important aspects of MySQL Configuration are not dynamic.
3. Replication is part of the mysqld server, not a separate process.
4. It’s not easy to configure table replication (config …

We added some new features to our backup tool, namely:

• Now we can handle log file taken during backup with size exceeding 4GB, it may happen if backup takes too long and you have a lot of updates on InnoDB tables
• Progress meter during recovery step, now you can see what percentage of log file was handled

PLAIN TEXT CODE:

1. InnoDB: Doing recovery: scanned up to log sequence number 1316 3688693248 (34 %)
2. ...
3. InnoDB: Doing recovery: scanned up to log sequence number 1316 4113366528 (68 %)
4. InnoDB: Doing recovery: scanned up to log sequence number 1316 4117548544 (68 %)

Also we did extensive testing and fixed bugs, so now we consider current state as feature complete and with beta-release stability.

You can …

For some reason my posts aren’t getting over to the planet site, so here’s a test post before I actually write something that might be important.

For some reason my posts aren’t getting over to the planet site, so here’s a test post before I actually write something that might be important.

We're making steady progress in removing bottlenecks in the Drizzle code base. So far, a number of mutexes have been removed and we've begin to replace a number of contention points with atomic instructions which remove the need for a lock structure on platforms which support atomic fetch and store instructions.

I'm pretty positive about the direction we are going so far. We're seeing the right trends in our scaling graphs, with very little performance drop off in read-only workloads up to 4X the number of cores on the machine, and little performance drop off on the read-write workloads up to 2X the number of cores, as you can see from the graphs below.

It's a little difficult to see, but we've made a small but steady improvement from r950 to r968, with numbers increasing around 1-2% across most concurrency levels. You can see the raw numbers here:

+--------------------------------+-------+-----+---------+----------+
| …