The MySQL Community Awards initiative is an effort to acknowledge and thank individuals and corporations for their contributions to the MySQL ecosystem. It is a from-the-community, by-the-community, and for-the-community effort. The committee is composed of an independent group of community members of different orientation and opinion, themselves past winners or known contributors to the community.

The 2017 community awards were presented on April 27, 2017, during the keynotes at the Percona Live conference. The winners are:

MySQL Community Awards: Community Contributor of the year 2017

• René Cannaò
  René – for creating and maintaining the ProxySQL project actively.
• Shlomi Noach
  Shlomi has been a been a conference chairperson for years, ran these mysqlawards for a long time, has been …

Isolation levels are a rare subject in MySQL literature. The documentation provides a terse description and focuses mainly on locking issues, but does not discuss the semantics of each isolation level. This is not only a problem that affects MySQL documentation but also the SQL standard itself.

Both the lack of documentation and the absence of a deeper description of the expected behavior in the SQL standard make isolation levels a topic that is more assumed than known by database administrators and developers. In this blog post, I aim to help you understand how the default isolation level in MySQL works and show you some surprising facts about it.

But first let’s see how isolation levels are described in the standard: “The transaction isolation level of a SQL-transaction defines the degree to which the operations on SQL-data, or schemas in that SQL-transaction are affected by the effects of and can affect operations on …

With tons of new No-SQL database offerings everyday, developers & architects have a lot of options. Cassandra, Mongodb, Couchdb, Dynamodb & Firebase to name a few. Join 33,000 others and follow Sean Hull on twitter @hullsean. What’s more in the data warehouse space, you have Hadoop, which can churn through terabytes of data and get … Continue reading Will SQL just die already? →

OK, Y’all.  If you have been a DBA long enough you have run into situations where you’ve had to import DDL from another database instance and forgotten to remove AUTO_INCREMENT on a table definition.  Sometimes this means your auto_increment is way up in the millions and you have 10 rows in the table.  People worried about ID depletion on an integer column will do a “facepalm”.

Making matters worse, having perhaps done this on more than one table, sometimes it’s a real pain to detect and fix the issue of auto_increments being much higher than you want them to be across a big number of tables.  Sometimes the pain is so great that you might want to simply repeat your data importation.

This quick and dirty “southern fried” script will help you report and rectify that.  It detects …

Taking a logical backup of a member of a Group Replication Cluster is not something very easy.

Currently (5.7.17, 5.7.18 or 8.0.0) if you want to use mysqldump to take a logical backup of your dataset, you need to lock all the tables on the member you are taking the dump. Indeed, a single transaction can’t be used as savepoints are not compatible with Group Replication.

[root@mysql3 ~]# mysqldump -p  --single-transaction --all-databases --triggers \
                      --routines --events >dump.sql
Enter password:
mysqldump: Couldn't execute 'SAVEPOINT sp': The MySQL server is running with the 
--transaction-write-set-extraction!=OFF option so it cannot execute this 
statement (1290)

So we need to use:

[root@mysql3 ~]# mysqldump -p  --lock-all-tables --all-databases --triggers \
                      --routines --events >dump.sql
Enter password:

This can have a negative effect on the full Group’s …

It was a big April if you’re in the MySQL ecosystem, so am looking forward to other events that have different focus and a different base, so to speak. See you at:

• rootconf – May 11-12 2017 – Bangalore, India. My first Rootconf was last year, and it was a great event; I look forward to going there again this year, to talk about capacity planning for your databases. If you register with this link you get a 10% discount.
• Open Source Data Center Conference – May 16-18 2017 – Berlin, Germany. I’ve enjoyed my trips to OSDC in the last few years, and they’re on their last tickets now …

This post is about quick steps to install Percona XtraBackup on the CentOS using yum repository. I have made it step by step for easy understanding.
Operating system information:

Add Percona repository:

yum install http://www.percona.com/downloads/percona-release/redhat/0.1-4/percona-release-0.1-4.noarch.rpm

This will …

I heard a frequent question at last week’s Percona Live conference regarding Percona Monitoring and Management (PMM): How much disk space should I allocate for PMM Server?

First, let’s review the three components of Percona Monitoring and Management that consume non-negligible disk space:

1. Prometheus data source for the time series metrics
2. Query Analytics (QAN) which uses Percona Server XtraDB (Percona’s enhanced version of the InnoDB storage engine)
3. Orchestrator, also backed by Percona Server XtraDB

Of these, you’ll find that Prometheus is generally your largest consumer of disk space. Prometheus hits a steady state of disk utilization once you reach the defined storage.local.retention period. If you deploy Percona Monitoring and Management …

The "MySQL for Database Administrators" course has been revised and released in its 4th edition.

As with previous editions, it covers the core techniques that all DBAs need to know, such as server configuration, user management, security, troubleshooting, query optimization, backups, and maintaining high availability.

The new edition also covers how to use exciting new features in the latest MySQL GA releases, including Group Replication and MySQL Cloud Service.

This is a very hands-on course, and each lesson has extensive practical activities so that you get a chance to try out new features and techniques in the safety of a properly-configured learning environment.

You can take this course in the following formats:

• Live-Virtual Event: Attend a live event from …

We will demonstrate the ease of monitoring Galera Cluster using Monyog MySQL monitor. By the end of the webinar, you will have a better understanding of how to use Monyog for monitoring Galera Cluster for MySQL to achieve a required balance of high availability and scalability.

Galera Cluster for MySQL is a multi-master active-active cluster. It is an easy-to-use, high-availability solution, which provides high system uptime, no data loss, and scalability for future growth. In this webinar, we will give an overview how does Galera Cluster work and what are the benefits of using Galera Cluster.

Join USA timezone webinar Wed, May 17, 10:00 AM – 11:00 AM PDT

Join EMEA timezone webinar Wed, May 17, 11:00 AM – 12:00 AM CET