Introducing new MySQL HeatWave features for lower cost and better performance

Time series forecasting is a technique for predicting future values of key metrics based on past events. It involves using time ordered events from past as well as other variables to predict future values. Multivariate time series forecasting can predict multiple time ordered variables, where each variable is dependent on its past value as well […]

MySQL HeatWave on AWS - New and upcoming capabilities in March and April 2023

Machine learning in MySQL HeartWave (aka HeatWave AutoML) offers a fully automated forecasting pipeline that can automatically preprocess, select the best algorithm, and tune its hyperparameters for a given time-series dataset resulting is unmatched model training performance and high forecasting accuracy. There is no additional cost for using machine learning in MySQL HeatWave.

In MySQL Server 8.0.32, Oracle fixed Bug #105761:

“mysqldump make a non-consistent backup with ‐‐single-transaction option” (this commit)

which caused a wave of complaints from users who could no longer do backups with the mysqldump utility because of the lack of the required privileges.

• Bug #109701 “Fix for #33630199 in 8.0.32 introduces regression when ‐‐set-gtid-purged=OFF”
• Bug #109685 “mysqldump has incompatible change in MySQL 8.0.32″

…

You might want to use binlog compression with MySQL/Percona Server for MySQL, but it can come with drawbacks. This article discusses the need for using binlog compression and the potential issues it may cause.

Binlog compression is a technique used to reduce the size of binary log files, which can become quite large over time. This can be especially important in situations where disk space is limited. However, it’s important to be aware that using binlog compression can also cause issues with replication.

Consider the following scenario: you have restored a backup that was taken from a replica node using Percona XtraBackup. Once the restoration is complete, you want to set up replication using the information from the xtrabackup_slave_info …

For this third article of the series dedicated on how a DBA can find the info he needs with MySQL Database Service in Oracle Cloud Infrastructure, we will see how we can find the error log. When using MySQL DBAAS, the DBA doesn’t have direct access to the files on the filesystem. Hopefully, with MySQL […]

The fourth edition of the MySQL Cookbook, solutions for database developers and administrators, Sveta Smirnova, Alkin Tezuysal, O’Reilly, 2022, is a huge book: 938 pages ! And the least we can say is that you get what you pay for ! This book is an excellent resource for anyone working with MySQL, whether you’re a […]

Although MySQL 8 was released back in 2018, a significant share of MySQL servers out there are still running MySQL 5.x. MySQL 5 had a lengthy run from its release in 2005, and thus many organizations still have databases that were built on 5.x. But Oracle has been phasing out MySQL 5.7 support for various platforms over the past few years and end of life for MySQL 5.7 is slated for October 2023. If you’re still running a database on MySQL 5.7, it’s time to seriously consider upgrading. You'll get several new features that give you performance improvements and security enhancements, so it is important that you do this soon — especially with the imminent end-of-life of MySQL 5.7, which means there will be no further security updates. Fortunately, this process is usually pretty straightforward, but there are several changes you may have to make. This article will cover many of the things that you should look out for when upgrading an existing …

Learn what you should look out for when upgrading an existing database from MySQL 5.7 to 8 and how to change your database to be compatible with the new version.