At the last minute Giuseppe convinced me to bring my video cameras, and so I was able to get some of the presentations at MySQL Sunday recorded, as well as some of the MySQL related presentations at Oracle OpenWorld. As usual, they are hosted on YouTube and free. Here's the list:
Earlier this year, the beta of MySQL 5.5 was announced. We all felt excited about the changes in 5.5, especially the large performance improvements. However, many of us proceeded with caution; version 5.4 was previously announced with similar fanfare and we had yet to see a GA version.
About six weeks ago I posted about leaving Pythian. I had a month off in which I spent quality time with my husband, including packing up our apartment to move two blocks away. I also spent some time doing some planning and organizing for OpenSQLCamp Boston, happening in 6 weeks. Many people have been wondering what my next move is.
You might notice that I haven’t blogged in oh, 2 years. How remiss of me. The only defense I have is that we’ve been non-stop busy! Since then we’ve built our client portfolio, brought in two new team members, presented at MySQL Conference and still managed to get into any number of shenanigans. Still, that is no excuse. Let me give a summary of some of the interesting things we’ve been up to:
I’ve been setting up partitioning for various customers lately. The goals primarily have been easy purging of large growth tables and keeping indexes small enough to stay in memory and manageable. These have all been range partitions on dates, which is a rather common requirement. As you’ve probably noticed in previous posts, I absolutely hate environments where people let their tables grow like blackberry bushes. While doing research, I found the following links to be very helpful:
Everyone puts lip service to the concept of keeping versions consistent between servers but it is consistently one of the most broken best practices I see amongst my clients. The problems with such inconsistency are legion, and I’ll point out a few here.
The MySQL Toolkit can be found at http://mysqltoolkit.sourceforge.net/. It is coded and maintained by Baron Schwartz (www.xaprb.com). I’ve been using the archiver tool he wrote lately, and wanted to share this tool. In every web environment I’ve worked in, there is data that is collected for analysis and that grows quite rapidly. User activity logs in particular can quickly grow out of control, and generally have no place in a front-end database after a certain amount of time.