Here is a compilation of MySQL-related news and posts that I found interesting. Enjoy!
When preparing for the the IOUG Collaborate 12′s deep dive on deploying Oracle Databases for High Availability, I wanted to provide some feedback on which hardware components are failing most and least frequently. I believe I have a reasonably good idea of the answer, but I thought that providing some more objective data would be better. I couldn’t find results from a more scientific research, so I decided to organize a poll. This blog post shows the results, which I promised to share with several groups.
While doing my high availability deep dive at Collaborate 12 few weeks ago, I stated that storage replication qualifies for the cold failover licensing rules (see slide #128). During collaborate, I spoke to one person at Oracle who definitely knows the rules. Simon Haslam also reached out to me by email pointing out that things might not be that rosy. I will update the slides accordingly. In any case, please do your own homework and don’t trust my conclusions here — don’t take this as licensing advice by any means.
These are my personal rules to moderate the public forums on LinkedIn. I’ve posted on that topic in the discussion on the IOUG Exadata SIG forum. As I’m passing RAC SIG group to the next folks on the board (I’m the RAC SIG president until end of August), I needed to hand over my forum management duties too. I decided that it might be useful to the wider audience, so why don’t I just publish this on the blog?
Our flagship tool, Support Track, is steadily migrating over to use DBIx::Class to read and manipulate our databases. This is a very useful tool, for many reasons that can be better explained by others. One of these reasons is that, thanks to the magic of SQLite, it lets us write unit test scripts, and other quick prototyping codes, without needing to set up a heavy database server to run against. However, Support Track is powered by Oracle, not SQLite, and while DBIx::Class abstracts most of the differences out of our code, it can’t completely eliminate them. How do we overcome the syntactic differences?
As Summer begins in many parts of the world, not only is nature waking up, but many bloggers are also coming out of hiatus and the database blogsphere is seeing new sensational activity. This Log Buffer Edition includes blogging tidbits from Oracle, SQL Server, and MySQL. Enjoy!
I spent last week at Collaborate 2012 in Las Vegas, and it was a really great experience in many ways. I am a MySQL DBA and have been working with MySQL for most of my career, so Collaborate didn’t seem like an obvious choice. It turned out that I had so much to learn from Oracle professionals and the Oracle community that could be applied in the MySQL world. For me, an indication of a good conference is when you come back inspired and full of ideas.
Pythian is excited to announce that Heidi Hauver, Pythian’s HR Director, has been named as one of the recipients of the Ottawa Business Journal’s prestigious Forty Under 40 Award! A BIG congratulations from all of us, Heidi!
Why this article? First, I had fun digging in the code. Then, I was reading about the future improvements for MySQL 5.6 and about some currently in 5.5. Most of them are well covered by people with more expertise than me. So I read, but after a while I became curious, read the code, and performed tests. I was looking at how the new Purge thread mechanism work and its implications. Here’s what I found.
Pythian’s Oracle Apps DBA team recently upgraded a client’s E-Business Suite system to version 12.1.3, bringing them into compliance with Oracle’s baseline support requirements for Release 12.1 nearly one year ahead of deadline. We’d like to tell you a bit about this project — not to toot our own horn (though that’s nice too, we are kinda proud), but because it provides an ideal illustration of the power of the Pythian service delivery model, particularly as it applies to large enterprise-class projects.