I have had a busy year playing with databases and it is nice that now things are slowing down. Of course next year holds lots more changes, but that is normal.

The big MySQL 5.0 to 5.1 upgrade that I have been spending a lot of time on recently has nearly finished. In spite of the early issues with upgrading servers with stored procedures and triggers, most of the servers are now running 5.1 so that is good, and the upgrades have been reasonably painless. Only the master servers need to be looked at, but with fewer people being around over the holiday period this will wait until next year.

Several users have been pleasantly surprised by the performance gain in switching to 5.1. That is also good news. When I finish upgrading all servers I will also be able to try out some of the 5.1 features such as RBR or partitioning. On the larger servers I’m hoping this will further help performance.

Finally I should be able to escape …

I’m on the MySQL conference committee again this year, so I’ll be reading and voting on your session proposals. My past experience is that reading 400 session proposals is a mind-numbing job, and I will be optimizing it to save my time. That means I will be scanning your proposals and deciding very quickly how to vote. I wrote before about how to submit a great proposal, but I’ve refined my opinion since then. Here are my suggestions:

• Write for two audiences: reviewers and attendees. Both of us want the same thing: to decide as quickly as possible whether your session will be good.
• Write a strong title/headline. Don’t know how? …

The MySQL conference site for 2010 is live, and ready for your proposals. Submit! Submit! Submit!

Related posts:

1. There will be an O’Reilly MySQL Conference in April 2010 O’Re
2. How to write a good MySQL conference proposal I’m
3. Attending the IT Management Conference I’ll

Related posts brought to you by Yet Another Related Posts Plugin.

MySQL 5.5 includes a number of features first implemented by the "Google patch", but in a different way. One feature in the patch that is still missing from 5.5 appears to be a monotonically increasing transaction identifier in the binary log.

I'm wondering where this feature is on the roadmap, and if we are likely to see it in one of the upcoming milestones?

I’m on the MySQL conference committee again this year, so I’ll be reading and voting on your session proposals. My past experience is that reading 400 session proposals is a mind-numbing job, and I will be optimizing it to save my time. That means I will be scanning your proposals and deciding very quickly how to vote. I wrote before about how to submit a great proposal, but I’ve refined my opinion since then.

The MySQL conference site for 2010 is live, and ready for your proposals. Submit! Submit! Submit!

With the beta releases of MySQL Workbench 5.2 well under way, we recently announced the EOL (http://www.mysql.com/support/eol-notice.html) of the MySQL GUI Tools Bundle.

The MySQL Tools team has been working on MySQL Workbench 5.2 to give DBAs and developers an integrated tools environment for:

• Database Design & Modeling
• SQL Development (replacing MySQL Query Browser)
• Database Administration (replacing MySQL Administrator)

MySQL Workbench 5.2 also provides:

• Remote Administration (using SSH-Tunneling)
• Python scripting and plugins
• Native GUI for Windows, Mac, Linux

A future release of MySQL Workbench (post 5.2) will add a migration plugin, providing features comparable to the MySQL Migration Toolkit component of the MySQL GUI Tools Bundle.  We will …

The re-enabling of the dlopen()-based dynamic plugin loading has hit the Drizzle trunk. This means that plugins can now be built as shared modules and loaded at will on server startup. We still do not support dynamically loading a plugin in a running server via the LOAD PLUGIN command, nor will we until this can be done without re-introducing global mutexes.

Since this is a feature we turned off a while ago, but that was there before, why mention it? There have been several changes to the system that I thought would be handy to mention.

First of all, Drizzle has a crap-ton of plugins and the numbers are only growing. In the tree now, the default is to build any of them we are able to, and to build them all as shared modules, rather than statically linking them into the server.  Then, from the list of built and available plugins, there is a default list of plugins that should be loaded if no other options are given.

…

Topics for this podcast:

*2009 review and 2010 preview
*New CAOS survey and report – Climate Change
*Ups and downs in new round of GPL lawsuits
*Oracle-Sun-MySQL saga continues

iTunes or direct download (30:00, 6.9 MB)

Dear MySQL Users,

We are proud to announce public Beta 3 of MySQL Workbench 5.2.

First off, again a big “Thank You” to all the people who have been testing MySQL Workbench 5.2 alphas and betas and taking the time to file bugs and provide valuable feedback. We have fixed another pile of bugs and included some minor changes in some of the workflows. We have upgraded our linux packages and are now serving packages for Fedora 12 and Ubuntu 9.10.

This build includes fixes for 54 bugs – 9 P1, 28 P2 and 17 P3.

MySQL Workbench 5.2 Beta 3 provides:

1. Data Modeling
2. Query (upgrade from MySQL Query Browser)
3. Admin (upgrade from MySQL Administrator)

If you are a current user of MySQL Query Browser or MySQL Administrator, we look forward to your feedback on all the new capabilities we are delivering in a single unified MySQL Workbench

As always, you will …