(Paul Namuag) We discussed in our previous blogs about the MySQL-related dashboards. We highlighted the things that a DBA can benefit from by studying the graphs, especially when performing their daily routines from diagnostics, metric reporting, and capacity planning.

Schema change is one of the crucial tasks in MySQL with huge tables. Schema change can cause locks.

(Yves Trudeau) Very often, database performance is affected by the inability to cache all the required data in memory. Disk IO, even when using the fastest devices, takes much more time than a memory access.

(Valentine Oleka) If the first time you heard this phrase “parent-child relationship in MySQL”, you went “Ok, anyone else got cool made up names or are we to start brainstorming now”, then this article is for you.

(Maria Couceiro) MySQL 8.0.13 improves replication lag monitoring by extending the instrumentation for transaction transient errors.

(Keith Hollman) So, if we’re applying GDPR to our system, and we’re already making use of MySQL Transparent Data Encryption / keyring, then here’s an example on how to migrate from filed-based keyring to the encrypted keyring. Online.

(Przemys³aw Malkowski) Probably not well known but quite an important optimization was introduced in MySQL 5.6 – reduced overhead for “read only transactions”.

(Jesper Krogh) Since MySQL 5.6, the digest feature of the MySQL Performance Schema has provided a convenient and effective way to obtain statistics of queries based on their normalized form.

(Fernando Laudares Camargos and Trey Raymond) The release of MySQL 8.0 has brought a lot of bold implementations that touched on things that have been avoided before, such as added support for common table expressions and window functions.

(Bhuvanesh) We recently moved an On-Prem environment to GCP for better scalability and availability.