Sveta Smirnova

It often looks like everyone loves AI. Everyone also seems worried about AI. Some will even be wondering if those two consecutive short sentences show that this text was written by AI. It wasn’t.

Many database professionals know only one way to install MySQL: using a system package manager. While this approach works for production environments, it limits experimentation and makes it difficult to safely test configuration changes, compare MySQL versions, or reproduce production issues.

MySQL Cookbook 4th edition is planned to be released this spring. I am one of the authors of the book and will show you how to "cook" MySQL. I will show you a few tasks with different priorities, such as JSON in MySQL for those who need flexibility; modern SQL for analytics, and Group...

MySQL performance can be improved by tuning queries, server options, and hardware. Traditionally it was an area of responsibility of three different roles: Development, DBA, and System Administrators.

It is common knowledge that built-in asynchronous master-master (active-active) replication is not safe. I remember times when the official MySQL User Reference Manual stated that such an installation is not recommended for production use.

We store data with an intention to use it: search, retrieve, group, sort... To do it effectively, the MySQL Optimizer uses index statistics when it compiles the query execution plan. This approach works excellently unless your data distribution is not even.

Born in 2010 in MySQL 5.5.3 as "a feature for monitoring server execution at a low level," grown in 5.6 times with performance fixes and DBA-faced features, in MySQL 5.7 Performance Schema is a mature tool, used by humans and more and more monitoring products. It becomes more popular over the years.