Starting from Percona Toolkit 3.6.0, pt-online-schema-change supports the option –where, so you can not only alter your table definition live but copy only rows that satisfy certain criteria. It may happen that you may not need to copy all the data when changing table definition. For example, if the table is too big and you […]

A month ago, I announced that I am working on a MySQL Contribution to add database / schema in the slow query log file (bug report, LinkedIn, Twitter, Facebook, and MySQL Community Slack).  My contribution is ready, and before submitting it, I would like feedback, so I am writing this post as a Request for Comments (RFC).  If you are in a hurry, you can go directly to the RFC Fake PR.&

I got quite a response to my article on whether Oracle is Killing MySQL, including a couple of great write-ups on The Register (1, 2)  on the topic.  There are a few questions in this discussion that I think are worth addressing.  AWS and other cloud vendors compete, without giving anything back, what else would […]

In today’s data-driven world, organizations rely heavily on data analysis and visualization to make informed decisions and gain a competitive edge. Microsoft Power BI and MySQL are two powerful tools that can facilitate this process. In this article, we will explore the process of how to connect MySQL to Power BI, a leading business intelligence tool.

Understanding Power BI Definition and Purpose

Power BI is a business analytics service that can gather all your data in a single platform and enable users to analyze and visualize easily. It provides a user-friendly interface and a wide range of tools to transform raw data into meaningful insights.

Key Features

Power BI offers an array of features, including interactive dashboards with a drag and drop interface, real-time data monitoring, natural language queries, and seamless integration with other Microsoft applications …

Starting from Percona Toolkit 3.6.0, you can resume pt-online-schema-change if it was interrupted. This blog describes the prerequisites and usage of the new –resume option. To restart the job, you need to know where it failed. This is why the first option you must use is –history. It instructs pt-online-schema-change to store its progress in […]

At Percona, we monitor our users’ needs and try to accommodate them. One aspect we monitor is the MySQL version distribution/utilization. Observing that, we identified a very interesting trend: the lack of migration from 5.7 to 8.x, or better yet, the need of many to remain on 5.7.  That observation has triggered several actions from […]

MySQL Shell offer many features to make life easier for DBAs and developers. In this post we discuss how to view and manage MySQL Shell configuration values.

Keeping Your Data Safe: An Introduction to Data-at-Rest Encryption in Percona XtraDB Cluster. In the first part of this blog post, we learned how to enable GCache and Record-Set cache encryption in Percona XtraDB Cluster. This part will explore the details of the implementation to understand what happens behind the scenes. How does it work […]

MySQL Shell offer many features to make life easier for DBAs and developers. In this post we discuss how to view the details of the connection to a MySQL instance.

MySQL warnings are an anti-pattern when it comes to maintaining data integrity. When the information retrieved from a database does not match what was entered, and this is not identified immediately, this can be permanently lost.

MySQL by default for several decades until the most recent versions enabled you to insert incorrect data, or insert data that was then truncated, or other patterns that resulted in failed data integrity. Very few applications considered handling warnings as errors, and there is a generation of software products that have never informed the developers that warnings were occurring.

The most simplest example is:

CREATE SCHEMA IF NOT EXISTS warnings;
USE warnings;

CREATE TABLE short_name(
  id INT UNSIGNED NOT NULL AUTO_INCREMENT,
  name VARCHAR(20) NOT NULL,
  PRIMARY KEY(id)
);

INSERT INTO short_name (name) VALUES ('This name is too long and will get truncated');
ERROR 1406 (22001): Data too long for …