(Sven Sandberg) MySQL is not only a relational database, but can also be used as a schemaless/NOSQL document store, or a mix of both. This is realized by the JSON datatype, and is useful for any data that is hard to fit in the ”tabular” format of a traditional table.

(Frederic Descamps) In MySQL 8.0, we have now a new way of storing tables definitions: the Data Dictionary !

(Frederic Descamps) Now that MySQL is upgraded to 8.0 RC1, let’s have a look on how we could check the workload and see if we can optimize something by adding indexes for example. The same technique can be used to find inefficient queries requiring rewriting.

(Marcelo Altmann) In this blog, I’ll look at how to do MySQL point in time recovery (PITR) correctly.

(João Gramacho) MySQL 8.0.1 introduced a work with replication threads mutexes in order to improve performance. In MySQL 8.0.2 the same work was extended, focusing in usability, and revamped how replication deals with disk-full conditions, improving the responsiveness of both monitoring commands and

(Ståle Deraas) The new data dictionary in MySQL 8.0 is mostly transparent to users upgrading, in that an import process is automatically run on first-start, and the semantics of DDL (creating tables, adding indexes etc) remain the same.

(Peter Zaitsev) In this blog post, I’ll provide some guidance on how to choose the MySQL innodb_log_file_size.

(Shree Nair) As tables increase in size and more and more users come online, it becomes increasingly necessary to fine-tune your database server from time to time. The secret to knowing what adjustments need to be made is to perform regular monitoring. Most databases offer dozens – if not hundreds –

(Vlad Mihalcea) Although there is an SQL Standard, every relational database is ultimately unique, and you need to adjust your data access layer so that you get the most out of the relational database in use.

(Sheeri K. Cabral) subtitle: How to use awk to filter binlogs for specific tables