Let’s have a quick look at some clustering examples in the new 3.0 engine:

This example runs all steps in the transformation in a clustered mode. That means that there are 4 slave transformations that run in parallel with each other.
The interesting part is that first of all the “Fixed Input” step is running in parallel, each copy reading a certain part of a file.
The second thing to mention about it is that we now allow you to run multiple copies of a single step on a cluster. In this example, we run 3 copies of a step per slave transformation. In total there are 12 copies of the sort step in action in parallel.

IMPORTANT: this is a test-transformation, a real world sorting exercise would also include a “Sorted Merge” step to keep the data sorted. I was too lazy to redo the screenshots though

The clustered transformations now also support logging to …

Hmm, long time no post! But I have the perfect excuse: I've actually been on vacation the past two weeks... Now I am back at work and busy trying to make a dent in the mail pile that has accumulated while I was gone. In addition to that, I am assisting with the organization of our MySQL Developer Meeting in Heidelberg, which will take place in September. See Kaj's blog post for more details about it. I am in charge of our community guests and really look forward to meeting most of our internal developers as well as community guests there! This is going to be a fun event.

In addition to that, I am applying the final touches to my upcoming presentation about our ongoing community activities: "Opening the doors (and windows) of the Cathedral", which will be held at the …

The role of data stored in MySQL database in today’s world is already known - it powers business and mission critical apps. Protecting this data is of utmost important to any enterprise. Before you actually have a backup in place, that are some very important things to think about the backup implementation. Like for instance, how soon would you want your data recovered after a user or system error? This article provides an indepth analysis about the basics of what needs to be considered while planning a Backup and Recovery solution for your MySQL database.

A MySQL network storage engine for MogileFS.

After writing the MySQL Storage Engine for Amazon S3, and having heavily dug into the storage engine for MemCacheD, it can't really be that hard.

Would it be useful?

Ok, so the MySQL Camp II officially starts in 8 hours and 9 minutes. If you are in New York, it behooves you to attend.

MySQL Camp II is sponsored by Polytechnic Institute, Logic Works, Too Many Connections (free MySQL Camp T-Shirts!), Proven Scaling (Lunch) and Google (Coffee).

I expect a lot of cool discussions and meeting with old and new friends. I will be interested in talking/discussing about:

Optimizing data architecture for InnoDB,
Speeding up MySQL replication,
MySQL disaster recovery,
Setting up QA environments that mimic production
Optimizing MySQL on …

I had a wonderful evening tonight with Jay Pipes, Paul McCullagh, Marc Simony, Ronald Bradford, Tania, Taso, Jeremy (not "the Jeremy" who along with Sheeri was missed) and my wife. We met at The Village Pourhouse for Pre-camp party organized by my good friend Ronald (thanks!).

One line said at the gathering (don't ask why):

"The Naked MySQL DBA: My ISAM is bigger than yours"

That called for a once-in-a-lifetime laughter. It was just so funny.

Scale-up vs scale-out - what are they?

Basically, “scaling up” means to add power to your server, or get a bigger server -build it up. “Scaling out” means to add new servers to your configuration - build it out.

Oracle touts both approaches, using RAC on big servers or on “blades”, or a “grid”.

MySQL generally touts scaling out, and most of the big sites using MySQL use “scale-out”. In my experience, and according to Jay Pipe’s excellent blog entry on the subject, that’s partially because MySQL doesn’t scale up as well as it scales out. (Another reason he mentions - that also fits my experience - is that people who pay for Oracle licensing match that by also buying expensive machines to put it on.)

In Oracle, whether you scale up or out, you’ll probably use RAC, which means setting up private interconnects and basically using “shared everything” with your servers. You’re still sort …

I just re-installed my MacOS 10.4 (Tiger) from scratch. However, it's more than just putting in the DVD and doing an upgrade.. This post is more a reminder for myself when I'll have to do it again!

For MySQL you'll need newer versions installed on MacOS 10.4 of the popular GNU tools: automake, autoconf, bison and libtool. Otherwise you'll notice it doesn't really compile. You'll find URLs here below and download the latest versions.
Additionally I needed to install pkgconfig because /usr/local/bin/autoreconf just failed for the ndb-connectors! Don't ask me why, I just found while googling for it..

I did install everything under /usr/local and changed my $PATH in ~/.bash_profile to PATH="/usr/local/bin:$PATH"

Quick "one liner" for shell to check on the version of the build tools:
shell> for p in automake autoconf bison pkg-config; do echo -n "$p: " ; $p --version | head -n1; done; glibtool …

I just re-installed my MacOS 10.4 (Tiger) from scratch. However, it's more than just putting in the DVD and doing an upgrade.. This post is more a reminder for myself when I'll have to do it again!

For MySQL you'll need newer versions installed on MacOS 10.4 of the popular GNU tools: automake, autoconf, bison and libtool. Otherwise you'll notice it doesn't really compile. You'll find URLs here below and download the latest versions.
Additionally I needed to install pkgconfig because /usr/local/bin/autoreconf just failed for the ndb-connectors! Don't ask me why, I just found while googling for it..

I did install everything under /usr/local and changed my $PATH in ~/.bash_profile to PATH="/usr/local/bin:$PATH"

Quick "one liner" for shell to check on the version of the build tools:
shell> for p in automake autoconf bison pkg-config; do echo -n "$p: " ; $p --version | head -n1; done; glibtool …

According to recent survey, over 20% of MySQL users plan to migrate a Microsoft Access applications to MySQL over the next 12 months. However there are few documents available that describe best practices for performing such a migration.
This document summarizes discussion from the ?MS Access Migration? session at the 2007 MySQL User Group meeting in California. That session brought together a number of MySQL users with a goal of identifying key success factors for moving MS Access applications to MySQL.