News
Entertainment
Science & Technology
Life
Culture & Art
Hobbies
News
Entertainment
Science & Technology
Culture & Art
Hobbies
Let's stay a bit longer with MySQL 3.2x to advance the MySQL Retrospective in anticipation of the 30th Anniversary. The idea of this article was suggested to me by Daniël van Eeden. Did you know that in the early days, and therefore still in MySQL 3.20, MySQL used the ISAM…
To further advance the MySQL Retrospective in anticipation of the 30th Anniversary, today, let's discuss the very first version of MySQL that became availble to a wide audient though the popular InfoMagic distribution: MySQL 3.20! In 1997, InfoMagic incorporated MySQL 3.20 as part of the RedHat Contrib CD-ROM (MySQL 3.20.25).…
This article builds upon the concepts introduced in my previous blog posts, HeatWave GenAI: Sentiment Analysis Made Easy-Peasy, HeatWave GenAI: Your AI-Powered Content Creation Partner, In-Database LLMs for Efficient Text Translation with HeatWave GenAI and HeatWave GenAI: Sentiment Analysis Made Easy-Peasy.For a deeper understanding, also consider reading these articles. This tutorial explores HeatWave GenAI, a cloud
Last month we released MySQL 9.1, the latest Innovation Release. Of course, we released bug fixes for 8.0 and 8.4 LTS but in this post, I focus on the newest release. Within these releases, we included patches and code received by our amazing Community. Here is the list of contributions…
With multi-threaded replication (MTR), a replica can commit transactions in the same order as the source, or not. This is determined by sysvar replica_preserve_commit_order (RPCO). As of MySQL v8.0.27 (released October 2021) it’s ON by default, but it was OFF by default for several years prior. In either case, it’s relatively new compared to 20+ years of single-threaded replication for which commit order was not an issue or option. But with MTR, it’s important to understand the affects of RPCO, especially with respect to the focus of this three-part series: replication lag.
We can use so many different observability tools to get notifications, alerts, react, generate reports, etc. from so many different companies, using agents, proxies, repositories, and so on and so forth. And after exchanging experiences with dolphie's author himself, Charles, the idea here is to go that little bit further in monitoring MySQL.
Learn different ways to rename tables in MySQL, from the RENAME TABLE query and ALTER TABLE statement to tools like MySQL Workbench and dbForge Studio. Includes step-by-step instructions for renaming tables in phpMyAdmin, with tips for avoiding downtime and precautions to take before renaming.
Don’t have time to read Efficient MySQL Performance? Here’s the book (10 chapters) in one-liners. Performance is query response time. Proper left-most indexing is required for performance. The less data, the better. Access patterns (part of the workload) help or hinder performance. Sharding is how to scale writes when single-node performance is truly reached. Server metrics reflect how the app workload causes MySQL to work. Replication lag is data loss. Locks are held until a transaction commits, so commit quickly. There are many other challenges that you might need to address—sorry. MySQL in the cloud is slower and more expensive, so performance is more important than ever.
For people to prepare for their travel to Belgium, we want to announce that the preFOSDEM fringe event known as the MySQL Belgian Days will take place the Thursday and Friday, January 30 and 31, before FOSDEM.