Posts Categorized: Technical Blog
Update 13-June-2012: It has come to my attention that the numbers from the original source may have been incorrect or improperly released. To avoid confusion and potentially misleading information, the original content of this blog post has been removed.
Here is a compilation of news relating to MySQL. (June 5th, 2012)
As heralded by Iggy Fernandez and Gwen Shapira, NoCOUG has launched its Third International SQL vs. NoSQL Challenge. Pythian is sponsoring the challenge, so I decided not to take part in the contest. However, I’m still having a crack at the problem just for fun. Here is my first take on it.
The purpose of this blog isn’t to show off the results of my presentation at Collaborate conference, but to inspire you (and maybe myself in the future) and give you additional motivation to never give up on your dreams if you truly believe in them.
For the third consecutive year, NoCOUG is hosting an international SQL challenge. In this challenge, the Wicked Witch of the West needs help in creating a magic spell to ensure that the Third Annual Witching & Wizarding Ball is a grand success. Here’s the challenge…
I’ve recently done two Exadata upgrades to 126.96.36.199 and want to share the experience. I hope this short note will help someone to make the decision, calculate an estimation, and prepare for maintenance. I am going to talk about upgrade from the version 188.8.131.52 BP10 to 184.108.40.206 BP2.
I had the chance to talk to several Oracle Database Appliance users at the annual Collaborate 2012 conference last month in Las Vegas. A common theme in these discussions, as well as discussions with Pythian clients, is an interest in using the ODA as a large-scale consolidation platform. I found this interesting and decided to dig a little further.
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.
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?
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.