I spoke to Daniel Abadi this morning about his HadoopDB announcement that came out a couple of days back.  I am sure this has been a busy time for Daniel and his team over in Yale as HadoopDB has been getting a lot of interest which I am sure will continue to build.

Some notes from our discussion:

• HadoopDB is primarily focused on high scalability and the required availability at scale.  Daniel questions current MPP’s ability to truly scale past 100 nodes whereas Hadoop has real examples on 3000+ nodes.
• HadoopDB like many MPP analytical database platforms uses shared nothing relational database as processing units. HadoopDB uses Postgres.  Unlike other MPP databases, HadoopDB uses Hadoop as the …

By making PBMS transactional I have been able to greatly simplify the engine interface making it much easier for engine builders to build in support for PBMS. How much simpler is it? From the time I decided to make InnoDB PBMS enabled to when I started the rebuild of MySQL was less than half an hour!

The same way that I added PBMS support to InnoDB it can be added directly to the MySQL server so that the PBMS engine will be used for BLOB storage for all engines regardless of if they have been enabled or not. PBMS support for drizzle will be provided via a data filter plug-in which I have yet to write but will soon.

To add PBMS support all you need to do is add the file pbms_enabled.cc to your source code and add the following to your handler code. I will use the InnoDB handler code as an example:


File ha_innodb.cc:

#ifdef USE_PRAGMA_IMPLEMENTATION
#pragma …

Fix your licensing model so that mirrors can legally maintain copies of your documentation, so that I'm not left sitting in the dark when your website goes down.

What if Oracle shut MySQL down today? They absolutely could. With the documentation not in the GPL, when Oracle pulls the plug on the websites, well, goodbye docs. It isn't legal to mirror them elsewhere.

We've been mingling here for 4 days already, but today the official part of OSCon kicks off. At Monty Program we've been a bit late in preparing for this conference - busy getting started with the company and everything. But even if we were a bit late, we succeeded in lining up a good set of sessions.

read more

I am a software guy, I admit that, but I have also worked with Hardware, way back. The reason I say this is that most history on Computers are related to hardware, and there is some good reason this is so. Mainly, the history of computer hardware is older, much older, than the history on Software.

This said though, Software and the Software industry is old enough (speaking of software as an entity of it's own, not related to Hardware, it is approaching 50 years) to start telling the History of software.

But for myself, even though I am a Software guy, Computer Hardware has at the moment a much more intriguing and interesting history. Being a MySQLer though, I will make an attempt to blog about as much Software History as I can. And I can tell you I have a few interesting stories on the issue of computer, and computing, history up my sleeves, including Software history. But I am not a researcher in the field myself, I …

Image by Getty Images via Daylife

Sun is now/soon-to-be part of Oracle and I am extremely concerned about MySQL. There has been reassurances from the community... and I believe they could probably work.

I was wondering however, about the hardware side of Sun. Sun has always thought that by giving something for free, you encourage customers to buy something else from the same company.
They put that model to work with open-source software like MySQL and hoped that customer will buy …

I just finished reading Joel Spolskys book "Joel on Software", and I had a good and interesting read I have to say. This doesn't mean that I agree with everything in this, by now a bit dated, published in 2004 and as it is a collection of writings from Spolskys website www.joelonsoftware.com, it is more dated than that.

Spolsky writes in a rather humorous, witty style, and he is very opinionated and has strong opinions on many things. And he sometimes hits some rather minor issue which he dislikes with a baseball bat. But I enjoyed reading the book, it was a fun read and it got me thinking on issues, even though I didn't agree with Spolsky always, frankly, most of the time I didn't (he's not too hot on Open Source for example, and gives examples why it's not going to work, and we now know, as the book is dated, how things went. And he was wrong). But the deal with this book …

The OpenSQLCamp 2009 European edition, is under scrutiny. There are 27 session proposals, from which we will need to get 12 in the schedule.
The open voting is done via Twitter or the mailing list.
I have a good feeling about it. Since I am proposing a public …

What comes up to your mind when you hear the phrase "MySQL performance tuning?"  Most of the discussions covering the topic are things like server parameter tuning and blog entries describing the use of the "EXPLAIN" command.  However, it is too time-consuming to check every single SQL query.  A better approach is at first to determine the SQL queries that are actually consuming the server resources, and then to optimize those queries.

So the question is how to find out the bottleneck queries.  At MySQL Conference & Expo 2009, Mark Callaghan explained in his keynote that Google was taking a statistical approach using the "SHOW PROCESSLIST" as a solution.  The same command is mentioned as a rival approach in the webpages of MySQL Query Analyzer as well.  Today, …

Currently Drizzle offers three (3) separate query logging plugins. These plugins offer an extensible means of gathering all or selected queries and provide the foundation for a query analyser tool. Additional filtering includes selecting queries by execution time, result size, rows processed and by any given regular expression via PCRE.

During this tutorial I’ll be stepping though the various logging_query parameters which log SQL in a CSV format.

Confirm Logging Plugins

You can view the current ACTIVE plugins in Drizzle with the following SQL.

drizzle> select version();
+--------------+
| version()    |
+--------------+
| 2009.07.1097 |
+--------------+

drizzle> select * from information_schema.plugins where plugin_name like 'logging%';
+-----------------+----------------+---------------+--------------------------------------+---------------------------------+----------------+
| PLUGIN_NAME     | PLUGIN_VERSION | …