The latest from the MySQL community

In the last weeks / months, I have been working on understanding / improving MySQL startup with many tables.  I already wrote two posts on the subject, the links are below.  So far, I did not share what brought my attention to this, and it is the subject of this post.  Also, and because it is related, I come back to the optimization / contribution I already made on

In this post I will talk about release management with MySQL as example. Release management has to do with what to put in a release, how often to do a release, how to long to support a release and how to number or name the releases.

The early years

Today software is almost exclusively delivered over the internet, but this didn’t use to be the case. Software used to be delivered in a box that you had to buy at a physical store. These were often shrink wrapped and forced you to agree with the EULA by opening the box. The box then contained floppies, CD’s, DVD’s or any other suitable medium.

There were multiple reasons why physical media were used, even when the internet arrived. One of the main limitations was bandwidth, this is also why FreeBSD, Linux, etc were sold on physical media. And one of the other reasons was that online payment wasn’t as ubiquitous as it is today. Then there were also ways of copy …

Don’t have time to read Efficient MySQL Performance? Here’s the book (10 chapters) in one-liners.

1. Performance is query response time.
2. Proper left-most indexing is required for performance.
3. The less data, the better.
4. Access patterns (part of the workload) help or hinder performance.
5. Sharding is how to scale writes when single-node performance is truly reached.
6. Server metrics reflect how the app workload causes MySQL to work.
7. Replication lag is data loss.
8. Locks are held until a transaction commits, so commit quickly.
9. There are many other challenges that you might need to address—sorry.
10. MySQL in the cloud is slower and more expensive, so performance is more important than ever.

Read on to learn about how to connect PHP with a MySQL database using different methods, including mysqli, PDO, and dbForge for MySQL.

The post How to Connect PHP With MySQL appeared first on Devart Blog.

Before MySQL 9.2.0 only users with the SUPER privilege were allowed to create or modify spatial reference systems (SRSs). That was inconvenient, especially for HeatWave MySQL where typically users do not have the SUPER privilege. MySQL 9.2.0 changes that by introducing a new dynamic privilege: CREATE_SPATIAL_REFERENCE_SYSTEM. This privilege enables users to create, replace, and drop […]

Hello, readers! I’m excited to announce the launch of my latest project: a dedicated MySQL Podcast! As a long-time MySQL enthusiast with extensive hands-on experience in database management, I understand…

The post MySQL Podcast – Practical Learning & Training first appeared on Change Is Inevitable.

Cloud-based database hosting seems to be an extremely viable solution for modern apps. After all, the entire management-and-maintenance thing is relegated to the hosting provider, scalability is not an issue, and you are free to focus on product development as you see fit.

The post Top MySQL Hosting Providers in 2024 for Reliable Database Management appeared first on Devart Blog.

Introduction   MySQL system variables configure the server’s operation, and the SET statement is used to change system variables. The MySQL SET statements have various options for specifying how and when changes are made to system variables. It’s important to understand how these changes are reflected in current sessions (connections), later sessions, and after database […]

MySQL system variables configure the server's operation, and the SET statement is used to change system variable. The MySQL SET statements have various options for specifying changes to SYSTEM VARIABLE. It’s important to understand how these changes are reflected in current sessions (connections), later sessions, and after database server restarts.

Introduction # In this blog post, we will discuss an example of a change to the Vitess query planner and how it enhances the optimization process. The new model focuses on making every step in the optimization pipeline a runnable plan. This approach offers several benefits, including simpler understanding and reasoning, ease of testing, and the ability to use arbitrary expressions in ordering, grouping, and aggregations. Vitess distributed query planner # VTGate is the proxy component of Vitess.