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

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.

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.

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.

WePay, the integrated payments arm of JPMorgan Chase, has taken significant strides to enhance its database infrastructure by upgrading to MySQL Enterprise Edition. For businesses looking to optimize their payment infrastructure, the journey of WePay serves as an insightful case study on leveraging advanced database solutions for maximum uptime and security.

We already have blog posts about Dual Password in MySQL from Brian Sumpter – Using MySQL 8 Dual Passwords, and from Marco Tusa – MySQL Dual Passwords – How To Manage Them Programmatically Let’s skip the details about dual passwords and focus on tracking password usage. How can we be sure that we are using […]

MySQL 8.3 introduced a new JSON format for EXPLAIN reflecting how the execution plan actually is built, allowing for programmatic analysis of plans and executions.

We have documented streaming replication, and we have also mentioned how you can use streaming replication, and we also once did a webinar with recording on it, and we wrote a very in-depth blog post on how to use streaming replication to manage large transactions with Galera Cluster.

However, we had a question recently about streaming replication around the usage of wsrep_trx_fragment_unit and wsrep_trx_fragment_size (also, well …