I have been scratching my head about MySQL startup for some time.  There is much to say about this, and many other posts will probably follow.  For now, it is enough to know that with many tables (millions) the startup of MySQL 8.0+ (including 8.0, 8.4 and 9.0) is suboptimal (to say the least).  With very little changes, I was able to speed it up, from 2:39 to 1:09 (1 minute and 9

The aim of this long article is to give you the instructions and tools to migrate your production database, from your current environment to a solution based on Percona Everest (MySQL).

Nice, you decided to test Percona Everest, and you found that it is the tool you were looking for to manage your private DBaaS. For sure the easiest part will be to run new environments to get better understanding and experience on how the solution works. However, the day when you will look to migrate your existing environments will come. What should you do?

Prepare a plan! In which the first step is to understand your current environment. 

 When I say understand the current environment, I mean that you need to have a clear understanding of:

• the current dimensions (CPU/Memory/Disk utilization)
• the way it is accessed by the …

The aim of this long article is to give you the instructions and tools to migrate your production database, from your current environment to a solution based on Percona Everest (MySQL).

Nice, you decided to test Percona Everest, and you found that it is the tool you were looking for to manage your private DBaaS. For sure the easiest part will be to run new environments to get better understanding and experience on how the solution works. However, the day when you will look to migrate your existing environments will come. What should you do?

Prepare a plan! In which the first step is to understand your current environment. 

 When I say understand the current environment, I mean that you need to have a clear understanding of:

• the current dimensions (CPU/Memory/Disk utilization)
• the way it is accessed by the …

 Check and review recommended MySQL InnoDB setting using MySQL Shell for optimal Performance. 

Performance of MySQL is always top priority for each organisations because data holds valuable insight into organizational productivity and proactive decision making. High-performing databases help organizations stay ahead by enabling faster insights, quicker adaptation to changes, and superior customer experiences. When performance of MySQL is slow it impacts user experience and data driven innovation. 
Performance has different meaning at different context however it’s important to keep MySQL instance healthy by balancing the hardware vis-à-vis InnoDB settings. 
I have been asked multiple times by MySQL customer about 

1. Does MySQL has right set of InnoDB configurations ? 
   
2. What are the InnoDB parameters to tune …

Mysterious warning Recently, I was involved in an investigation whose goal was to find out the reason for a warning message like this: [crayon-6790b5b2ced83782454901/] The message looks clear, isn’t it? Well, the problem was that this particular table had not been changed for years, and so no DDL (ALTER) query was involved here. Moreover, there […]

This post will explain how to troubleshoot MySQL HeatWave by accessing information in the MySQL error log table and the HeatWave audit log.

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.

MySQL Shell offers a wide variety of tools to manage our MySQL instances. With all those tools, though, we may want functionality that would be helpful and pertain to just your situation. Thankfully, the MySQL Shell team made it possible to extend MySQL Shell and add functionality. In this post, we will explore the use of […]

With the new release model supporting LTS (Long Term Support) releases, a given MySQL server will fall into one out of two categories:  This blog post will explain how to determine whether a given MySQL server is an LTS release or not. Defining release type The MySQL server source code repository contains a file called […]

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.