I’ve just submitted “Leverage LSI to Open Source MegaCli” to the Dell IdeaStorm website:

Dell makes some awesome and affordable hardware. Many new Dell machines have the PERC 5/i SAS RAID controller, which is a rebranded LSI MegaRAID SAS.

LSI makes some nice RAID cards. Dell likes LSI. Dell made a deal with LSI to provide the chips for their fancy new PERC 5/i cards.

We buy machines with these cards in them. We need to monitor our RAIDs, rebuild them, and do all manner of other maintenance tasks. We do not expect LSI to provide perfect tools. LSI is a hardware vendor, and it’s understandable that they provide terrible *software*. What is NOT understandable, though, is why LSI’s terrible tools are closed source.

What is further incomprehensible is why Dell is willing to accept this situation on …

This is perhaps the first I've ever heard someone credibly say that Microsoft must now live by open source's rules, or suffer. As Marten Mickos (CEO, MySQL) told The Register, If you won't work with MySQL, PHP and Ruby then you are lost.Wow. Say those same words (and maybe add in "Linux," "Apache," and others) five years ago and Microsoft could have legitimately laughed. But no more. Microsoft must partner with open source companies and communities, or it's business will tank. Not immediately, of course, but imagine a world where Microsoft is an island of proprietary software, surrounded by the... READ MORE

Again, this post is slightly off topic since I'm on vacation, but I wanted to point out a source for good freeware utilities for Windows.  I was looking for a good Windows outliner program and not having much luck and my Java Flex guru buddy Bruce Eckel pointed this site out to me.  If you're looking for a bit torrent client, a photo organizer, HTML editor, registry editor or any of a few dozen other items, this site will spare you the tedious research. The recommended outliner, Keynote, is available under an open source license, but it's no longer in active development.

• Tech Support Alert: …

This week I already had two serious performance regression cases when upgrading from MySQL 4.0 and 4.1 to MySQL 5.0. By serious I mean several times performance difference not just 5-10% you often see for simple queries due to generally fatter code.

The problem in both cases was MySQL 5.0 broken group commit bug.

First I should note I am extremely unhappy how MySQL handled this problem. While working for MySQL we spotted this problem early in MySQL 5.0 release cycle as it was introduced and reported it to everyone we could inside the company - this was over 2 years ago. Few months later I created a bug for this issue to get more public attention to the problem and giving extra motivation to MySQL to fix it. Few months later I blogged about this problem with more …

Just short message that patch enables microsecond resolution in slow-log (see more http://www.mysqlperformanceblog.com/2006/09/06/slow-query-log-analyzes-tools/) for 5.0.37 is available here:
www.mysqlperformanceblog.com/files/patches/patch.slow-micro.5.0.37.diff

The patch for 5.0.41 :
www.mysqlperformanceblog.com/files/patches/patch.slow-micro.5.0.41.diff

There is a popular myth about the SQL GROUP BY clause. The myth holds that 'standard SQL' requires columns referenced in the SELECT list of a query to also appear in the GROUP BY clause, unless these columns appear exclusively in an aggregated expression. MySQL is often accused of violating this standard.

In this article I will attempt to debunk this myth, and to provide a more balanced view regarding MySQL's treatment of GROUP BY at the same time.

MySQL Archiver is the implementation of the efficient forward-only archiving and purging strategies I wrote about more than a year ago. It nibbles rows from a table, then inserts them into another table and/or writes them to a file. The object is to do this without interfering with critical online transaction-processing (OLTP) queries. Several people have asked me to release this code, which I originally wrote for my employer. As it turns out, the delay has been fruitful.

I came across a list of possible questions for a security panel and thought it may be interesting to apply some of them to MySQL and see what happens .

* What is the biggest challenge in data security?

I would suggest it is always the same problem with security - human error. It seems that no matter how well you protect the data, people will be the weakest link in the chain. This could come from social engineering, or to the point where the admin does silly things like deleting/dropping data from the wrong area.

How can we address this problem with MySQL? There are some configuration options that let you force safer interaction like safe-updates etc, but it will never be enough. Backups are probably the best answer.

read more

I came across a list of possible questions for a security panel and thought it may be interesting to apply some of them to MySQL and see what happens .

* What is the biggest challenge in data security?

I would suggest it is always the same problem with security - human error. It seems that no matter how well you protect the data, people will be the weakest link in the chain. This could come from social engineering, or to the point where the admin does silly things like deleting/dropping data from the wrong area.

How can we address this problem with MySQL? There are some configuration options that let you force safer interaction like safe-updates etc, but it will never be enough. Backups are probably the best answer.

read more

OK, this is maybe no big news and maybe old, but I needed an excuse to blog something!

Since MySQL 5.1.15 the /etc/mysql/my.cnf has been added as default location after /etc/my.cnf. This is great and something I like keeping /etc a bit cleaner, but it might be tricky for some not knowing!

I found this the hard way and a bit with red cheeks (I'm a MySQL Support Engineer after all..). After installing postfix-mysql Ubuntu package, which also sets up common MySQL stuff, I couldn't connect to my fresh installed 5.1.19. Confused, I saw it was using a socket setting I didn't specify. So, /etc/mysql/my.cnf was read extra to /etc/my.cnf! I said 'doh!' and saw it was good.

Tip: leave /etc/my.cnf there for a while with a warning like "You're living in the past dude! Check /etc/mysql/my.cnf", or something.

Next would be to read /etc/mysql/config.ini for MySQL Cluster too, but work is on its way to …