I’ll be speaking on MySQL Users Conference 2010. Talk: MySQL Architecture Design Patterns for Performance, Scalability, and Availability, 11:55am Thursday, 04/15/2010. Details.

I just got a sneak peak at Domas’s slides for his High Concurrency MySQL session next Tuesday.  With apologies to the fine folks presenting at the same time as him, in my opinion you really don’t want to miss his presentation if you care at all about concurrency.  Lots of details about MySQL best practices and how real world problems have been solved.

On this big trip, I made particular effort to finally visit Monty at his home near Helsinki. Somehow, in all my years at MySQL AB, this never happened – a sad omission. So, I spent the Easter days with Monty, Anna and now 5yo Maria.

I’m not a fan of most meetings, and in many cases in-person meetings are not actually necessary to get things organised or done, but I think this was both most enjoyable as well as productive for our respective businesses and joint interests. Good company, discussion, food, drink, sauna… fabulous.

It’s a great pity we live on opposite sides of the planet, as we do get along very well together. We definitely don’t agree on everything, but we’re always absolutely direct with each other, and try to provide good arguments whenever we disagree, to explore things further.

This release of Workbench has shown some major improvements. Especially in looks and feel, so I want to thank the team for those improvements at this time. I would like to take the opportunity though to point out some short commings or inconsistencies – at least in my oppinion. These are not bugs per say – for those see the bug reporting system – but just things that make using WB not as much pleasure as it could be.

1.) Triggers: Why can’t the handling of triggers be consistent with the way MYSQL stores/handles triggers. Namely each trigger as its own entity. Currently triggers just roll together in the sample as shown below in an example that does nothing but is just used to describe the problem

– Trigger DDL Statements
DELIMITER $$

USE `test`$$CREATE DEFINER=`admin`@`%` TRIGGER `beforeinsert`
BEFORE INSERT On table1
FOR EACH ROW
…

If you are attending this year’s O’Reilly MySQL Conference & Expo, it is with great pleasure that I invite you to attend my presentation featuring Securich, the MySQL user administration and security plugin. It is a user friendly tool which will help make user management and general database security much more versatile and fun than ever before.

The session will be held at 10:50am on Wednesday 14th April 2010 at BallRoom A.

http://en.oreilly.com/mysql2010/public/schedule/detail/13351

So come on over and `grant all on *.*` no more :)

Hasta luego mez amis
Haben eine sichere fahrt

MySQL database dumps can be automated via a CRON job, without providing a password, to achieve the same follow these steps

Edit you my.cnf and make the following entries

[mysqldump]

User=root

Password=secret

Save and exit the my.cnf file

Now write the following script to the CRON job

#! /bin/sh

mysqldump –u root –all-databases –routines

>/var/lib/mysqldump/mysql.dump

Automating the database dumps without using the password will make the maintenance easier.

-Death

…

In a couple of weeks at the MySQL Conference, I will be co-presenting a session “Database Operations At Scale” with some of my colleagues from Facebook’s database operations team.

What sorts of questions do you folks have regarding database operations at Facebook? Leave a comment here and we’ll see if we can incorporate that into the presentation.

The InnoDB Plugin manual is now available on the MySQL web site.

The Tokutek/Sunfish entry into the next America’s Cup promises to bring the America’s cup back to the USA’s east coast. The sailboat, named '; Update Race set time=1 where Team='Tokutek (we’re trying to win using a SQL injection attack) features a single-hull pontoon-type hull carrying a lateen sail mounted to an un-stayed mast. The fiberglass hull carries a crew of one or two. The double-plus secret keel technology features a daggerboard keel, an overall length of 4.22m, a beam of 1.24m, and a hull weight of 59kg. The 6.0m2 mainsail provides a D-PN of 100.7, and an on-board computer comprising an Android in a zip-lock sandwich bag running MySQL with TokuDB.

So, Open Query is going to move to Silicon Valley. We all know there’ve been a few booms (and accompanying busts), but it is -still- where much of the big business of the online (and thus database) world is; and particular with projects/products like OQGRAPH, it makes sense for us now. Of course we can (and) do our other services from anywhere, but it’s quite important to be local to more of our clients – can’t beat face-to-face contact, right?

About half of our people will be in Santa Clara for the upcoming MySQL conference anyway, so that’s also an excellent time to meet (we don’t, often, in real life) and plan ahead.

More later.