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.

Machine learning has become pervasive, and businesses are scrambling to introduce machine learning and AI based functionality in their products. The biggest challenge is shortage of people with technical knowledge to deliver a machine learning based project. Now, with the interactive console for machine learning in MySQL HeatWave (aka MySQL HeatWave AutoML), even business analysts […]

Interactive console for MySQL HeatWave is an integrated environment which provides users the ability to manage the database schema objects, run interactive queries, monitor performance, and use machine learning capabilities such that a business analyst can easily develop applications, manage data objects, and machine learning models.

MySQL HeatWave on AWS – New and upcoming capabilities in March and April 2023   HeatWave Scale Out Data Management MySQL HeatWave on AWS now provides an optimized storage layer built on S3 to store the HeatWave in-memory hybrid columnar representation of the data. This allows data to be reloaded to each HeatWave node independently […]

Introducing new MySQL HeatWave features for lower cost and better performance   Customers with various sizes of workloads want to use MySQL HeatWave for query acceleration. MySQL HeatWave is addressing the wide spectrum of MySQL workloads with the following new features: HeatWave can now address workloads from less than 50GB to 64TB with the best […]

At the MySQL Summit Day in Redwood Shores, California, we’re announcing new MySQL HeatWave AutoML capabilities, expanding the machine learning use cases for MySQL HeatWave, as well as new capabilities for MySQL HeatWave on AWS, and price-performance improvements for MySQL HeatWave on OCI. New MySQL HeatWave AutoML capabilities MySQL HeatWave provides native, in-database machine learning. […]

March 23, 2023. MySQL Summit, Redwood Shores, CA. Oracle announces new MySQL HeatWave AutoML capabilities, expanding the machine learning use cases for MySQL HeatWave, as well as new capabilities for MySQL HeatWave on AWS, and price-performance improvements for MySQL HeatWave on OCI.

Greetings everyone!!!!!

Let’s begin the phase II of our blog on Aurora serverless-V2.

Part 1 – https://mydbops.wordpress.com/2022/05/22/exploring-auAurora-serverless-v2-for-mysql

Here, I have focused primarily on the migration strategies, hence this blog will be helpful for those who are in a stance to migrate towards serverless V2.

Before entering into the migration strategies, let’s take a look at the feature called “Mixed-Configuration”. and then discuss about the migration strategies

1. Mixed-Configuration: …

In this blog, I’ll discuss the use case for replication. We want to improve our ability to replicate your data and limit replication to row-based events securely, wherein we do not have control over the source(s).

The replica doesn’t have checking capabilities when processing replicated transactions as of MySQL 8.0.18. It does this to carry out all instructions from its upstream. The replica must impose data access limitations on the replicated stream because changes may get past the security barrier separating the source and replica in some configurations. In that situation, implementing the upstream changes in a more constrained security context is beneficial to organizations needing privilege-controlled aggregate data from multiple separate databases.

In MySQL 8.0.18, a new feature PRIVILEGE_CHECKS_USER is introduced in replication channels. When a PRIVILEGE CHECKS USER account is used, a replication channel is more protected …