(Xaprb) In part 1 of this series I examined the behavior of MySQL’s FEDERATED storage engine by running queries with the general query log enabled on the remote server. In this article I take a higher-level view. I summarize my findings from the first article, then give my thoughts on the engine’s s

(Matt Asay) MySQL made two major announcements today. One reflects a fundamental change in the database industry. The second is intended to cement that change forever.

(Melonfire) Most server administrators know that the MySQL relational data base management system (RDBMS) is a highly flexible piece of software and comes with a wide range of startup options that can be used to modify its behavior. What most don’t know, however, is that the standard MySQL client co

(Xaprb) MySQL’s FEDERATED storage engine is a fascinating example of the flexibility gained by abstracting the storage engine layer away from the rest of the server. FEDERATED tables allow you to access a table on another server as though it exists on the local server. However, the manual doesn’t sa

(Vincent Danen) MySQL is a database that is synonymous with ease-of-use, and most database-driven Web applications use it as their database of choice. Because of this, MySQL is used on many Web servers. While the MySQL command line tool is useful, unless you know all the ins and outs of SQL syntax,

(Sergey Petrunia) Working on subquery optimizations, got an idea how to speed up join execution a little. Read on.

(Il Corra) Answering yesterday to some newsgroup question about MySQL I have answered about the problem of the full-text searches in natural language.

(Xaprb) MySQL has no built-in functionality to calculate a table’s checksum in any storage engine but MyISAM. Table checksums can confirm that two tables are identical — useful to verify a slave server is in sync with its master (see my article on reliable MySQL replication for more). Fortunately, i

(Domas Mituzas) One of MySQL features I usually like to exploit is covering index. Simply, if all fields required for a query are contained in an index, there’s no need to access table row somewhere else. In MyISAM that would mean not going to MYD file. Inside InnoDB data is clustered together with

Late in 2006 MySQL decided to move to a split distribution model, Community and Enterprise. A lot has (apparently) changed since then, yet nothing has really changed since then.