I’m very pleased to announce that the breakout session and tutorial schedules for the third annual Percona Live MySQL Conference and Expo 2014 are now online. The conference will be at The Hyatt Regency Santa Clara and Santa Clara Convention Center, April 1-4, 2014. I wish to personally thank our dedicated Conference Committee members who put in many hours evaluating hundreds of submissions in order to create these schedules.

Breakout Session Schedule

We have a strong and diverse schedule of breakout sessions which will take place April 2-4, following each morning’s keynote addresses. The speaker list includes top MySQL practitioners from …

I’ve been blogging a lot about some of the new things you can expect with Percona XtraDB Cluster 5.6 and Galera 3.x – and GA is coming …

Oracle has released the Critical Patch Update (CPU) advisory for January 2014.

The affected MySQL products are:

• Oracle MySQL Enterprise Monitor, versions 2.3, 3.0 

• Oracle MySQL Server, versions 5.1, 5.5, 5.6

So this means that you should consider updating MySQL. For MySQL Enterprise the updates should be available on My Oracle Support and for the Community version the new versions are on the regular download locations. I guess the official repositories are already updated.

For MySQL 5.6 you should upgrade to 5.6.15
For MySQL 5.5 you should upgrade to 5.5.35
For MySQL 5.1 you should upgrade to 5.1.73

If you use the MySQL release from your distribution …

Several MariaDB developers are attending SkySQL’s annual engineering meeting being held this week in Barcelona. While some of the discussions are SkySQL-specific (customers, internal projects, and so on), there are, naturally, lots of MariaDB discussions happening.

Patrik Sallner, CEO of SkySQL, opened the meeting this morning with a short presentation about SkySQL’s goals for 2014. While the plan includes standard business-like things that include growing the company and sales goals, the top two goals for 2014 are:

1. Help make MariaDB into the leading open source database

2. Help increase awareness and adoption of MariaDB

Looking back at 2013, it was an excellent year for MariaDB. It is now the default database in Fedora, OpenSUSE, Mageia, and others and it is included in the recently released Red Hat Enterprise Linux 7  preview. During the last …

UPDATED: explaining the role of innodb_strict_mode and correcting introduction of innodb_file_format

Compressed tables is an example of an InnoDB feature that became available with the Barracuda file format, introduced in the InnoDB plugin. They can bring significant gains in raw performance and scalability: given the data is stored in a compressed format the amount of memory and disk space necessary to hold it and move it around (disk/memory) is lower, thus making them attractive for servers equipped with SSD drives of smaller capacity.

The notion of “file formats” (defined by the variable innodb_file_format) was first introduced when InnoDB was still a …

MariaDB is in Debian/unstable now, and its great to see that we already have a Japanese po-debconf translation (in under a month!). The last time I was in Tokyo, Japan we seemed to have great interest in MariaDB, especially with the backing of MariaDB.com/SkySQL investment dollars and the MariaDB Foundation to keep things real.

For me, I’m happy to go back to Tokyo to talk to users about MariaDB. If you’re in the area on Tuesday, 18 February 2013, there is a …

MySQL Cluster Manager 1.3.0 is now Generally Available and can be downloaded from the Oracle Software Delivery Cloud. The release contains a number of enhancements including performance improvements, handling larger clusters and of course bug fixes. The other big feature is that you can now import an existing, running MySQL Cluster instance into MCM without having to stop it first – this is the topic for this post.

In the past, we had a nice browser-based tool (the MySQL Clster Auto-Installer) to get a well configured cluster up and running (tuned to your environment) and we also had MySQL Cluster …

Acteur international des services informatiques avec un chiffre d’affaires annuel de 8,8 milliards d’euros et 77,100 collaborateurs dans 52 pays, Atos fournit à ses clients du monde entier des services informatiques dans 3 domaines, Conseil & Services Technologiques, Intégration de Systèmes et Infogérance & BPO, ainsi que Services Transactionnels de Haute Technologie avec Worldline.

En 2009, Atos s’est vu confier le projet de réduire drastiquement les coûts du moteur de compensation des marchés Cash (actions et obligations) et Produits Dérivés d’Euronext en Zone euro: l’application UCS (Universal Clearing System). Dans le domaine financier, la compensation, ou le "clearing", s'exerce par l'agrégat de toutes les positions d'achats et de ventes par type de produit/actif détenu par chaque teneur de compte, et se matérialise par un solde net dû ou à recevoir ainsi que par des flux nets de titres à livrer ou à …

I have put up a set of scripts on github: https://github.com/stewartsmith/bzr-to-git-conversion-scripts. Why do I need these? Well… if only bzr fast-export|git fast-import worked flawlessly for large, complex and old trees. It doesn’t.

Basically, when you clone this repo you can run “./sync-BLAH.sh” and it’ll pull BZR trees for the project, convert to git and clean things up a bit. You will likely have to edit the sync-BLAH.sh scripts as I have them pointed at branches on my own machine (to speed up the process, not having to do fresh BZR branches of MySQL trees over the network is a feature - it’s never been fast.). You’ll also want to edit the git remotes to point where you want git trees to end up.

I’ve done it for:

• Bazaar …

So how would a DBA set up a system to expire the password of interactive MySQL users? Some kind folks have been reading the last few entries of this blog and asked me to flesh out how to go from concept to production and we will work this out together (feedback please!) over the next few postings.

The first step is to find out what information we have and then determine what information do not have. We have the account name, the password, and if the password is expired. But we do not know the interval for password expiration. We might want to keep track of when the last change was made, possibly keep a list of the last N passwords to check against to discourage reuse, and maybe have a black list of words not to use as passwords.

In the mysql.user table we find the account name, the password, and if the password is expired or not. But we need some new tables to hold the data we do not have yet. I have seen some …