MySQL AB today announced the appointment of industry visionary Tim O?Reilly to its corporate board of directors. The company also announced that Dr. Jeffrey Pugh has joined its senior management team as vice president of engineering.

Are you seeing a MySQL error that says InnoDB support isn’t enabled, even though it is? This article explains why it happens and how to fix it. The symptom Suppose you call SHOW INNODB STATUS or another InnoDB-specific command and MySQL reports the following error: “ERROR 1235 (42000): Cannot call SHOW INNODB STATUS because skip-innodb is defined” Yet you search the MySQL configuration files and find that’s not true. And you know you have InnoDB tables, too.

I’m continuing to add new tools to the MySQL Toolkit. MySQL Deadlock Logger is for extracting and storing information about the latest recorded InnoDB deadlock. It’s not only easy to view the information from the command line, it’s dead simple to store it back into a MySQL table for analysis. I think most users will find it handy to create a cron job to record the deadlocks automatically for later analysis.

The topic of database stored procedures does not cease to divide the community of database application developers and DBAs. There are many articles around, expressing various opinions about this subject. But what do you think?

Please let me know and take this survey. The survey contains 5 multiple choice questions, and will take about 1 to 5 minutes to complete.

The results will be posted soon here on my blog at http://rpbouman.blogspot.com/. Thank you in advance!

(Disclaimer: I'm an employee of MySQL AB, but this survey does not in any way relate to my position with my employer. Also, I have made an utmost effort to write an unbiased survey. If you feel that something is wrong in this regard, please post a comment on this post.)

Today I was cloning the master using LVM Snapshot and found it was taking quite a while to catch up, which highlighted replication could be the limiting factor for this system quite soon, so I decided to check what is limiting MySQL Replication speed.

My first idea was to check it based on slow query log, happily the server was running MySQL with slow query log with microsecond resolution so I could check exactly which update queries take most time to execute. Unfortunately it did not work because Slave thread seems to have problems picking up long_query_time when it is set online, meaning changing it via
set global long_query_time=0 and restarting slave does not pick up the change.

I of course could just restart MySQL but this would make replication to be delayed few more hours …

A few days ago I had some good news on the new MySQL Bulk loader for which we added support in Kettle.

Today French i18n/translation hero Samatar checked in the code for the exact oposite, built on the “SELECT … INTO OUTFILE …” statements that MySQL supports.

As you can see, this job entry allows you to export the content of a MySQL database table to a flat file. Again, this is done completely by MySQL and therefor works at optimal speed (really fast!)
We added all kinds of helpers in the GUI so that you can easily select the table and the columns to export. All you need to do is give it a filename a separator and off you go! Not only that, you can use variables to specify almost all parameters of the job entry.

In short: another great option for those of us that work with MySQL …

Matt Casters has been around the open source business intelligence, ETL, and data warehousing scene for quite some time. He is the original developer of Kettle, an open source Java tool now packaged by Pentaho as Pentaho Data Integration. He's also doing a couple a couple of absolutely dynamite sessions at the MySQL conference in April, which I asked him recently to comment on.

Our own Roland Bouman is a huge Pentaho fan, and is also doing a session called …

Zend has announced that the latest update of their integrated platform offering, Zend Core 2.0, includes MySQL 5.0 as well as many other improvements to the PHP runtime system, faster performance on Windows, integration with Microsoft's FastCGI implementation, and a bundled Zend framework. In my view, the Zend Framework could well be the most important piece of technology here.  Many people think of Zend as being a tools company, but it is the framework that gives developers such a huge …

When you have a node failure the best practice is to restart the ndbd node as soon as possible.
This post illustrates what happens with restart times:

• if you have configured TimeBetweenLocalCheckpoints wrong and have a high load
• if you don't restart the failed ndbd node immediately
• how long time it takes to resync 1GB of data with and without ongoing transactions.
  

5.0 and 5.1 differences in node recovery protocol

In 5.0 the node recovery protocol copies all data from the other node in its node group.
In 5.1, there is a new node recovery protocol, called "Optimized Node Recovery", called ONR below.
When a node has failed, and is restarted, it will recover its local logs (Local Checkpoint (LCP) + redo log) and only copy the changes that has been made on the started node.
This is faster than copy all information as done in …

MySQL Connector/Net 5.0.5 a new version of the all-managed .NET driver for MySQL has been released.

This is a bug fix release for the current production branch of Connector/Net.
Version 5.0.5 is suitable for use with any MySQL version including MySQL-4.1, MySQL-5.0, MySQL-5.1 beta or the MySQL-5.2 Falcon "Preview".

It is now available in source and binary form from the Connector/Net download pages at http://dev.mysql.com/downloads/connector/net/5.0.html and mirror sites (note that not all mirror sites may be up to date at this point of time - if you can't find this version on some mirror, please try again later or choose another download site.)

What happened to 5.0.4?
We had 5.0.4 packaged up and ready to go and then discovered that a previous bug fix was not complete.  Rather …