Migrating your database to a new datacenter can be a high-risk and time-consuming process. A database contains state, and can be much harder to migrate as compared to web servers, queues or cache servers.

In this blog post, we will give you some tips on how to migrate your data from one service provider to another. The process is somewhat similar to our previous post on how to upgrade MySQL, but there are a couple of important differences.

MySQL Replication or Galera Cluster?

Switching to another service provider (e.g., moving from AWS to Rackspace or from colocated servers to cloud) very often means one would build a brand new infrastructure in parallel, sync it with the old infrastructure and then switch over to it. To connect and sync them, you may want to leverage MySQL replication.

If you are using …

Yes, your read the title correctly: an unprivileged user can crash your MySQL Server.  This applies for the default configuration of MySQL 8.0.21 (and it is probably the case for all MySQL 8 GA versions).  Depending on your configuration, it might also be the case for MySQL 5.7.  This needs malicious intent and a lot of determination, so no need to panic as this will not happen by

Percona Live Online Agenda Slot: Wed 21 Oct • New York 7:30 a.m. • London 12:30 p.m. • New Delhi 5:00 p.m. • Singapore 7:30 p.m.

Abstract

ProxySQL is a high performance, high available, protocol aware proxy for MySQL. 2.0 has been GA for some time now, and there have been a lot of changes that come in point releases as well, such that you can benefit from them.

Listen to René, the founder of ProxySQL, take you through some of the new features in 2.0, and how you can effectively utilize them. Some topics that are covered include:

– LDAP authentication
– SSL for client connections
– AWS Aurora usage
– Native clustering support for Percona XtraDB Cluster (PXC) / Galera Cluster / group replication
– Kubernetes deployments

This is the talk to take you from intermediate ProxySQL user to …

Changing the default value (3) of log_error_verbosity in MySQL/Percona Server for MySQL 5.7 can have a hidden unintended effect! What does log_error_verbosity do exactly? As per the documentation:

“The log_error_verbosity system variable specifies the verbosity for handling events intended for the error log.“

Basically a value of 1 logs only [Errors]; 2 is 1)+[Warnings]; and 3 is 2)+[Notes].

For example, one might be tempted to change the default of log_error_verbosity since the error.log might be bloated with thousands (or millions) of lines with [Notes], such as:

2020-10-08T17:02:56.736179Z 3 [Note] Access denied for user 'root'@'localhost' (using password: NO)
2020-10-08T17:04:48.149038Z 4 [Note] Aborted connection 4 to db: 'unconnected' user: 'root' host: 'localhost' (Got timeout reading communication packets)

(P.S. you can read more about those Notes on this other Percona blog posts):

Percona Live Online Agenda Slot: Wed 21 Oct • New York 3:30 a.m. • London 8:30 a.m. • New Delhi 1:00 p.m. • Singapore 3:30 p.m.

Abstract

DBdeployer, an open source tool that allows easy deployment of many MySQL/Percona servers in the same host, has passed two years of development. Its latest additions have aimed at improving ease of use for both beginners and experts. This talk will show how to start with dbdeployer with an empty box, and quickly populate it with recent and less recent server versions, all at the command line.

Why is your talk exciting?

This talk is a celebration of collaboration in the community. I will present recent features that were requested, or suggested, by the community. I will also show how those suggestions came to fruition, to …

In InnoDB Data Locking – Part 1 “Introduction” we’ve described the difficulties Lock System tries to solve using metaphor of people trying to concurrently edit spreadsheets. While it might be useful metaphor to get some intuitions about the problem, to talk about solutions it helps to know at least a little about the “reality” this metaphor maps to.…

Facebook Twitter LinkedIn

PHP provides a handy function, empty(), that is used to determine whether a variable is empty. Perhaps that is a bit confusing to someone unfamiliar with the empty() function and I can see how. In this blog post, I will cover: what empty() means in PHP, what the empty() function does, and a use case pairing up empty() with the PHP ternary operator conditional construct. Both used in combination with the MySQL NULL value. Continue reading and see examples of empty()…

Photo by Debby Hudson on …

Percona Live Online Agenda Slot: Wed 21 Oct • New York 7:00 a.m. • London 12:00 noon • New Delhi 4:30 p.m. • Singapore 7:00 p.m.

Why is your talk exciting?

I’m not sure if my talk is exciting, but I’m quite positive the subject is! Vitess has been gaining a lot of traction over the past few years and I must admit that I’ve been keen to get hands-on experience with it for years. As we, MessageBird, encounter rapid growth standard (read) scaling wasn’t applicable anymore and we were in need for a solution. Late 2019 we implemented our (quick) DIY sharding solution based upon existing components. A few months later we encountered the next scaling issue and we found our own built solution wasn’t suitable in this case. That’s when we considered investing our time instead in a Vitess proof of concept (community edition) and this talk will …

There are different reasons for upgrading your databases. It could be to apply security fixes, to use new features, solve compatibility issues, or just to keep your system up-to-date. This upgrade can be a major upgrade or a minor one, and depending on the technology, there are different approaches to do this job, but if you need your systems running all the time with zero downtime, performing a rolling upgrade could be the best option.

In this blog, we will see some considerations to take into account before upgrading and how to perform a rolling upgrade on MySQL.

Minor vs Major Upgrades

In general, minor upgrades are safe in the way that you can easily downgrade or rollback it and should be compatible with the previous packages and features.

Major version upgrade involves some risks like database package removal, …

 I am please to announce that the Second Edition of MySQL and JSON - A Practical Programming Guide is now Available.  The new book is twice the length of the first edition due to  the many advancements made by MySQL Engineering over the past two years. 

Who needs this book:   Anyone wanting to take advantage of the MySQL JSON data type for storing JSON formatted data, those wanting to turn relational data into JSON, those who want to make their JSON data relational, and those seeking a through introduction into the use of MySQL as a NoSQL JSON 

document store.  The second edition features even more illustrations, code examples, and covers the many new features added in the last two years including JSON document validation (yes, you can have required fields, type checking, and constraints on your JSON data before it gets into the database), new MySQL …