Falcon engine is here! It seems that MySQL is pushing very hard to have its own transaction engine ever since Innodb was acquired by Oracle. MySQL should buy Innodb long time ago. Now they are paying for the price!

On the bright side, I do believe the developers at MySQL will do a good job and come out something better than Innodb :-)

In the next few weeks, I will do some benchmarks to how the baby falcon doing.

http://www.mysql.com/mysql60/

One of the cool capabilities that's part of our Enterprise subscription offering is MysQL Enterprise Monitor.  This week at our user conference in Japan we showed a preview of the forthcoming Japanese version.  I don't know what it says, …



One of the most appreciated keynotes at the ongoing Japanese MySQL Users Conference was by Yukihiro “Matz” Matsumoto, the creator of the Ruby language.

Me and Matz at MySQL UC Japan Day 1 2007-09-11

Matz was preceded by an impressive set of keynoters, moderated by MySQL K.K. President Larry Stefonic, also Senior Vice President of Asia Pacific at MySQL AB :

• His Excellency Mr. Stefan Noreén, Ambassador of Sweden to Japan
• Mårten Mickos, CEO, MySQL AB
• Masahiko Yoshida-san, Director, Hewlett-Packard Japan, Ltd.
…

If everything seems under control, you're just not going fast enough --Mario Andretti

The performance optimization options available are too numerous and often confusing. You need to keep the design simple by minimizing the number of optimizations required. Choosing the optimizations with biggest impacts is easy when you align them to the appropriate process in the data warehouse:

ETL performance

1. Database bulk load
2. Assuming that sufficient hardware capacity in terms of CPU processing power and disk throughput is available to support the parallelism:

• Task parallelism
• …

So, someone had a great idea to go back through the Developer Zone, which has become a bit disorganized of late, and put together an article with links and summaries for all the Dev Zone articles that discussed MySQL 5.1 features. I have done so, and also linked in many community member's blog articles and tutorials to give everyone a good dose of the features that make MySQL 5.1 worth investigating.

MySQL AB today announced a major new version of MySQL Enterprise, its commercial subscription service -- adding many new features to make it easier and more affordable for corporate database developers and DBAs to manage their high-growth Web sites and critical business applications.

In addition, the company is now featuring free-of-charge 30-day trial subscriptions for the new MySQL Enterprise service on its Web site at www.mysql.com/enterprise.

The MySQL Enterprise Fall 2007 Release was unveiled this morning at the inaugural Japanese MySQL Users Conference being held here this week in front of hundreds of MySQL users, customers, partners and employees.

MySQL AB today announced that it plans to release alpha and beta versions of several new Free and Open Source Software (FOSS) products this month, including a 'release candidate' of MySQL 5.1 -- a major new upgrade of the world?s most popular open source database server.

The announcement was made this morning at the inaugural Japanese MySQL Users Conference being held here this week.

Go see either my Flickr stream, and I’ll get things onto my Gallery as well.

MySQL is today releasing a new ODBC driver, under the version number ODBC 5.1. It is a partial rewrite of the the original MyODBC 3.51 code base, originally developed by Monty and Venu Anuganti, including individual parts of the current 65K ODBC 5 code base. It is designed to work with all MySQL versions starting with MySQL 4.1.

The original ODBC 3.51 driver was incomplete and admittedly somewhat of a quick hack, containing some debatable code. For that reason, Connector/ODBC 5 started as a complete rewrite. After 2 years it had 65 KLOC, but no tests and was in part overdesigned. That project was started but never finished, and had some deep Qt dependencies.

In the meantime, the original ODBC 3.51 has had 6 new releases and over 200 bugs fixed. As for ODBC 5.1, debatable parts of the code have been …