A single hour of downtime costs companies an average of $300,000, with critical systems like databases bearing the brunt of this risk. MySQL, widely used for managing essential data, requires high availability (HA) solutions to maintain smooth uptime and avoid disruptions that can lead to financial loss or reputational damage. 

Ensuring the continuous availability of MySQL databases is essential, especially when handling high transaction volumes. ProxySQL, a powerful middleware, provides advanced support on techniques ranging from replication to clustering that assist with MySQL high availability. 

These techniques minimize vulnerabilities, improve fault tolerance, and keep systems running smoothly, even during failures or …

I’m just trying out the v8.4 Read-Write configuration for MySQL Router, that comes default in the community edition and, as they say, TL;DR “it’s default upon bootstrap”.

What does this mean and how can I go about it?

The overview is simple:

• Either install or upgrade your existing MySQL Router to v8.4 at least.
• Bootstrap the Router.
• Use the port 3310 or change it to fit your needs.

Let’s get to it:

Stop your running router:

systemctl stop mysqlrouter

Copy the old config, just in case:

cp /etc/mysqlrouter/mysqlrouter.conf /etc/mysqlrouter/mysqlrouter_v80.conf

I normally keep my mysql linux repository disabled so no “yum update” takes over version control and gives me a nasty surprise afterwards. As so, I uncomment the “mysql” entry:

vi /etc/yum.conf …

When working with MySQL databases, you may encounter the need to change a database name. However, MySQL no longer supports a direct renaming option. The RENAME DATABASE command, available in earlier versions, was removed due to the risk of data loss. Despite this, renaming a database in MySQL is still possible. This article explores the […]

The post How to Rename a MySQL Database appeared first on Devart Blog.

TL;DR ALTER TABLE and OPTIMIZE TABLE on an InnoDB table, which rebuilds the table without blocking concurrent changes to it (i.e., executed using INPLACE algorithm) and concurrent DML or purge activity on the table can occasionally lead to two significant problems: ALTER/OPTIMIZE TABLE failing with an unnecessary duplicate key error (even though there are no […]

In the last weeks / months, I have been working on understanding / improving MySQL startup with many tables.  I already wrote five posts on the subject, they are listed below.  In this post, I use the knowledge we gained in the previous two posts to show the interest of tuning InnoDB Tablespace Duplicate Check Threads, making startup 30% in one case (2:28 vs. 3:33) and 5% in

Codership is pleased to announce a new Generally Available (GA) release of the multi-master Galera Cluster for MySQL 8.0, consisting of MySQL-wsrep 8.0.40-26.21 (release notes, download), with Galera replication library 4.21 (release notes, download) implementing wsrep API version 26. It also includes Galera Cluster for MySQL 8.4, consisting of MySQL-wsrep 8.4.3-26.21 (release notes, …

For the third day of our Advent Calendar of Content, we bring you a summary of all the MySQL Shorts that are focussed on HeatWave MySQL

With the successful deployment of MySQL Enterprise Edition, Lina One has improved telemarketing productivity across its call centers and set a new standard for efficiency and security in the insurance industry. Read the blog.

Tagging is an essential practice in managing and organizing cloud resources. In Oracle Cloud Infrastructure (OCI), tagging is an integral part of the OCI Identity and Access Management service(IAM) which provides a systematic way to categorize and manage resources effectively, such as cost tracking, cloud resource searching, filtering and logical organization.

In this blog post, we will explore how to use cost tags to correlate the cost associated with a particular HeatWave MySQL DB System.

MySQL 8.4 and newer have extended the Global Transaction ID (GTID) functionality with a new “tag” option.

Refresher on GTID

A GTID is a unique ID that is assigned to a transaction. This is used if gtid_mode is set to ON. The benefit of this is that a transaction can be uniquely identified in a MySQL replication setup with multiple levels. Among others this makes it easier to refactor a replication tree as a MySQL replica knows which transactions it has seen and can use this to find the right position to start replicating from a new source.

The format of GTIDs is documented here.

Before GTID was used replication worked based on a file and offset (e.g. file=binlog.000001,offset=4), which is unique to every server.

A GTID without tag looks like …