I'll present a session on the innotop MySQL and InnoDB monitoring tool at 2007 MySQL Conference and Expo in a couple of weeks.

The innotop session will focus on using innotop's basic and intermediate-level features. I'll demonstrate how to install it and get the initial configuration set up. I'll show you what innotop is good at doing, and how to do some of the things I do frequently, such as watch queries, check replication status, and look at what transactions are currently open. And I'll demonstrate some of innotop's many small features that can help you use it to watch and control your MySQL servers.

You'll leave the session with a comprehensive …

I've been preparing for my innotop session at the upcoming MySQL conference, and enlisted Giuseppe Maxia's MySQL Sandbox to help me get a bunch of MySQL servers, from 3.23.58 to 5.2.3, running on one machine. It was super-easy and has helped me find some bugs in innotop. I should have done this a long time ago.

I'm continuing to add new tools to the MySQL Toolkit. MySQL Deadlock Logger is for extracting and storing information about the latest recorded InnoDB deadlock. It's not only easy to view the information from the command line, it's dead simple to store it back into a MySQL table for analysis. I think most users will find it handy to create a cron job to record the deadlocks automatically for later analysis.

Are you seeing a MySQL error that says InnoDB support isn't enabled, even though it is? This article explains why it happens and how to fix it.

It's finally ready -- the new stable version of the innotop MySQL and InnoDB monitor. Version 1.4.0 brings you new features and enhancements I think you'll really enjoy.

Now that I have innotop hosted on sourceforge, I'd like to use the tools they provide, especially the forums and mailing lists. I've set up an innotop-discuss mailing list, which I hope you'll find a better way to get support than posting in the comments on this blog. I think I will close comments on all innotop-related articles I post, because I can't keep track of feedback in so many places.

innotop 1.3.5 is the latest release of the increasingly popular MySQL and InnoDB monitor. I recommend everyone upgrade to this release. Aside from incomplete documentation, it's close to a stable 1.4 release (I'm counting on you to find the bugs!). There are many significant new features since version 1.3, which make it more powerful and easier to use.

I just made a snapshot of the development branch of the innotop MySQL and InnoDB monitor, and released it as version 1.3.0. This code will eventually become version 1.4. Here's what's new.

I've made the 1.0 release I promised yesterday. I am very happy to declare innotop production-ready and stable. In this article I talk a little bit about my plans for the future, and look back to the project's humble beginnings as a script I ran inside watch. Check out the screenshot! OMG!

A couple of weeks ago I submitted a request to open a new project on Sourceforge for the innotop MySQL and InnoDB monitor. I want to make it easier for others to collaborate, especially package maintainers. Yesterday I got word of its approval. I have done a quick-and-dirty import of the source code into its new home, and I'm now continuing work on the next major version, which I've been working on for about six weeks. This post is about Sourceforge, what I've gotten done, and also to ask for your help.