OpenSQLCamp was a huge success! I took videos of most of the sessions (we only had 3 video cameras, and 4 rooms, and 2 sessions were not recorded). Unfortunately, I was busy doing administrative stuff for opensqlcamp for the opening keynote and first 15 minutes of the session organizing, and when I got to the planning board, it was already full….so I was not able to give a session.

• 
  
• Comparing Non-Relational Databases: MongoDB, Tokyo Tyrant, CouchDB by Igal Koshevoy of Pragmaticraft

At the July MySQL User Group, Eric Day and Patrick Galbraith spoke about Drizzle, a lightweight, microkernel, open source database for high-performance scale-out applications, and Gearman, an open source, distributed job queuing system.

The slides can be downloaded from http://www.oddments.org/notes/DrizzleGearmanBoston2009.pdf.

The first hour of video, where Eric and Patrick talk about Drizzle, is at http://www.youtube.com/watch?v=hi4cGzFlcuU, and below:

The second part, about 1.5 hours, where Eric and Patrick talk about Gearman, and then illustrate Gearman and Drizzle working together in a custom search application called Narada, is …

I’ll be liveblogging the keynote here along with Marc Fielding, Christo Kutrovsky, Darrin Leboeuf and Luke Davies and Martin Wisniewski.

First observation: I can not believe I can not make this video full screen.

Even Pythian’s flash video player can go full screen.

Introduction time. Safra Katz.

Confirming HP is here as part of the announcement.

So presentation from HP is here first. Weird. Maybe this is a megabucks commercial keynote. Introducting Exec VP Anne Livermore.

“Very very very very very important event for HP. 100000 joint customers.”

Show of hands for HP adoption. A bit lame, she seems disappointed with how many hands are raised. :-)

The video stream is super saturated, the video is super skippy. Hopefully I can understand what’s going on well enough to do this liveblog.

So far it’s completely a vendor advertisement keynote.

…

Note: This article is about the WHERE extension to SHOW. I specifically use SHOW STATUS as an example, but WHERE is an extension to many SHOW statements.

Often DBAs will assess the health of a system by looking at some of the status variables returned by SHOW GLOBAL STATUS (specifying GLOBAL is important; remember that SHOW STATUS is the same as SHOW SESSION STATUS).

There are many status variables that SHOW GLOBAL STATUS returns. (SHOW GLOBAL STATUS on a Windows machine, MySQL version 5.0.67 returned 249, 5.1.22 returned 256 and 6.0.6-alpha returned 295 status variables!). I have used the SHOW STATUS LIKE syntax to help give me the output I really want, particularly when I forget the exact names of the status variables I am looking for.

But I did not know of a way to …

Smithy commented on my blog post about the rumor of Monty leaving Sun with a pointer to an article on ComputerWorld Finland that mentions:

Widenius told to Computerworld Finland on Friday that negotiations are still on.

Meanwhile, Matt Asay, who seems to think Monty actually has left Sun (even though all other reports have been clear to mention that this is unconfirmed), writes of a new investment Monty has made.

Last week I speculated about the impact of Monty leaving Sun. In the end, if he does stay, it’s wonderful for Sun. If he leaves, he will no …

Scenario: Someone wants to know which of the over 50 MySQL users have certain privileges.

There are many ways to solve this problem. Some of these scenarios are tedious and repetitious, others take no time at all.

The issue, of course, lies in what the “certain” privileges are. If it is “who has the SUPER privilege?” then a simple

SELECT user,host FROM mysql.user WHERE Super_priv='Y';

is sufficient. If it is “who has write access to the foo database”, you might write:

SELECT user,host FROM db WHERE Db='foo' AND Select_priv='Y';

but that only shows who explicitly has read permissions on that database; it does not include those who have global read permissions. The full query would be:
(more…)

Last week Giuseppe Maxia announced the Call for Papers for the 2009 MySQL Users Conference and Expo, and also announced that there would be an unconference, MySQL Camp, organized by me.

It’s true! Currently MySQL Camp is set to happen, though I am still working out details with Colin Charles and Giuseppe Maxia. We had originally talked about having MySQL Camp on Tuesday and Wednesday, but I would like to add Monday so that folks attending the conference who are not attending a tutorial have a choice on Monday. I am also looking into lunch options, since the conference venue does not have many options within walking distance.

There will be plenty of …

I have not said much about Drizzle here; that is because there is not much to say. It is premature, really, to say anything about it at this point. Some have said they will support Drizzle; as Pythian supports several database systems, it is very likely that we will support Drizzle as well. Particularly since there is in-house Drizzle expertise already. But I digress; my point is that it is premature to really say much about Drizzle.

My involvement in Drizzle goes back to around the end of April/beginning of May 2008. Given my early involvement, (more…)

Back in May 2006, I have started my blog using the Blogger platform and one month later moved it to my own website using Wordpress. Couple month later, I joined Pythian and, since then, the vast majority of my blogging activities has been on the Pythian Group Blog.

The Pythian blog has grown significantly since then and many more excellent authors started blogging there. While the Pythian blog was mostly focused on Oracle database just a couple years ago, it’s has got very broad coverage now and is including MySQL, SQL Server and Oracle databases as well as Oracle Application Server, Oracle eBusiness Suite and …

The MySQL Community version is different in theory from the Enterprise version in relation to the following points:

0) It’s free
1) It has community patches
2) It is released less often
3) It is tested less strictly

In reality, the first two differences are not applicable — the binaries and source code for Enterprise can be freely and legally downloaded at http://mirror.provenscaling.com/mysql/enterprise/. The process for adding community patches to the MySQL source code has not been changed sufficiently to be able to actually add community patches and encourage more community development.

I understand that MySQL (and now Sun) needs to make money. I also understand that development takes a lot of effort, and seeing an ROI is important. The Community/Enterprise split was designed to have tradeoffs on both sides. …