(Morgan Tocker) I occasionally get in to light arguments healthy discussions with students about whether or not to use Foreign Key constraints on InnoDB tables. My standard response has always been: “it depends on how much of a tradeoff you are willing to make for performance. In some situations th

(Shinguz) We recently had the case with one of our customers where we got externally generated random hash values (up to 70 bytes) and they were used as Primary Keys in InnoDB.

(Baron Schwartz) Here’s a little trivia that you might find helpful. Suppose that I have the following in the MySQL slow query log (abbreviated for clarity):

(Mikael Ronstrom) In our work to improve MySQL scalability we tested many opportunities to scale the MySQL Server and the InnoDB storage engine. The InnoDB buffer pool was often one of the hottest contention points in the server. This is very natural since every access to a data page, UNDO page, ind

(Sean Hull) The MySQL Binary Log files are important to the proper functioning of the database and facilitate replication, and recovery. This article discusses some of the inner workings of these important files, and explains how ordering of transactions also plays into how they work.

(Kedar) Recently I saw a MySQL Stored Function requirement on Experts-Exchange for converting date into some specific words format.

(Mark Callaghan) This provides more documentation for Online Schema Change (OSC) beyond part 1.

(David Fetter) Graphs? In Databases? Yes, you can! To do graphs in SQL, we need nodes and edges. One common mistake we’ll avoid is to lump the nodes and edges into a single table. I’ll get into just why this is a mistake later, but let’s just take it as a given for now.

(Mark Callaghan) It is great to be able to build small utilities on top of an excellent RDBMS. Thank you MySQL.

(David Christensen) Nothing strikes fear into the heart of a DBA like error messages, particularly ones which indicate that there may be data corruption. One such situation happened recently to us, when we ran into a recent unusual situation in an upgrade to PostgreSQL 8.1.21. We had updated the sof