It’s been a while since the MySQL Management Plug-in 0.42 was released. Since then, I quietly updated it to version 1.0. The changes were very few; the biggest news was that the plug-in was certified by Oracle and added to OTN Oracle 10g Grid Control Extensions Exchange. Version 1.1 turned out to be a major rewrite for the Perl collection scripts and the net result is that compatibility across platforms is greatly improved. I have successfully tested the new version on Linux and Windows Agent hosts. So what’s new in version 1.1 compared to 0.42? Find out here.
he Boston MySQL User Group was lucky enough to get Keith Murphy to speak at the June User Group meeting, about backups. here are links to the video and presentation materials, and reference information in this post. Enjoy!
Simple auditing can save you tons of time while troubleshooting. I came up with some simple stored procedure that will compare two data sets and keep track of the changes historically. It’s loosely based on slowly-changing dimension type 2 in the data warehouse world. This method tracks only changes, so you should be able to keep historical rows forever, unless you are constantly dropping and creating whatever you are tracking.
In the case when the error log writes to a non-default path, FLUSH LOGS actually does not work as specified for the error log. I have not seen issues with binary logs in non-default paths, but we just ran into this issue on a client site and it threw us for a big loop. The bug description is here…
At last night’s event, a lot of the questions were really implicitly asking, “Is open source better? Why?” The first answer everyone comes up with is that it’s free, and that’s better. However, that is neither necessary nor sufficient to deem it “better”. Let me explain….
When Steve Curry contacted me just after the MySQL Conference and Expo asking me if I’d be interested in a community roundtable, I was excited. However, a few weeks ago it seemed like the event was more of a PR gathering than a community roundtable. I was disappointed, and told Steve as much. And then, one of two things happened…
In interesting news, at last night’s Boston Sun/MySQL event (more on that in another post), the question was asked if the panel thought that Microsoft was really serious about open sourcing their software(s) and what that would mean for open source software. If Microsoft opened all of their code tomorrow, how big of a *developer* community would they have? By that I mean, how many people would say “yeah, all right! I’m going to make this code better!” and how many would take a look at the internals and feel like they’d just been on a roller coaster? Open source is the foundation of civilization. The title of this post mentions that, and now I will explain why.
I understand that MySQL as a company wants to recruit paying customers. However, as a community user I have a hard time finding what I want on the MySQL website. Today’s frustration is brought to you by trying to find the documentation.
One of the most frequently needed functionality in the MySQL Proxy is the need to know which server you are on. This is not given, on purpose, by the proxy, because the proxy is supposed to be transparent. It is not supposed to matter which back-end server you are on. However, for testing purposes we often want to know which back-end server we’re on. Thus I developed functionality for SHOW PROXY BACKEND [INDEX ADDRESS OTHER].
Contemporary software engineering models include many loosely-defined layers. Database developers might help with other layers, but for the most part a database administrator’s domain is the persistence layer. The Daily WTF has an article on The Mythical Business Layer makes the case for not separating the business layer and the application layer: I will call this merged business/application layer the “functional layer.” The serious scaling requirements posed by most applications these days call for partitioning, clustering, sharding or some other term for “dividing up the data so it does not become the bottleneck”. Enter the “architecture layer”. I hear you asking. “Isn’t that just the persistence layer?” Yes and no.