Your MySQL database has been running smoothly for years. Your team knows it inside and out. Everything just… works. Why rock the boat with an upgrade? Here’s why: MySQL 8.0 reaches its end-of-life date in April 2026. After this date, there’s no safety net; staying on end-of-life software means you’re taking on all the responsibility […]

If you’re running MySQL 8.0 databases, you need to know this: Oracle will stop supporting them in April 2026. That means no more security patches, bug fixes, or help when things go wrong. Maybe you’re thinking, “But April 2026 feels far away!“. But once that date hits, every day you keep running MySQL 8.0 makes […]

You’ve got a shiny new Percona Monitoring & Management instance standing by and want to move existing users over. This blog is a quick work around for migrating PMM users…

The post How to migrate PMM (Grafana) users first appeared on Change Is Inevitable.

Have you already tried to upgrade the MySQL version of your MySQL HeatWave instance in OCI that is deployed with Terraform? When you tried, you realized, I hope you didn’t turn off backups, that the instance is destroyed and recreated new! This is our current MySQL HeatWave DB System deployed using Terrafrom: And this is […]

The MySQL REST Service is a next-generation JSON Document Store solution, enabling fast and secure HTTPS access to data stored in MySQL, HeatWave, InnoDB Cluster, InnoDB ClusterSet, and InnoDB ReplicaSet. The MySQL REST Service was first released on https://labs.mysql.com in 2023 using MySQL Router. During spring 2025, it was released on MySQL HeatWave and standard […]

When troubleshooting a MySQL crash, having only the error log is rarely enough to pinpoint the exact root cause. To truly understand what happened, we need to go deeper—into the memory state of the process at the moment it crashed. That’s where GDB, the GNU Debugger, comes in. GDB lets us inspect a core dump […]

We all know MySQL InnoDB ClusterSet, a solution that links multiple InnoDB Clusters and Read Replicas asynchronously to easily generate complex MySQL architectures and manage them without burdensome commands. All this thanks to the MySQL Shell’s AdminAPI. This is an example of MySQL InnoDB ClusterSet using two data centers: Let’s explore how we can automate […]

In my previous blog post, Understanding trx-consistency-only on MyDumper Before Removal, I talked about --trx-consistency-only removal, in which I explained that it acts like a shortcut, reducing the amount of time we have to block the write traffic to the database by skipping to check if we are going to backup any non-transactional tables. Now, […]

HeatWave MySQL Database Audit brings powerful enterprise-grade auditing capabilities to the cloud, allowing organizations to monitor and track database activity for security, compliance, and performance optimization. With features like customizable filters, real-time monitoring, minimal overhead, and seamless integration with MySQL tools, it enables administrators to log critical operations, detect threats, and maintain detailed records for regulatory requirements. The audit system is easy to set up, supports granular activity tracking, and provides actionable insights directly through the SQL interface.

The post HeatWave MySQL Database Audit first appeared on dasini.net - Diary of a MySQL expert.

MySQL Analysis: With an AI-Powered CLI Tool

As DBAs with MySQL we often live on a Linux terminal window. We also enjoy free options when available. This post shows an approach that allows us to stay on our terminal window and still use an AI-powered tool. You can update to use other direct AI providers but I set this example up to use aimlapi.com as it brings multiple AI models to your terminal for free with limited use or very low cost for more testing.

Note: I'm not a paid spokesperson for AIMLAPI or anything - this is just an easy example to highlight the idea.

The Problem

You're looking at a legacy database with hundreds of tables, each with complex relationships and questionable design decisions made years ago. The usual process involves:

• Manual schema inspection
• Cross-referencing documentation (if it exists)
• Running multiple EXPLAIN queries
…