This blog post will explain how to tell whether a given MySQL server is an LTS release or not. The features described are implemented in MySQL 8.4.0 (the mysql_upgrade_history file) and 8.4.1 (the INFO_SRC extension). The features are available in on-premise as well as cloud releases.

I thought I’d share some quick intro steps into how we can monitor the MySQL Router.

This can be useful if we’re observing intermittent outages, network packet drops or you’re just not sure if everythings fine in your MySQL InnoDB Cluster.

My scenario: The drupal servers are connecting and sometimes the users are getting connection errors. I don’0t see anything at MySQL server level of any instance nor cluster problem. Let’s review the Routers.

On all MySQL Router servers, double check the config file for the log location and also the log level. At /etc/mysqlrouter/mysqlrouter.conf (default rpm install location):

[DEFAULT]
name=myrouter
user=mysqlrouter
..
..
logging_folder=/routerlog/log
..
[logger]
level=DEBUG
#level=INFO

I’ve changed my logger level to DEBUG which will give you a lot more info about connections and counters so you can see what’s happening …

We recently conducted a survey of how Vitess is being used by the community. This blog post summarizes what we learned. "Vitess solves an existential threat for services which outgrow a single MySQL database." "Horizontal sharding helps us scale quickly, and the new generation execution plan, Gen4, enables us to support more SQL queries." "Vitess has allowed us to scale and step away from our dev-ops role, allowing us to focus on higher level and higher impact tooling and automation.

At Oracle CloudWorld, several HeatWave sessions feature customers who will share their experience using HeatWave MySQL, HeatWave GenAI, HeatWave AutoML, or running HeatWave on AWS. Check out the sessions and add them to your schedule.

At Percona, we have always prioritized database performance as a critical factor in selecting database technologies. Recently, we have observed a concerning trend in the community edition of MySQL, where performance appears to be declining across major releases, specifically MySQL versions 5.7, 8.0, and 8.4. If you’re interested in learning more about these observations, we […]

Stewardship of a community is easy for new and emerging technology. After 29 years, MySQL has become one of the most-used and trusted open-source databases by millions of users worldwide.

MySQL Shell offer many features to make life easier for DBAs and developers. In this post we discuss how we can add custom functionality to MySQL Shell using startup scripts.

This post will explain how you can start and stop your MySQL Heatwave and compute instances from the command line using Oracle's Command Line Interface tool.

We are excited to announce that Vitess now supports recursive Common Table Expressions (CTEs), marking another significant step in our journey to fully align with MySQL’s capabilities. Recursive CTEs, often a critical feature for complex query handling, allow for the execution of recursive queries within a single CTE. This addition brings more flexibility and power to developers using Vitess, especially those working with distributed databases. One of the key challenges in implementing recursive CTEs within a sharded environment is managing the distribution of data across multiple shards.

A work-around for partitioning MySQL tables with foreign keys is described in this article.