Community journal

The latest from the MySQL community

Ideas, releases, practical guides, and perspectives from the people building with MySQL.

Follow the feed
Showing entries 21 to 30 of 45610 « Previous | Next »
Migrating Azure SQL Database to Nutanix Database Service with a Planned Cutover Window

Migrate Azure SQL Database to SQL Server on Nutanix Database Service (NDB) using Azure SQL Data Sync or Azure Data Factory, with a planned cutover and data-integrity checks.

Refresh a single tenant across accounts with Aurora MySQL and Amazon S3

Multi-tenant software as a service (SaaS) applications regularly need to copy one tenant’s data from production into a lower environment. Teams do this to reproduce a defect, validate a schema change, or give quality assurance (QA) a representative dataset. When production and non-production run in separate AWS accounts, their virtual private clouds (VPCs) often have no route to each other. That turns the copy into a networking problem as much as a data problem, and security teams are rightly reluctant to open a path between the two.

In this post, we show how to move a single tenant’s data between Amazon Aurora MySQL-Compatible Edition clusters in two separate AWS accounts, using Aurora cloning, SELECT INTO OUTFILE S3, and LOAD DATA FROM S3. The databases don’t connect directly. Each account reaches Amazon Simple Storage Service (Amazon S3) independently through its own gateway VPC endpoint, and the accounts …

[Read more]
How Oracle changed the future of MySQL: Dominic Preuss on Inside the Silicon Mind

Shopify, GitHub, and Uber run on MySQL, yet, as Dominic Preuss puts it, the hype, innovation, and investment historically went to PostgreSQL. Inside the Silicon Mind published Firas Sozan's interview with Dominic, co-founder and CEO of VillageSQL, about why that happened, what Oracle is doing to address it, and how VillageSQL plans to bring innovation back to MySQL.

Dominic covers how MySQL went from a Swedish startup to Oracle, why Oracle is now opening MySQL development to the community, including AWS and Google, and why he started a company on MySQL when everyone was running in the direction of PostgreSQL.

Watch more VillageSQL talks on the Talks page, or get started at villagesql.com.

Help prevent out-of-memory restarts on Aurora MySQL 8.4

When an Amazon Aurora MySQL-Compatible Edition instance runs critically low on memory, the operating system terminates the mysql process. This drops every connection, rolls back in-flight transactions, and triggers a cluster restart. The instinctive fixes (move to a larger instance, or lower max_connections) treat the symptom, not the underlying memory pressure your workload generates.

Aurora has long included out-of-memory (OOM) avoidance that watches system memory and takes recovery actions before the OS steps in. On Aurora MySQL version 3, use the aurora_oom_response parameter to configure these actions; Aurora provides sensible defaults that you can customize. Aurora MySQL version 8.4 adds a new instance-level …

[Read more]
Diagnose Amazon Aurora MySQL performance using CloudWatch Database Insights

When an Amazon Aurora MySQL-Compatible Edition or Amazon Relational Database Service (Amazon RDS) for MySQL database slows down, it can be hard to tell why. CPU graphs and slow-query logs rarely tell the whole story. The more direct answer usually lies in wait events. A wait event tells you what your sessions are waiting for: reading from storage, redo log flushes, acquiring an internal lock, or waiting for CPU time. Amazon CloudWatch Database Insights surfaces this data as DB load, so you can quickly see whether a database is constrained and, if so, on what.

Earlier MySQL wait-event guidance relied on the Performance Insights dashboard. Our 2018 post …

[Read more]
MySQL Community Spotlight - Omar Farhat

Omar shares how he got started with MySQL, his experience at the contributor summit, and his enthusiasm for replication performance, extensibility, and data interoperability.

DuckDB × MySQL Day: Eight Talks, One Question

For about twenty years people have been asking the same thing about MySQL: can I please just run my reports on it? And for about twenty years the honest answer was “sort of, but you will regret it on a big table”.

On November 17 we are running DuckDB × MySQL Day. It’s a free online conference: one day, eight talks. The agenda was not random. If you read it top to bottom it is basically one long argument.

Heavy MySQL Reports in Seconds: Open Source HTAP with DBTrail and Percona Server for MySQL

In Part 1 we ran analytical reports in DuckDB on a DBTrail copy instead of on MySQL. This time I want to look at a different question: what if the application does not need to know the copy exists?

Most MySQL servers have a few queries that make someone wait. The monthly report that aggregates a whole table. Page 5,000 of a sorted list. The screen that reads years of history. MySQL is built for many small reads and writes, and these queries are a different kind of work.

So what happens to them with DBTrail next to the server? The same 14 reports ran for a day on a Percona Server for MySQL replica and on the copy of the same database that DBTrail keeps.

Short answer: twelve were faster on the copy, and the slowest went from 225 seconds to 7.94 seconds.

Not …

[Read more]
Diagnosing MySQL at Scale (Part 2): Storage Subsystems, Buffer Pool Latches, and Memory Spills

In transactional database systems, the latency gap between memory access (tens to hundreds of nanoseconds) and persistent storage access (tens to hundreds of microseconds for local NVMe devices and milliseconds for remote cloud block storage such as Amazon EBS) spans multiple orders of magnitude. Once a workload exhausts available memory and begins interacting heavily with storage, query response times can deteriorate rapidly.

However, storage-related performance problems in MySQL are rarely solved by simply adding IOPS. In many production incidents, latency originates within the database engine itself:

  • Redo-log checkpoint advancement falling behind incoming write velocity, forcing foreground transactions to participate in synchronous flushing activity ("sync flush").
  • Doublewrite buffering increasing write amplification, contributing to storage-pressure events and …
[Read more]
Releasing iClaustron API, a new Rust NDB API with a C and a Rust API towards RonDB 26.10.0

We have released version 1.0.0 of the iClaustron API. The github tree is at https://github.com/logicalclocks/iclaustron
Training material for Rust is available here
Training material for C is available here

Extensive training material on RonDB is available here

Some takeaways:

1. MIT licensed
2. Receiver thread only routing messages => Scales to 3x more CPUs
3. Capable of doing 9M key lookups per second on a Mac M5 Pro laptop running cluster and API on the laptop
4. Cost of key lookup can be as low as 500ns per row in iClaustron API
5. 0 …

[Read more]