dasini.net – Diary of a MySQL expert

If you have (too) long running select queries it is probably because of lack of relevant indexes, problematic schema that lead to poor queries or inadequate hardware.

That said, sometime even if you doing it right, the query execution time could be too long regarding of what the application or your users expect. It is often true for reporting, real time analytics or BI queries.

At Oracle we have developed Heatwave, that allow you to easily run high performance analytics against your MySQL database.

To be more precise, Heatwave is a massively-scalable integrated analytics engine for MySQL Database Service (MDS), the MySQL DBaaS in Oracle Cloud Infrastructure (OCI).

Some key points of Heatwave:

– Single MySQL database for OLTP & analytics applications
– All existing applications work without any changes
– Extreme performance:
+ 400x faster than MySQL, scales to thousands of cores
+ 1100x faster than Amazon
Aurora
+ 2.7x faster than Amazon Redshift

Since MySQL 8.0.22 there is a mechanism in asynchronous replication that makes the receiver automatically try to re-establish an asynchronous replication connection to another sender, in case the current connection gets interrupted due to the failure of the current sender.

Dual-password capability makes it possible to seamlessly perform credential changes without downtime.

DBA can configure user accounts such that too many consecutive login failures cause temporary account locking.

MySQL 8.0 has introduced an optional behavior that authorize users to change their password only if they could provide the current password.

MySQL provides password-reuse capability, which allows database administrators to determine the number of unique passwords a user must use before they can use an old password again.

MySQL provides password-expiration capability, which enables database administrators to require that users reset their password.

MySQL has the capability of generating random passwords for user accounts, as an alternative to requiring explicit administrator-specified literal passwords.

Up to MySQL 8.0.16, to perform these tasks you could:
– Use MySQL Enterprise Backup :
– Use mysqldump

Starting with MySQL 8.0.17, the easiest and recommended method is to use the CLONE feature.

Like I stated in my previous article – MySQL InnoDB Cluster – Recovering and provisioning with mysqldump :
“As the administrator of a cluster, among others tasks, you should be able to restore failed nodes and to add (or remove) new nodes”.
Well, I still agree with myself 🙂
MySQL customers using a Commercial Edition have access to MySQL Enterprise Backup (MEB) which provide enterprise-grade physical backup and recovery for MySQL.
MEB delivers hot, online, non-blocking backups on multiple platforms including Linux, Windows, Mac & Solaris.