Here are some quotes from a recent article talking about Oracle's maintenance and support fees:

Before Oracle acquired BEA earlier this year, the company charged 18% to 20% for support and maintenance. Oracle increased those fees to meet its own structure and also raised list prices on most BEA products.

That didn't sit well.

and


One Java-centric VAR, who spoke on the condition of anonymity, said some of his BEA WebLogic customers are moving to alternative application servers just to get away from Oracle.

and

"What company comes in this climate and not only jacks up prices but support prices as …

Here are some quotes from a recent article talking about Oracle's maintenance and support fees:

Before Oracle acquired BEA earlier this year, the company charged 18% to 20% for support and maintenance. Oracle increased those fees to meet its own structure and also raised list prices on most BEA products.

That didn't sit well.

and


One Java-centric VAR, who spoke on the condition of anonymity, said some of his BEA WebLogic customers are moving to alternative application servers just to get away from Oracle.

and

"What company comes in this climate and not only jacks up prices but support prices as …

Here are some quotes from a recent article talking about Oracle's maintenance and support fees:

Before Oracle acquired BEA earlier this year, the company charged 18% to 20% for support and maintenance. Oracle increased those fees to meet its own structure and also raised list prices on most BEA products.

That didn't sit well.

and


One Java-centric VAR, who spoke on the condition of anonymity, said some of his BEA WebLogic customers are moving to alternative application servers just to get away from Oracle.

and

"What company comes in this climate and not only jacks up prices but support prices as …

While working with Monty Widenius on a bug I reported in MariaDB I was surprised to not get an IRC response for a few minutes. When committed Monty can identify, create a workaround, and patch a problem in code before you have time to read all the responses he also types. See my Monty’s Monument “Passion is a timeless wisdom” comment. One thing I forgot to say in that entry was, while 9pm in New york, it was at last 3am-5am Monty time.

We all love memorable quotes, so here is one.

“sorry, machine died; First time in years”

[9:40pm] montywi: then just try compiling mysqld.o, no need to wait for everything else...
....
[9:58pm] rbradfor: make is clean.
[9:59pm] montywi: sorry, machine died;  First time in years
[10:00pm] rbradfor: laughs …

In the last three updates to this blog, I've tried to set out a clear direction of where Sun's headed. I've talked about our three basic priorities:

1. Technology Adoption
2. Commercial Innovation
3. Efficiently Connecting Adoption and Commercial Opportunity.

I'm hoping you've got a clear picture surrounding the first of these two priorities - how and where we drive software adoption, and focus our commercial efforts.

So now I'd like to talk about the linkages - while also addressing one of our biggest strategic challenges, our scale.

Selling Scale

First, why is scale a challenge for Sun? To be clear, I'm not talking about purchasing scale. As I've said before, we use innovation to drive product profitability, not simply bulk purchasing leverage. The scale to which I'm referring is selling and marketing scale. With Sun's current products, we could be selling to twice …

My previous blog entry on MySQL scalability on the T5440 is now completed by a Sun BluePrint that you can find here.

See you next time in the wonderful world of benchmarking....

My previous blog entry on MySQL scalability on the T5440 is now completed by a Sun BluePrint that you can find here.

See you next time in the wonderful world of benchmarking....

My previous blog entry on MySQL scalability on the T5440 is now completed by a Sun BluePrint that you can find here.

See you next time in the wonderful world of benchmarking....

Today I come back from the dentist, if that wasn’t bad enough news, I get an email from Google AdWords titled Your Google AdWords Approval Status.

In the email, all my AdWords campaigns are now disapproved, because of:

SUGGESTIONS:
-> Ad Content: Please remove the following trademark from your ad:
mysql.

Yeah right. I can’t put the word ‘MySQL’ in my ads. How are people to now find me? It would appear that many ads have been pulled not just mine. Is this a proactive measure by Google? is this a complaint from the MySQL trademark holder Sun Microsystems?

I’d like any comment, feedback or suggestions on how one can proceed here.

It reminds me of the days CentOS advertised itself as an “Open source provider of a popular North American Operating System”, or something of that nature.

One of the pain points of upgrading any software package is knowing which version to upgrade to when the time comes. With software that is frequently updated, like MySQL, choosing a version that provides new features and addresses issues you are aware of, without also being exposed to other issues is an added complexity.

This week, I added another new feature to our documentation, spurred on by Baron Schwarz’s idea for a ‘reverse changelog’.

As Baron noted, the idea is to report the bugs reported in a specific version, and then provide information about the version in which each bug was fixed, so that you can determine which version you need to choose when upgrading to avoid that bug.

You can see the output for 5.1: …