In this second MySQL User Group meeting, we’ll again focus on general best practices and free discussions, in order to share our knowledge as much as we can. The last meeting was in Mellieha and it was a success — we had a good turnout and some very interesting discussions. Darren, one of our members, blogged about our meeting and so did I in one of my previous posts. If you’d like to learn more about MySQL, or if you’re a DBA (doesn’t matter which level) I encourage you to email us (and sign up to our mailing list) at malta (at) ug.mysql.org. Or subscribe here. You can also, as always, email me directly at: westerlund (at) pythian.com
I’d like to share some great news — The Pythian Group and Open Query have become partners! Open Query is a leading provider of high-quality MySQL, PostgreSQL and related training in Australia and New Zealand. They offer consulting services too, and are also known for their MySQL Graph Storage Engine. Feel free to browse through Open Query web-site for more info.
So, you have a binlog. You want to find out something specific that happened inside of it. What to do? mysqlbinlog has some neat features, which I thought we would look at here. I should first explain what mysqlbinlog really is. It is a tool that lets you analyze and view the binlogs/relaylogs from mysql, which are stored in binary format. This tool converts them to plaintext, so that they’re human-readable. For the first tip, let’s start with the –read-from-remote-server option, which allows you to examine a binlog on a master server in order, perhaps, to dump it onto your slave and compare master/slave logs for potential problems*.
The Maatkit toolkit is a real blessing for the MySQL DBA. And while its documentation is pretty good, in some cases it’s necessary to read carefully a second and third time to make sure you are not missing an important piece of information. In this article I will comment on mk-table-chksum and mk-table-sync. My comments are mostly aimed at those DBAs who are considering using these utilities with medium or larger-sized databases.
In two words: online operations. In a paragraph: Forget partitioning, row-based replication and events. The big reasons most people are going to salivate over 5.1, and probably start plans to upgrade now, are the online operations
After I moved back to Europe and Malta in order to set up our operations here, I was approached by a old friend of mine who wanted to know how to add a UNIQUE constraint and remove duplicates on a table, while keeping the newest records. He had been trying with ALTER TABLE but ran into problems as the older values were taken. To help him out, I first solved it based on his original idea, and then figured I would post a small note about the solution here.
So, the Malta MySQL User Group has had its first ever meet-up today, and it was a success! he evening proceeded with a introduction of ourselves, our interest in MySQL, and mainly talk about weird bugs that we had encountered during our careers. Oh, we also discussed Kickfire a bit, and it does indeed sound like a very interesting product, which I’d love to try out one day. Overall, I am very satisfied with this meeting and the turnout.
I recently needed to set up multiple MySQL servers on a test computer to simulate a master-slave setup. I had never done this before, so I think it might be useful for others if I documented what occurred.
How does a wild-mannered MySQL DBA like me get to speak at an Oracle conference? Well, after I received the MySQL Community Award two years in a row, Dan Norris contacted me, and encouraged me to submit a proposal with him on how to contribute to the community.
The MySQL Community version is different in theory from the Enterprise version in relation to the following points….