Looks like the InnoDB plugin is completely broken with MySQL-5.1.24; at least there is no luck for me so far to set it up right. First, the Makefile is broken. Second, I tried to do a static build of InnoDB plugin with MySQL server (–enable-innodb and –with-plugin-innobase) resulted in partial InnoDB plugins (Information schema) missing the main one as shown below:

   1:  mysql> show plugins;

2:  +---------------------+--------+--------------------+---------+---------+

3:  | Name                | Status | Type               | Library | License |

4:  +---------------------+--------+--------------------+---------+---------+

5:  | …

In probably the best move by Sun during the whole MySQL Conference and Expo, Rich Green and Jonathan Schwartz turned up at the Community Dinner on the Sunday night before the conference.

As we walked into the restaurant I saw a face that I thought was familiar. Jonathan and Rich were standing outside the restaurant talking. However, only when we got inside did I hear Jay saying that that was Jonathan Schwartz.

So just before we all took our places, and while we were trying to work out how we were going to organize payment for the dinner, Rich and Jonathan turned up and quickly ended the discussion. Rich said his credit card would be good for the tab. So thanks to …

I thought I had already conquered the jet lag last night when I fell asleep at 22:00 (that's 10 pm...). But then I woke up somewhere around 2:30, read a book for a while until I decided to give up and have a nice breakfast. I kind of like jet lag though, it is a nice feeling to get out of bed 5:30, when no one else is awake, and birds are singing outside.

There would be a lot to tell about the conference, but you kind of find summaries from many live bloggers on Planet MySQL. One interesting aspect of the conference of course was to meet so many interesting people, many of whom I work with of course, but meeting them in flesh is still great. And Santa Clara being in Silicon Valley adds another funny revelational feeling to it all. For a European Yahoo, Google, Digg and others are Internet companies and seeing that they actually do have tangible offices in Silicon Valley was a …

Jay’s opening lines regarding the final MySQL Conference keynote speaker was: “I work with a lot of data. I think peta-bytes, maybe exa-bytes”. This was relating to Jacek Becla from the Stanford Linear Accelerator Center, giving his presentation on “The Science and Fiction of Petascale Analytics”.

The goal of the Large Synoptics Survey Telescope (LSST) is the storage of 50+ PB of images and 20+ PB data.
Let’s just clarify the size. 20 PB of data = 20 years of HD Movies = 2000 years of 128kb MP3

The next database frontier is obviously building huge databases. What part will MySQL or other relational databases play? Some interesting facts were.

• The Digital Universe Created 161 Exabytes of data last year.
• Google, processes 20 petabytes of data per day.

The Operational plan for LSST Project Timeline is 10 years, only starting in 2014. The timeline:

Over the past several years whether I am working with a small company or a fortune 500 client I have seen lots of issues and mistakes made around the configuration, setup, and ongoing maintenance of disk on Unix and Linux Servers. This is not only an issue with MySQL shops, rather it can be an issue with all database setups whether it is Oracle, DB2, or Sybase. Neglecting the disk is setting yourself up for long term issues. These mistakes often force companies to throw more and more hardware at the problem… Lets look at some common mistakes around disk:

#1 The problem is always an IO problem, and remember spindles not capacity

In performance disk is everything. It makes you happy, it makes you sad. Learn to love it. Learn to hate it. Learn to understand it. Everything eventually comes back to disk. Take this example: Lets say you have a bad query that you fix with an index. Why …

The messages going back and forth on the “close sourcing” or paying to make use of some “plugins” /addons within MySQL are flying still! And in my opinion this is getting way out of hand. < DISCLAIMER >I work for Sun/MySQL as a senior consultant but claim no special knowledge or agenda here. The comments here are simply my opinions. </ DISCLAIMER> I can not help but look at all the hubbub and laugh a little bit. The vast majority of what I have read seems way off base (more of a he/she posted this, fifth hand retelling instead of from official channels). But there is a lot of FUD floating around, and I keep seeing more and more legit news sources picking up on this “massive change to licensing”, which In my opinion it really is a non-story… because there is no massive change.

What is the issue?

One thing that still springs to mind when I think of the MySQL User Conference last week is Sun's opening keynote. While talking about Sun's market penetration with open source software, Jonathan Schwartz, Sun's CEO, slipped in a short mention of the mobile market saying something along the lines of "Sun is going to be entering the mobile market later on this year". He didn't spend more than 5 seconds talking about it, moving on to the acquisition of MySQL.

Last year, Sun already made an announcement of …

I will be at the Mashable Party at Webster Hall on May 16, 2008. The party starts at 8PM and goes till 4 AM although I won't be staying till 4.

There are less than 100 tickets left. If you are attending and use MySQL, Solaris 10 or Sun hardware in your environment, I would love to chat with you.

And, there are no presentations :)

------ EVENT DETAILS ----

What: MashBash NYC : Mashable?s NYC Spring Party!
Who: 2,500 Sold Out Crowd, 400 Mashable VIP Tickets on Balcony, Grandmaster Flash starts the night off
When: Friday, May 16th, 2008
Drinks: Open Bar, 8 - 10 pm sponsored by Kluster
Where: Webster Hall, 125 East 11th Street, New York, NY

Schedule for the …

Welcome to Tip #1 in MySQL Replication Series. In this tip we will go over what to do when you only want to replicate certain data to slave(s). Most general way to tell what is replicated to which slave is to include following configuration directive in my.cnf file depending on your environment and your goals. We will start with slave server side options since you have more flexibility on slave on what to replicate and what not to.

Slave server options:

• replicate-do-db = dbname (or) replicate-do-db = dbname1, dbname2, …, dbnameN
  This option is used on slave server to tell the server to only replicate dbname db on this particular host. You would want to use this if you have a master which is replicating to multiple slaves and each slave may contain different database for read performance reasons.
• replicate-ignore-db = dbname (or) …

Doing Billions of Queries per Day
Read this doc on Scribd: DVPmysqlucFederation at Flickr: Doing Billions of Queries Per Day