With an ear to the interwebs, you’ll hear a few things about Docker. Docker is an open platform for developers and sysadmins to build, ship, and run distributed applications. In this blog post, I’m going to outline a very basic example of how to use Sphinx from within a Docker container. What is Docker? This [...]

Yay! My first blog post! As long as at least 1 person finds it useful, I’ve done my job. Recently, one of my long-term clients was noticing that while their INSERTs were succeeding, a particular column counter was not incrementing. A quick investigation determined the column was of type int(11) and they had reached the maximum value of 2147483647. We fixed this by using pt-online-schema-change to change the column to int(10) unsigned, thus allowing values up to 4294967295.

My client was now concerned about all his other integer-based columns and wanted me to check them all. So I wrote a quick-n-dirty script in Go to check all integer-based columns on their current value compared to the maximum allowed for that column type.

You …

MySQL Cluster enables high availability by storing data replicas on multiple hosts. MySQL Cluster maintains connections between data nodes by using high-speed interconnects over TCP/IP - standard or direct connections - or SCI (Scalable Coherent Interface) sockets.

To learn more about MySQL Cluster, take the MySQL Cluster training course.

This course is currently scheduled for the following locations:

After MySQL 5.1 was released work started on MySQL 5.2, but then this was renamed to MySQL 6.0. There were many new features introduced in 6.0. But then stabilizing this branch became as huge task. Eventually the decision was made to start of with a stable branch and backport the new features from 6.0. This is how many of the 6.0 features landed in 5.5 and 5.6.

So let's see which features 6.0 brought and were they landed. I'll use the What Is New in MySQL 6.0 section of the MySQL 6.0 Reference Manual for this.

• The Falcon storage engine. This never landed anywhere as far as I know. It's not even included in the …

Critical MySQL 5.6 bug: any user with GRANT privileges can unwillingly cause all replicas to break

The latest major release of MySQL brought us a lot of new and exciting features. As always, new features come with brand new bugs waiting to bite you in the least expected way.

I was implementing a monitoring system for a client and needed to create a new dedicated user. I went ahead and granted the usual basic privileges but later, I discovered that this user also needed the REPLICATION CLIENT privilege because the monitoring needed it to check for replication status.

No big deal, let’s grant this as well. Unfortunately I did not get it right at first:

grant replication client on database.* to user@’10.%';
ERROR 1221 (HY000): Incorrect usage of DB GRANT and GLOBAL PRIVILEGES

Ouch! My bad! This is a global privilege and I should grant it on “*.*”:

grant replication client on *.* to …

Finally! The new db4free.net Website has launched and along with it comes a new (slightly stronger) server and some simplifications with the service itself.

So what is new? Of course the new website which now is up to modern standards again, using a responsive design. While the old site was only designed for desktop (no surprise if you consider it was created in 2005 and remained more or less unchanged since), the new site adopts to small screen devices like mobile phones and tablets as well. Also the look is totally different:

db4free.net old

db4free.net new

The service now has a few simplifications. It is no longer allowed, or necessary, to …

In the previous post of this series we saw how you could use mysqlrpladmin to perform manual failover/switchover when GTID replication is enabled in MySQL 5.6. Now we will review mysqlfailover (version 1.4.3), another tool from the MySQL Utilities that can be used for automatic failover.

Summary

• mysqlfailover can perform automatic failover if MySQL 5.6′s GTID-replication is enabled.
• All slaves must use --master-info-repository=TABLE.
• The monitoring node is a single point of failure: don’t forget to monitor it!
…

One of the most frequent questions in our forums is about how to get the graphical integration when using Visual Studio with MySQL databases.

When developing applications with MySQL databases there are two basics products: a .net driver for MySQL, which is MySQL Connector/Net, and a tool to integrate all of the Visual Studio database oriented tools such as the Server Explorer window. These tools are designed to make a lot easier the creation and edition of MySQL databases when using an IDE like Visual Studio.

I was recently asked about if MySQL Enterprise Backup would be able to restore single databases.

My initial answer was that this was complicated, but might be doable with the Transportable Table Space (TTS) option.

But first let's go back to the basics. A common way of working with mysqldump is to get a list of databases and then loop through the databases and dump the data and schema to a SQL file. But both backups and restores will take a lot of time if the size of the database grows. And it's a luke-warm backup at best instead of a hot backup. So that's why we have MySQL Enterprise Backup.

MySQL Enterprise Backup allows you to make a hot backup of InnoDB tables by copying the datafiles while watching the InnoDB redo log files.

On disk the data from the InnoDB storage engine consists of a system tablespace (one of more ibdataX files), the redo log files (iblogfileX) and zero or more …

MySQL for Visual Studio is a product including all of the Visual Studio integration previously available as part of Connector/Net. The 1.2.1 version is a beta release of this product which is feature complete but still can contain minor bugs and is not suitable for production environments.