Yesterday I announced the MySQL Unconference. Some folks have asked about the MySQL Camp that both Giuseppe and I previously announced.

They are one and the same. In order to minimize confusion, I’ll change things to say “MySQL Camp” instead of “Unconference”. Apologies to those who were confused!

This post is more of a personal note than most on the Pythian blog, but over the holidays, I couldn’t help thinking about my turbulent last year.

First, MySQL

In 2008, I worked at three different companies. It was about a year ago (January 15th will be a year) I was at MySQL AB’s first company-wide meeting in a few years with more than 400 of my colleagues, when all of a sudden we get the announcement: “Sun acquired MySQL for 1 billion dollars”. Many thought it was a joke, just in time to watch Jonathan Schwartz come up live on video to greet us. Talk about an intense way of starting a year! For some reason, nobody thought that toasting with a shot of vodka before 9:00am was the oddest thing to happen that morning.

Working for MySQL was, most likely, the wildest ride I will ever have. True Open Source spirit (no matter what the rest of the world says), start-up mentality, and growth equal to one order of magnitude …

The MySQL 5.1 GA Release will be on or about Dec. 6th, 2008.

How do I know?
(more…)

Happy birthday to Giuseppe Maxia, a wonderful community organizer for MySQL.

And happy birthday to Leslie Hawthorn, Google’s geek herder.

Thank you for making life better for open source volunteers like me!

Sorry for the outage, everyone. We’re looking into the causes of the downtime (and sponging the sweat off our keyboards), but for now we’re happy just to be back. Stay tuned for a real blog article soon.

I confess — I have not always been an exclusive MySQL user. I have fooled around with other DBMSs. I was young, inexperienced, and I needed the money, I swear!

This comes about because I was doing some electronic de-crufting….From a file last modified on 10:50 am on 2005-06-30:

> more addcatalog.sh
#!/bin/sh

 db2 catalog tcpip node $1 remote $2 server 50000
 db2 terminate
 db2 catalog database sample as $2 at node $1
 db2 terminate

# [db2inst1@midgard db2inst1]$ db2sql92 -a db2inst3/password -d coworkername

And from the same time-frame there’s also:

(more…)

So, we have all heard that Billy Joel played a concert at Oracle’s OpenWorld in 2007.

What follows is an actual IRC conversation among Don Seiler, Dave Edwards, and myself:

(4:02:46 PM) don: ha @ Billy Joel at OOW
(4:03:38 PM) dave: “We didn’t fire the startup…”
(4:07:53 PM) don: “we didn’t start the backup”?
(4:12:53 PM) dave: “Don’t go changin’ . . . your slave and master”
(4:20:19 PM) ***sheeri shoots Dave
(4:20:49 PM) sheeri: “I don’t want clever replication, we never could have come this far”
(4:24:05 PM) sheeri: “And the server sounds like an aero-plane, and replication chugs along as it must…and the inserts go on, replication corrupts, and I say “Man, now I’m workin’ all night!”

(4:24:29 PM) dave: “I said ‘ls -u’ . . . …

Tonight I am catching up on older e-mails — here’s another question that came to me about 2 weeks ago from a user group member that I never had time to research and answer. I have directed the original author to this post so questions you pose in the comments can be answered.

Do you know anything about indexed file systems? I’m looking for a ‘nearline’ storage solution to help with data archiving.

We have a system which at it’s peak will be accepting 15 million short records / day. In order to keep the Web front end moving nicely, we want to drop data after about 3 weeks and shift it into a higher latency, higher capacity storage system. Indexed file systems seemed like a perfect solution for this. Ideally it would have a good front end to allow execution of arbitrary queries in some language (SQL would be nice).

The only thing I’ve been able to locate is an MS product called “Microsoft Index Server” and …

Hi all,

I was asked this question in an e-mail — feel free to ask your questions in the comments, as I will point the original author to this post to answer those questions. There is not a lot of data here, so instead of me asking questions in an e-mail I figured I would open it up to the (MySQL) world. Without further ado, here’s the question:

Basically when we open more than one connection- we’re opening 5, and we do processing in mysql (innodb tables) the server cpu and memory max out and the processing grinds to a halt. One connection at a time is able to run well- even with lots of data. But once we try to process data under 5 concurrent connections, mysql gets bogged down to the point where it’s barely usable.

I’ve researched this and found a number of opinions, including whether this is just poor performance due to where the we are in the 5.1 life cycle (i.e. energies have gone into fixing big bugs not …

Well, in the “notes from the front line” part of this post…. I have been a MySQL DBA at The Pythian Group for three months (and 2 days) now. At most companies that is the probationary period, and I am still here, so that is a good sign….. So, after three months, how do I like [...]