7I find it interesting, that many people "need" to put me in a box called CTO or VPEng.

Reminds me of [ancient] Mork and Mindy, where a psychologist got miffed, when Mork successfully stuck a round peg in a square hole... ("how did he do it?" "I don't care... he ruined by block test")

• A CTO dreams up technologies, solutions, has little constraints
• A VPEng deals with processes, Quality, releases, schedules, mentoring
• An Architect Designs systems (the more systems you know, the more choices for "the" right technology you have)

read more

The MySQL developer tools team announces the availability of version 5.2.41 of the MySQL Workbench GUI tool. This version has significant improvements in several parts of the tool and also includes the new Migration Wizard plugin.

The new Migration Wizard presents an easy to use GUI for migrating databases from third party products to MySQL. In this initial release, support for Microsoft SQL Server is included, in addition to other products that support ODBC, such as PostgreSQL.

Other improvements include:

• More than 100 bug fixes
• Code completion in the SQL Editor (beta)
• Better handling of schema synchronization in modeling

For a full list of issues fixed in this release, see  http://dev.mysql.com/doc/workbench/en/changes-5.2.x.html

Please get your copy from our Downloads …

MySQL Workbench 5.2.41 introduces a new Migration Wizard module. This module allows you to easily and quickly migrate databases from various RDBMS products to MySQL. In this initial version, migrations from Microsoft SQL Server are supported, but it should also be possible to migrate from most ODBC capable RDBMS as well, using its generic RDBMS support. Additionally, you can use it to perform MySQL to MySQL database copies, which can be used for tasks such as copying a database across servers or migrating data across different versions of MySQL.

So let’s get our hands dirty and run through the Migration Wizard in order to migrate a Microsoft SQL Server database to MySQL. In the rest of this post I assume that you have:

• A running SQL Server instance in which you have proper access to the database you want to migrate. (I’ll call this database from now on the source database). I have a remote SQL Server 2000 instance …

So in the summer of 2007 I switched from Windows to OSX which also meant switching from Thinkpad to Macbook Pro. While there were some details I liked on the Macbook Pro, like the at the time quite innovative magnetic design on the lid latch, overall I was sad to not be able to use a Thinkpad. So it also came that my first Macbook Pro had to repaired 3 times in total. Despite having bought the insanely expensive AppleCare this meant having to drop off my laptop for several days (usually 5 business days) or paying an "express service" charge. In general I believe Macbook's to be pretty decent, but not as sturdy as Thinkpads (starting with the availability of spill resistant keyboards). More over they tend to skip on connection options and are overpriced. Then again I really don't care about the price that much. I use my laptop for pretty much everything, from work to DJing to private use. …

I wanted to make sure that John's blog got some attention. If you have not seen this yet:   New home for MySQL Random Query Generator docs

I still do not know how this works for MySQL, but whatever the thiinking is, I do not like it. There is a flow of new features coming into the GA releases which is my mind usually isn't a good thing (i.e. a new feature means a new source of bugs). This is particularily bad in the case of MySQL due to the risk of regression bugs and lack of modularization.

And I know, what you are going to say, if we didn't get those new features then that old GA version would not be useful, if for no other reason so due to Moore's Law, the software has to keep up with what is going on in the world of Hardware. But MySQL has never been good at that, for example, can someone explain why the sample MySQL config file for big MySQl server, my-huge.cnf, starts with this comment:
# Example MySQL config file for very large systems.
#
# This is for a large system with memory of 1G-2G where the system runs mainly
# …

Yo!

    My idea for a JSON based SQL schema tool that I wrote about some time ago has been on the backburner as I wanted to finish two other projects:

• A better JSON import tool to substitute the old mysqljsonload.
• Fix up mysqljsonexport to align it with mysqljsonimport.

These two projects are now done and the program are ready for download from Sourceforge, mysqljsonimport from here and mysqljsonexport from here. There is some serious changes to these program here, for example, the multi-threading in …

Save money on your ticket to MySQl Connect by registering on or before the 27th of July. This is your chance to talk to the engineers that write MySQL, the folks at the big companies who are doing amazing things with MySQL, and network with other MySQL-ers.

And you can catch the MySQL Community Team at these events:

• August 1st Los Angeles Moodle Moot
• August 1st Los Angeles MySQL Users Group*
• August 2nd San Diego PHP Users Group*
• August 11th-12th Northeast PHP Conference
• August 13th Boston MySQL Users …

Due to the tragedy that took place in Aurora, CO, and it's close proximity to our event in Broomfield, collectively our team has decided to postpone this MySQL Tech Tour.

We are planning on rescheduling for mid September.

If you haven't already registered for MySQL Connect, now is the time to do it.

Looking for the right reason to attend? Here are the TOP THREE REASONS...

• You'll get the chance to hear directly from users including PayPal, Verizon, Twitter, Facebook, Ticketmaster, Ning, Mozilla, CERN, Yahoo! and more, about best practices for deploying MySQL based solutions.
• Don't miss this unique opportunity to meet the engineers developing and supporting the MySQL products, all in a single location. You'll be able to ask them all your questions and provide them feedback.
• Acquire detailed knowledge about the latest …