I recently was asked the following from a Kontrollbase user via email. Since this question might be asked by others I’m posting my response so that the user community can have the answer available right here, right now. Question “I am unable to locate the slow / general queries list as well as processlist. Does [...]

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want …

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want …

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want …

I was working on a server today that was not hooked up to our usual monitoring systems for one reason or another and I needed to generate a database tuning report. Typically I use Matthew Montgomery’s ‘tuning-primer.sh’ script for this since it’s command line based, simple to use, and generates a number of useful items for tuning recommendations. It’s a great starting point before delving into the deeper aspects of MySQL and the OS.

I ran into an issue with it on this server that was running the MySQL 5.0.77-percona-highperf-b13-log x86_64 build. The error was:
./tuning-primer.sh.1: line 517: 5.000000: syntax error in expression (error token is ".000000")

There were three options to fix this issue

1. Dive into the code and modify it cowboy style
2. Use our typical monitoring against the client’s wishes
3. Contact the developer to get a fix

I hopped on …

We know that the open source + paid support business model works for software products that have extremely large numbers of users, but does it scale to products with medium or small numbers of users?

Software is often described as a stack (see the simplified version below).

Vertical Applications [Installed base = small]
————————–
Middleware (e.g. Database) [Installed base of MySQL = 12 Million]
————————–
Operating System [Installed base of Windows = 1Billion+]

Companies in the operating system layer typically have large numbers of users with a small license fee per user. This dynamic makes it relatively painless for a company to forgo a small license fee in exchange for a larger userbase, and then make money on support. For example, an open source company might forgo the $100 license fee, but charge $15 a seat for support. With large numbers of users, the …

I’m happy to note (this is internal Open Query happiness but I’m pleased to share) that so far we have a 100% renewal rate for our Proactive Services for MySQL subscriptions. Some of the early clients have grown in the initial period and are have now moved to a higher # of hours (this can also be changed upward during a term), which is of course excellent both for the clients and for us.

I was in eager anticipation of this time since the introduction of the concept late last year, as it is of course the essential proof of whether a subscription service actually works over time. Ideally, you’d want renewal to be a simple straightforward process, with the client having experienced the value of the service. This is relatively straightforward in this case, since it’s not an insurance, emergency or retainer type arrangement – the client actually gets benefits each and …

This alliance is an excellent step, showing the maturity, breadth and depth of expertise for MySQL related services! Of course Open Query is an active early member, with our training and subscription services, and initiatives like the OurDelta builds project.

Kudos to MontyW and PeterZ for driving this further while at the MySQL Conference last month.

So, you’ve emailed MySQL Support, they’re working on the problem you’re having. How are they working? What tools do they use? Well, here’s my list:

• IRC – All MySQL Support Engineers work on IRC, it’s our main communication medium. While you’re only getting emails from one Engineer, it’s quite likely they’re consulting with several others at the same time. Many pairs of eyes catch all of the details.
• MySQL Docs, Changelogs, Knowledge Base, Google, etc – There’s a lot of information out there, far too much for any one person to keep in their head at once. So, we have extensive documentation that everyone can access, plus the Knowledge Base available to customers. Also, given that MySQL is a very open project, we have plenty of community members who write about their experiences.
• MySQL Sandbox …

Did you know that by banging your head against the wall you burn about 150 calories per hour? However, there are more effective and less painful ways to exercise (no surprise there). Personally, I like an early morning walk and playing some Wii games around lunch time.

Most companies aim towards high(er) value offerings, sold at a higher price, so that their margin increases. Right?
But what they're actually doing is desperately trying to outrun their own high (and escalating) cost structure. I ask you this: why should a client have to pay for inefficiencies in a provider's organisation? Also, why says that a higher value offering needs to a) be priced higher and b) have a higher profit margin?

This is not the unavoidable way of things, but the reason it's the usual is that you can't just decide to change one aspect (such as a higher value offering), yet keep the way the company is run the same, and then still …