The latest from the MySQL community

This release of the innotop MySQL and InnoDB monitor is a major upgrade in terms of functionality, code quality, and interface consistency. It is the result of me working for over a month to get innotop into shape for the recent MySQL Conference and Expo. This article is a summary of the changes and a look at what's coming next.

One thing is always certain about information technology: there is always change. This past week I was pitching in on a Citrix upgrade for my organization and I went to tweak the web interface. Though I'm not primarily a "server guy" and directory services administrator, I do have a web developer skillset (in fact, that's how I got my start where I work now). However, it's been a few years since I've done anything but touch up work with regards to web development and initially I got that blank feeling... the one where you know how to do things but it's like your mind is cycling through the archives to pull back that information and bring it to the forefront. After a thankfully brief period of "brain thrashing," I went to it.

This experience reminded me of a .NET Rocks! episode with noted Windows …

MySQL Table Sync 0.9.2 is a bug-fix release. Since the last release users have reported several bugs. I am still postponing new features until after the MySQL Conference and Expo, because I am focusing on the innotop session I'll be presenting at the conference.

I have also created a new mailing list on sourceforge for discussing all things MySQL Toolkit.

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.

A frequently asked question about MySQL replication is "how do I know whether my slave is identical to the master?" Until recently there hasn't been a good way to know, but now you can compare all the data in your master to the data in the slaves and get a reliable yes-or-no answer. And you can do this online, efficiently, across many servers simultaneously. Read on to find out how.

I've just released three updates to tools in MySQL Toolkit. The updated programs are MySQL Query Profiler (major new features and helper script), MySQL Table Sync (bug fixes, documentation, features), and MySQL Table Checksum (minor sanity check enhancement).

When I wrote my first article on algorithms to compare and synchronize data between MySQL tables, Webyog's Rohit Nadhani left a comment on the article mentioning the SQLyog Job Agent, which has a similar function. Although I have been developing MySQL Table Sync essentially in isolation, I have been meaning to give SQLyog Job Agent a try. I recently did so, and then followed that up with an email conversation with Rohit. This article is about my experience using the SQLyog Job Agent from the command line, some thoughts on the algorithm as best I can deduce it, and benchmark results against MySQL Table Sync.

I wrote an article late last week about benchmark results for the two table-synchronization algorithms I've been implementing for the MySQL Table Sync tool. I've spent some time developing a test suite for the tool, and learned some really interesting things about the general problem of synchronizing tables.

I've been working on how to efficiently compare and synchronize data between two tables on different MySQL servers. I've also been working on a tool, sort of like rsync for database tables, which implements both algorithms. I profiled it to see how well the comparison algorithms work on real data. This article is about the results.

MySQL Table Maintainer is a new utility to help you run table maintenance commands (ANALYZE, CHECK, OPTIMIZE, REPAIR) on your MySQL tables. It's part of the MySQL toolkit.