Ok, at least they tried. But it seems SAP has for now put their attempts to rest to smoose up a bit closer to OSS. I guess Oracle-InnoDB deal send enough shockwaves around the SAP HQ to kill of any of the little wishpers that had made the surprising MySQL-SAP deal happen in the first time. Now things have come full circle again, MaxDB development is not only back at SAP as I have noted before, its also back to closed source development. At the same time most big European OSS companies seem to end up in the hands of US based companies.

A while ago Novel scooped up SUSE. Recently MySQL AB was bought up by Sun. The biggest European software maker …

As a rule I always execute the following commands on a fresh database installation. Then for each user that is granted privileges, of course they are given a password and the host permissions are locked down as much as possible for their needs, alternately table and column privs as well. I’m not going to get into the parts the manual covers, but rather mention a couple of things on my mind.

First the initial commands:


mysql> use mysql
mysql> delete from user where User='';
mysql> delete from db where User='';
mysql> update user set Password=password('password_here') where User=’root’;
mysql> flush privileges;


However, one thing I’ve noticed is that when you hand over a server to someone that doesn’t necessarily follow your same understanding or regard to user privilege security, bad things can happen. Such as users created without a password. …

No, this is not a blog post on the endless battle between end user and developers as a result of them not understanding each other. No, this post is about "what determines the value of a software/service company". Is it the number of end users or the developers/service people?

Lets start off with a made up example: What would MySQL AB be worth if, lets say Microsoft and not Sun would have bought it? Microsoft would have gotten a ton of users this way. Maybe it would have been worth the price just for an opportunity to try and kill a competitor (this would of course only partially work due to MySQL's GPL nature). How many developers would quit their jobs? How would that affect the future of the product? Ultimately I would expect the chances for a MySQL product and related services to go down considerably because key developers leaving would diminish end user trust and they would spearhead the creation of alternatives.

Now what …

Last week, we held a conference for leading financial and industry analysts from around the world. My keynote presentation is below - broken into two parts for ease of viewing. One analyst remarked, "but this is pretty much what you said last year."

I responded with, "That's the point."

If you'd like more specifics on our financial performance (directly from Mike Lehman, our CFO), views from the marketplace (from Don Grantham, our Global Sales and Services) or specific product roadmaps (from the heads of our Systems or Software businesses), just click here...)

I came across this very thought provoking blog post by Brain Aker of MySQL and /. fame. I think he raises some very important points about OSS development and how to create a successful new project. However some of the advice can also be applied retroactively to existing projects. I especially find his comments regarding "old boys clubs" important. Sometimes when you have a successful project it becomes hard to manage the influx of new people. So the old boys start to feel most comfy when they ignore the new guys. Patches are a good basis (though you still need people to have a look at the patches) of judgement to let new guys in. After all with good patches the project should be moving forward. I think in PHP we have a very similar policy to the "Three Commits, Ding, Ding, Ding" policy Brain applies. And that is a good thing.

A bit more on the "old boys club" stuff …

We’ve got a lot of queries recently on the MySQL docs team address about the documentation (particularly man pages) for MySQL on Debian/Ubuntu.

The source of the original problem was reported as a Debian bug. The assumption from the reading of the license in this instance is that you are not allowed to distribute MySQL documentation unless you’ve asked first, and that the documentation is not released under the GPL license.

The original license was misunderstood in this respect.

In fact, the license as originally quoted in that bug does allow you to provide the documentation if you are providing the MySQL software.

In addition, regardless of how you interpret the license, all of our documentation, including installable man pages, has been available on …

Well we are all quite excited about what's going on with MySQL AB. We have read the talk about MySQL 6.0 and the upcoming Falcon storage engine. We have read the news about SUN having bought up MySQL AB and how this is going to improve their abilities. We also took note about Monty's first blog posts and the announcement of the Maria storage engine. But in the middle of this, I wonder if the priorities are sorted properly.

Again, the above mentioned stuff is all big news and very important. But since quite some time I have not heard anything about MySQL 5.1. Wasn't 5.1 supposed to be GA last fall? Aren't we all really excited …

We just had an internal discussion about if sticking with PHP limits your career options. And just now (coincidence?) I noticed blog posts in the PHP and MySQL community noting similar concerns. The issue is that there is simply not enough top qualified talent that knows LAMP well enough to hire. Or maybe its just too hard to find them? It seems all the good guys are already hired. As a result companies end up looking for other technology, not because they actually believe that these technologies are any better or worth the license fees that these usually require to be paid up ..

So whats the problem here? Well I think one of the key issues is that LAMP focus on solving issues with a very non academic way. This implies that …

Please read the luculent Safe Harbor Statement at the bottom of this page....

We released our official earnings on Thursday last week, after pre-announcing the news one week prior alongside the announcement of our intent to acquire MySQL.

Our second quarter financial announcement came down to this: we doubled our profitability compared to a year ago, with $260 million in net income on revenues of $3.6 billion, while generating $336 million in cash from operations. We also repurchased $750 million of our own shares within the quarter, and reaffirmed our guidance for the full year of low to mid …

I passed the MySQL 5.0 DBA I and II certification tests today with very nice results. Just figured I’d post that so it’s verifiable that I’m not entirely spewing nonsense and general rabble. Today is a good day, and I will celebrate with the finest wines, and choicest of meats.

Exam Date: Monday, January 28, 2008 at 9:00 AM
Candidate: Matthew Reid
Candidate ID: MYSQL005372
Registration #: xxxxx2740
Exam Series: 005-002
Exam: Certified MySQL 5.0 DBA Part I
Validation #: xxxxx5662
Grade: pass

Exam Date: Monday, January 28, 2008 at 10:30 AM
Candidate: Matthew Reid
Candidate ID: MYSQL005372
Registration #: xxxxx7164
Exam Series: 006-002
Exam: Certified MySQL 5.0 DBA Part II
Validation #: xxxxxx5956
Grade: pass