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.

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.

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 …

This article is the second of the new series dedicated on how a DBA can find the info he needs with MySQL Database Service in Oracle Cloud Infrastructure.

The first article was dedicated on Backups, this one is about Disk Space Utilization.

This time we have two options to retrieve useful information related to disk space:

1. Metrics
2. Performance_Schema

Metrics

In the OCI Web Console, there is a dedicated metric for the disk usage:

As for the backup, we can create Alarms for …

New series of articles about how to find useful information when using MySQL Database Service

Running MySQL InnoDB Cluster / Group Replication, there is a transaction size limit (https://dev.mysql.com/doc/refman/8.0/en/group-replication-options.html#sysvar_group_replication_transaction_size_limit)

The default value of "group_replication_transaction_size_limit"  is about 143 MB (150000000 bytes)

How can we determine the size of a batch job (single transaction) in MySQL?

Setting a small value with variable group_replication_transaction_size_limit and running the transaction produces the error message in error log. 

For example :

Assuming there is primary node on port 3310

mysql -uroot -p -h127.0.0.1 -P3310  -e "  set global group_replication_transaction_size_limit=1024;" …

With a special focus on Percona Operator for MySQL

Overview

HAProxy, ProxySQL, MySQL Router (AKA MySQL Proxy); in the last few years, I had to answer multiple times on what proxy to use and in what scenario. When designing an architecture, many components need to be considered before deciding on the best solution.

When deciding what to pick, there are many things to consider, like where the proxy needs to be, if it “just” needs to redirect the connections, or if more features need to be in, like caching and filtering, or if it needs to be integrated with some MySQL embedded automation.

Given that, there never was a single straight answer. Instead, an analysis needs to be done. Only after a better understanding of the environment, the needs, and the evolution that the platform needs to achieve is it possible …

A friend’s application started failing with MySQL causing error about timestamp columns and it needs urgent fixing from the database side. A timestamp column was not accepting the null values…

The post MySQL 8 – timestamp cannot be null and explicit_defaults_for_timestamp first appeared on Change Is Inevitable.