Haven’t actually tried this yet, but it’s worth keeping in mind for later.

This is going to make me sound like an old man (OK, right, I am old. So, suck it.), but these two posts alternately scare me and let me know that I’ll have work going into the future as a DB developer. In the first post, Chris Moos describes a problem he’s having with queries [...]

This is awesome! We’ve been having multiple issues with data loads recently. Especially one file we get monthly, which is not very wide (few columns, with small data types), but has over 27 millions rows. Even though our server is now huge, and I split the file into 7M row files, one of the “chunks” [...]

Our tables have gotten large enough that it takes hours to do an alter table. So, this could be a very good thing. It doesn’t relieve any of the issues dealing with the table being locked during this time, but at least we’ll know how much longer it will be locked. Makes me wonder if [...]

Despite the title, this post only describes one scenario: that where you need to skip one (or possibly more) queries on the slave in order for replication to restart. Still, this has come in handy recently. Here’s the money section: Just to go sure, we stop the slave: mysql> STOP SLAVE; Fixing the problem is [...]

Looks like an awesome site, full of a lot of information on MySQL performance. Both writers, Peter Zaitsev and Vadim Tkachenko, worked with MySQL in their Performance Group. Includes presentations given at various conferences, and results of various tests, including this one showing performance benchmarks between InnoDB, MyISAM and Falcon (MySQL’s new storage engine – [...]

In order to get data from the MySQL command line output to a file, at the MySQL prompt, use:mysql> pager cat > /path/to/file/filenameat the file system, use:$ mysql …

This article is pretty basic and not really worth linking on its own, but it is worth watching this series, especially the last two articles, as there may be some interesting stuff there.

The actual title of this is “Managing Hierarchical Data in MySQL”, but there’s no reason why this wouldn’t work in any other relational db (except of course, some of the sql examples).I’ve also made a pdf of this, just in case MySQL decides to remove it for some reason.

This backs up database-name to output-filename with no create database or table statements. Does not put the statements in any particular order so should add set foreignkeychecks=0; to top of output-filename.