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 …

With many other open source projects - like our friends from phpMyAdmin - we're showcasing our software at this year's DotOrg-Pavilion (open April 24th and 25th) and will be happy to talk to you about the past, the present and the future of XAMPP.

The MySQL Conference & Expo is taking place in Santa Clara, April 23-26, and it's not too late to qualify for the early bird discount: If you take advantage of early registration by March 14th you can save $200 off the standard conference fee.

For complete MySQL Conference & Expo details, visit: http://www.mysqlconf.com

In the most recent edition of Database Trends and Applications (hardcopy), there’s an interview with Tom Kyte from Oracle with the focus being the new enhancements coming in Oracle11g. I’m a big fan of Mr. Kyte as he really knows his stuff and is not shy in admitting what Oracle doesn’t do well. Even though I’m no longer an in-the-trenches Oracle DBA, I still follow his columns because his advice can oftentimes apply to other DBMS’s in addition to Oracle.

I was intrigued to see the very first 11g enhancement he noted in his interview - Oracle will now sport a new memory cache that will cache the results (not just the raw data blocks) of SQL queries. Sound familiar? When I first came to MySQL, one thing that quickly caught my eye was the query cache. Now I know the query cache isn’t for everybody, but in the right situations, it can really be a godsend. Seems Oracle has now gotten the same message. And no wonder: for repetitively …

Oracle contributes TopLink to the Eclipse Foundation…Zend releases updated version of Zend Core…FSF seeks partnerships with hardware vendors…and more…

Oracle Proposes Open Source Persistence Project at Eclipse Foundation, Oracle (Press Release)

Oracle Becomes Board Member of Eclipse Foundation , Oracle (Press Release)

Eclipse Foundation Community Awards Announcement, Eclipse Foundation (Press Release)

…

With many other open source projects - like our friends from phpMyAdmin - we're showcasing our software at this year's DotOrg-Pavilion (open April 24th and 25th) and will be happy to talk to you about the past, the present and the future of XAMPP.

The MySQL Conference & Expo is taking place in Santa Clara, April 23-26, and it's not too late to qualify for the early bird discount: If you take advantage of early registration by March 14th you can save $200 off the standard conference fee.

For complete MySQL Conference & Expo details, visit: http://www.mysqlconf.com

Last few days I had a lot of a lot of questions at MySQL Performance Forum as well as from our customers regarding query optimization... which had one thing in common - It is not query which needed to be optimized.

Way too frequently people design schema first and then think how the queries they are looking to be answered can be expressed using that schema... which just does not work as a lot of rows needs to be traversed to get results you're looking for. Here are couple of examples:

GROUP BY Consider SELECT COUNT(*) cnt, page FROM log GROUP BY page ORDER BY cnt DESC limit 10, the query to display top popular pages. There are very many queries of this type in many web applications which do group by one field sort by another and then use LIMIT to output first few rows. This query is not going to be efficient as it needs to traverse a lot of rows …