Sometimes it’s convenient to retrieve the user creation statement and to copy it to another server.

However, with the new authentication method used as default since MySQL 8.0, caching_sha2_password, this can become a nightmare as the output is binary and some bytes can be hidden or decoded differently depending of the terminal and font used.

Let’s have a look:

If we cut the create user statement and paste it into another server what will happen ?

We can see that we get the following error:

ERROR: 1827 (HY000): The password hash doesn't have the expected format.

How could we deal with that ?

The solution to be able to cut & paste the authentication string without having any issue, is to change it as a binary representation (hexadecimal) like this:

And then replace the value in the user create statement:

But there is an easier way. MySQL …

Here comes the success story of Specialized Media Dashboard, a project that comprises an open-source media monitoring system. The specialized media in question encompasses the spheres of journalism, law enforcement, and climate change.

The post Case Study: How the Engineers of SMD Found a Way to Process Millions of Database Records Faster With dbForge Studio for MySQL appeared first on Devart Blog.

Find the official MySQL container image in the Oracle Container Registry

If you are deploying MySQL on containers, one of the first tasks is to find the right image.

There’s a certain amount of confusion, especially when we’re trying to help someone who’s having problems with their deployment.

For example, when people say I’m using the official docker image… what does that really mean?

Docker Hub, provides their official image (https://hub.docker.com/_/mysql), but this is not the official MySQL image that we, the MySQL Team at Oracle, support.

Before the mess with Docker Hub ([1], [2], [3]), the real official images for MySQL …

By integrating MySQL database migrations into your testing process, you can not only ensure your testing database is up to date with the most recent changes, but you can also test that the migrations themselves are performing as expected. In this post we will walk you though how to incorporate migrations with Knex and run those migrations on your test database being run in Testcontainers.

We now added a new automated capability (AutoLoad) to MySQL Autopilot – Auto Load & Auto Unload which continuously monitors workload run in MySQL and use machine learning model to predict the queries that can offload to HeatWave for query acceleration. Based on the list of queries, the new AutoLoad dynamically loads or unloads tables to HeatWave cluster.

We are excited to introduce the JSON support in HeatWave which offers significant performance improvement with no change in applications, or no indexes needed for accelerating JSON processing. This provides significant enhancement for applications that heavily rely on JSON data structures, as query execution times are now drastically reduced, improving overall application performance.

As a MySQL database administrator, you’re likely familiar with the SHOW REPLICA STATUS command. It is an important command for monitoring the replication status on your MySQL replicas. However, its output can be overwhelming for beginners, especially regarding the binary log coordinates. I have seen confusion amongst new DBAs on which binary log file and position represent what in the replication.

In this guide, we’ll simplify the SHOW REPLICA STATUS output, focusing on the critical binary log coordinates essential for troubleshooting and managing replication.

The key binlog coordinates

Before we delve into the output, let’s understand the key binlog coordinates we’ll be working with:

• Master_Log_File: This is the name of the primary binary log file that the I/O thread is currently reading from.
• Read_Master_Log_Pos: It represents the …

To mark the 3rd day of Oracle CloudWorld 2023, Oracle announced significant enhancements to MySQL HeatWave. Hear what leading Industry Analysts have to say about the latest Vector store and generative AI innovations.

If you’re a DBA, one of your “easiest” tasks is to stop/start MySQL during a maintenance window, but even that could lead to unwanted scenarios if you modify some dynamic parameters at some point in your instance.

Here’s a brief story of how this could happen, to make it clearer:

You’re a DBA managing a few MySQL servers. The application using one of them starts having issues on a Friday night, right before it’s time to leave; after a quick check, you notice the app is requesting more connections, and the hotfix is to up max connections; you change them dynamically, the fire is off, and so are you. Let your future self worry about finding the root cause and fixing it properly the following Monday.

But life happens; Monday is here with new challenges, and you already forgot about the connections issue… A few months later, a restart for MySQL is required, and surprise, surprise, right after …