In the first post in a series on MariaDB features we find interesting, we begin with selectively skipping replication of binlog events. This feature is available on MariaDB 5.5 and 10.

By default when using MySQL’s standard replication, all events are logged in the binary log and those binary log events are replicated to all slaves (it’s possible to filter out some schema). But with this feature, it’s also possible to bypass some events to be replicated on the slave(s) even if they are written in the binary log. Having those event in the binary logs is always useful for point-in-time recovery.

Indeed, usually when we need to not replicate an event, we set sql_log_bin = 0 and the event is bypassed: neither …

Percona Server version 5.1.73-14.12

Percona is glad to announce the release of Percona Server 5.1.73-14.12 on July 31st, 2014 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1.73, including all the bug fixes in it, Percona Server 5.1.73-14.12 is now the current stable release in the 5.1 series. All of Percona‘s software is …

This is a wew blog post by Ramana Yeruva on how we test the mysql repository. Please check it out

  http://mysqlrelease.com/2014/07/testing-mysql-repository-packages-how-we-make-sure-they-work-for-you/

Around nine months ago, we launched the MySQL yum repositories for Enterprise Linux and Fedora, followed by apt repos for Debian and Ubuntu back in May. We’re extremely happy that the repos have proved to be a big hit with the community: the monthly number of downloads hit 100K recently and it is still growing […]

Today, I was reminded of a Jim Starkey quote on the Random Query Generator:

“The Colonoscopy of Database Software”
– Jim Starkey

If your project does not have something that you can adapt that quote to, odds are your testing is inadequate.

We are happy to announce the update of comparison tools for Oracle and MySQL databases. Each of them has its own features that our team implemented to let you feel a professional in comparing and synchronizing databases. Choose the right product that is suited for you and enjoy your work.

We are happy to announce the update of comparison tools for Oracle and MySQL databases. Each of them has its own features that our team implemented to let you feel a professional in comparing and synchronizing databases. Choose the right product that is suited for you and enjoy your work.

The frm file has provided long service since the earliest days of MySQL. Now, it is time to replace it with a native InnoDB-based Data Dictionary.

This is a change that has been on our wish list for a long time, as well as others in the MySQL development community:

• Brian Aker on Drizzle, The Death of FRM
• Jan Kneschke on MySQL Internals: screens (or .frm files)
• Stewart Smith on The FRM file format, Goodbye FRM (or at least the steps to it), …

Welcome to another blog post from the MySQL for Excel Team. Today we're going to talk about a new feature included since 1.3.0, remember you can always install the latest GA or maintenance version using the MySQL Installer also you can download directly any GA or non-GA version from the MySQL Developer Zone.

In this post we will learn how to reset several advanced options to their default values.

Remember that your feedback is very important for us, please drop us a message with your comments, suggestions for this or other features and follow us at our social media channels:

• MySQL on Windows (this) Blog:  …

As we know different storage engines in MySQL have different file structures. Every table in MySQL 5.6 must have a .frm file in the database directory matching the table name. But where the rest of the data resides depends on the storage engine.

For MyISAM we have .MYI and .MYD files in the database directory (unless special settings are in place); for InnoDB we might have data stored in the single table space (typically ibdata1 in the database directory) or as file per table (or better said file per partition) producing a single file with .ibd extension for each table/partition. TokuDB as of this version (7.1.7) has its own innovative approach to storing the table contents.

I have created the table in the database test having the following structure:

CREATE TABLE `mytable` (
  `id` int(10) unsigned NOT NULL,
  `c` varchar(15) NOT NULL, …