In case you have not already noticed, Workbench 5.2 alpha / preview release of MySQL's premier development and design tool, has been announced.

For an independent preview, you can also see here. 

The NoSQL movement has been gaining some steam lately, with discussion forums and mailing lists popping up all around the web.  Despite having a career that has been centered on the RDBMS, I have made no secret that I think we have gone too far down with our RDBMS for everything mindset.  I think we need to add a few more tools back into our data toolbox. 

Today, 99.5% of new data centric developments started will use a RDBMS by default.  Maybe .5 of a % will consider using something as obtuse as a NoSQL platform.  By experience I know the majority of people discussing NoSQL platforms today are web developers.  In fact there is almost a sense of trying to trying to keep this under the radar of DBAs.  If we don’t talk to the DBAs about this stuff then they won’t bother us with all that …

Stealing the announcement news from Selena’s blog post:

I’m happy to announce that Portland, OR will be host to the next OpenSQL Camp, Portland. We’ll be holding it November 14-15, 2009.

Patterned after the first Open SQL camp held in Charlottesville, Virginia, USA, in November 2008, we’re inviting any and all database practitioners (even the non-SQL, non-relational ones!) to join us for two days of deep database geeking.

To quote:

“Attendees of this conference are mostly open source developers and end users/open source enthusiasts. The goal of this event is to spread the word about the vibrant communities and large ecosystems around Open Source Databases and to educate the attendees about what alternatives exist to …

In this post I’m going to talk about how TokuDB’s implementation of auto increment works, and contrast it to the behavior of MyISAM and InnoDB. We feel that the TokuDB behavior is easier to understand, more standard-compliant and offers higher performance (especially when implemented with Fractal Tree indexes).

In TokuDB, each table can have an auto-increment column. That column can be used as any part of a key, but it doesn’t have to be part of any key. The value produced by auto incrementing is always greater than the previous maximum value for that column. There are some cases where auto-incremented values are skipped, such as when a transaction aborts, which “uses up” auto-incremented values.

This behavior is close to that required for SQL:2003 (see SQL:2003 at wikipedia), which specifies that each table provides one unnamed sequence which behaves essentially in the way we implemented auto increment. The …

Last week we had a lively panel discussion moderated by Dave Nielsen, founder of CloudCamp, with leading experts in cloud computing on the panel: Chander Kant (CEO, Zmanda) & Michael Crandell (CEO, RightScale). Chander and Michael shared their insights into how their customers are using cloud computing and achieving new levels of reliability and recoverability. Here is a video archive of the panel. 

This panel discusses how you can migrate your apps and data to the cloud in a way that’s affordable and reliable and how to integrate the cloud into your IT strategy. Also hear about real-world examples of companies using the cloud for data backup and recovery and understand the hurdles to moving to the cloud, and how you can overcome them.

  …

In this post I’m going to talk about how TokuDB’s implementation of auto increment works, and contrast it to the behavior of MyISAM and InnoDB.  We feel that the TokuDB behavior is easier to understand, more standard-compliant and offers higher performance (especially when implemented with Fractal Tree indexes).

In TokuDB, each table can have an auto-increment column.  That column can be used as any part of a key, but it doesn’t have to be part of any key.  The value produced by auto incrementing is always greater than the previous maximum value for that column. There are some cases where auto-incremented values are skipped, such as when a transaction aborts, which “uses up” auto-incremented values.

This behavior is close to that required for SQL:2003 (see SQL:2003 at wikipedia), which specifies that each table provides one unnamed sequence which behaves essentially in the way we implemented …

One of the things about supporting multiple storage engines is that there is "no one way" to say "this is what we have".

Michael Widenius solution was to create a file called an "FRM" for MySQL that would work as a one to one ratio between table information and engine information.

All of the first engines were "stupid". Meaning that, the kernel handled lots of heavy lifting for them. As engines like Innodb were added, which were a lot more advanced, there was some friction.

Innodb keeps its own data dictionary, and so have a lot of the engines that have come after it.

This creates a very nasty problem, and a set of limitations. You can't do a lot of online work, because of the nature of ownership of "this is the real information".

And in the case of a crash? You can end up with orphaned tables or corruption on ALTER TABLE (which is very hard to make happen... but it can). …

The morning find for me was this written out entry of Kirrily Robert's OSCON keynote Standing Out in the Crowd :
http://infotrope.net/blog/2009/07/25/standing-out-in-the-crowd-my-oscon-keynote/

Some of the highlighted quotes strike home with me:

I’d never contributed to an open source project before, or even considered that I could.

but the barriers to entry seemed high.

One of my main concerns with Drizzle is that we make sure that both of the above does not happen, for women or men. I want people to feel that contributing is something that is very easy to do. We have been setting aside tasks in a …

At the May 2009 Boston MySQL User Group, Giuseppe Maxia of Sun Microsystems gave a presentation about MySQL 5.4 with use cases and benchmarks to show how it outperforms all other current MySQL releases (including the Google patches and the OurDelta/Percona releases).

The slides can be downloaded from http://www.slideshare.net/datacharmer/mysql-54-theory-and-practice

The video can be watched below, or directly on YouTube at http://www.youtube.com/watch?v=giT4SYXuVqA&hl

MyQuery 3.0 is now available, as 3.0.0 Alpha, for download from Sourceforge. I am aware that this is probably surprising for many MySQL users, as the original plan was to release 2.4, and now we end up with 3.0 instead, which is the reverse of what MySQL is up to now (going from 6.0 to 5.4).

Now,. jokes aside, the reasons for 3.0 instead of 2.4 is that 3.0 really contains a whole bunch of new features and bug fixes. Among the cool new features are:

• Tabbed editing - This allows you to edit several files at the same time, in different tabs. The old "History" function is still there, although of less use now I guess.
• Dual connections - MyQuery can now keep two connections active at the same time, one for issuing queries, and one for controlling the whole thing. This allows the controlling connection, for example, to issue a KILL QUERY if …