MySQL HeatWave Best Practices Series: Schema Design

MySQL Community Advent Calendar 2022 - How to generate MySQL slow query log in OCI for MySQL HeatWave Database Service using Fn infrastructure

MySQL Community Advent Calendar 2022 - How can you analyze queries in MySQL Database Service in OCI using Performance_Schema

In the previous part, we created our application and our 2 functions. Now we need to create an API Gateway to be able to call these functions from outside OCI. Using a third party scheduler, our laptop, etc… Before creating the gateway, we need to create some policy to allow the API Gateway to call […]

In my previous post, I explained how to deal with Performance_Schema and Sys to identify the candidates for Query Optimization but also to understand the workload on the database. In this article, we will see how we can create an OCI Fn Application that will generate a slow query log from our MySQL Database Service […]

​ In a previous post, I talked about using MySQL Shell to import JSON data into a MySQL Document Store. But what if you have JSON data that you need to import into a column into an existing table? Fear not; the importJSON() utility can handle this as well. This post assumes you have access to a MySQL […]

In this blog, I’m going to discuss how to easily skip the replication errors in GTID (Global Transaction Identifier)-based replication.

In the MySQL world, if replication is broken we all use the famous SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; to skip the replication error. It always works if it’s a traditional binlogs events-based replication and is helpful to quickly resume the replication. But does this same method work for GTID-based replication? Let’s see.

In GTID-based replication, skipping a replication error in a broken replica is not as simple as binlogs-based replication. We have one old blog post — Repair MySQL 5.6 GTID replication by injecting empty transactions —where one of our colleagues showed us one way to skip and fix the replication.

Let’s get into action and …

Percona Server for MySQL 8.0.30-22 introduces a new authentication plugin, named authentication_fido. With this new plugin, it is possible to perform multi-factor authentication using hardware keys, or single-factor passwordless authentication with the same keys. This new plugin is in technical preview.

The plugin works exactly the same as the MySQL Enterprise FIDO authentication plugin, which is documented in detail in the official MySQL documentation and in the Percona Server for MySQL documentation

To try …

If like me you are an old experienced MySQL DBA, to analyze your MySQL workload, you certainly have used the slow query log with long_query_time set to 0. The slow query log is a file that contains all the queries whose execution time is greater than the value of long_query_time. This file can be huge […]

Today’s MySQL Community Advent Calendar post is about JSON datatype. Let’s start with some info about how MySQL Document Store handles JSON documents. Document Store and CRUD We know that MySQL 8.0 Document Store handles JSON documents with CRUD operations. We can add, delete and modify those documents very easily: JS > db.mycollection.find() { "_id": […]