We are excited to announce TokuDB® v6.5, the latest version of Tokutek’s flagship storage engine for MySQL and MariaDB.

This version offers optimization for Flash as well as more hot schema change operations for improved agility.

We’ll be posting more details about the new features and performance, so here’s an overview of what’s in store.

Flash

TokuDB v6.5 continues the great Toku-tradition of fast insertions. On flash drives, we show an order-of-magnitude (9x) faster insertion rate than InnoDB. TokuDB’s standard compression works just as well on flash and helps you get the most out of your storage system. And TokuDB reduces wear …

Let’s review today the conference sessions where users and customers will describe their use of MySQL as well as best practices.

Remember you can plan your schedule with Schedule Builder.

Saturday, 11.30 am, Room Golden Gate 7:

MySQL and Hadoop—Chris Schneider, Ning.com

Saturday, 1.00 pm, Room Golden Gate 7:

Thriving in a MySQL Replicated World—Ed Presz and Andrew Yee, Ticketmaster

Saturday, 1.00 pm, Room Golden Gate 8:

Rick’s RoTs (Rules of Thumb)—Rick …

Will you be at MySQL Connect? Alfredo and Sergio will be presenting a couple of Workbench sessions in the MySQL event preceding Oracle OpenWorld in the weekend, 29 and 30 of September.

The sessions are:

Getting the Most out of MySQL with MySQL Workbench – CON9340
Migrating from Microsoft SQL Server to MySQL: The New MySQL Migration Wizard – CON8560 The first one is an introductory session on using MySQL Workbench, which should be the fastest way to get familiar and productive with the tool. The second one will …

I will give 2 talks at MySQL Connect
1. New MySQL Full-Text Search Features and Solutions, where I will focus on the new (and very promising!) InnoDB full text search. I’ve done some benchmarks recently and will publish it here.
2. In-Depth Query Optimization for MySQL, where we will work on the real word examples of MySQL query tuning.

*SESSION SCHEDULE INFORMATION*

Session ID: CON9283
Session Title: New MySQL Full-Text Search Features and Solutions
Venue / Room: Hilton San Francisco – Golden Gate 8
Date and Time: 9/29/12, 14:30 – 15:30

Session ID: CON8811
Session Title: In-Depth Query Optimization for MySQL
Venue / Room: Hilton San Francisco – Golden Gate 8
Date and Time: 9/30/12, 14:45 – 15:45

…

It was recently pointed out to me what a confusing mess the source repositories were for MySQLdb, so I spent a good bit of time cleaning them up. To understand how things got into the state they were in, and where we are going, a brief history lesson  required.

I first started working on MySQLdb in 1998. At the time, the best option for source control was CVS, and I had a local CVS repository for the project, and occasionally put up some tarballs. In 2001, I got the OK to make it an open source project, and development moved to SourceForge. Whatever you might think of SourceForge nowadays, it was a safe place to host your code, distribute files, and you got a couple nice extras like a bug tracker and forums. And SourceForge had CVS, of course, but nothing else at the time. Subversion existed in early form but was not yet available at SourceForge.

SourceForge was a bit slow to pick up on Subversion. Even though …

Not so long ago Fusion-io announced an SDK which provides direct API access to Fusion ioMemory(tm) in addition to providing a native filesystem (directFS) with a goal to avoid overhead from kernel and regular Linux filesystems: ext4 and xfs. This requires a support from application, it should use special calls for IO. With help from Fusion-io, we provide source code of Percona Server which uses direct API access. The main idea that with this functionality you can disable “innodb-doublewrite”, retain ACID compliance by using atomic writes, and in IO intensive workloads gain an additional 30-50% in throughput when compared to workloads on the same ioMemory™ device using an unmodified Percona Server. Further benchmarking results on latency variability reduction expected soon.
Percona Server 5.5.27 with Fusion-io atomic writes is available from Launchpad repository: …

Come meet Tungsten replication and clustering experts. Don't miss these 5 talks:

Managing Worldwide Data with MySQL and Continuent Tungsten by Robert Hodges Replicating from MySQL to Oracle Database and Back Again by Robert Hodges MySQL High Availability: Power and Usability by Giuseppe Maxia Lessons from Managing 500+ MySQL Instances in the Cloud by Ronald Bradford Improving Performance with

Advanced Weblob operations help to use Weblobs most effectively.

Weblob recap

In an earlier post I introduced Weblobs.  Weblob is a new data type that is supported by the Cloud Storage Engine for MySQL (ClouSE).  To a database developer, a WEBLOB behaves (almost) like a regular BLOB.  However, in addition to the regular BLOB functionality, Weblobs can be downloaded directly from Amazon S3 by HTTP URLs.

In MySQL, a Weblob is expressed via a pair of BLOB fields that have a special naming convention: field_name$wblob and field_name$wblob_info.  The latter field is what provides the Weblob functionality.  It can be used to retrieve the direct Amazon S3 URL for the BLOB content. …

"But 63 slides is too much" has been the initial reply to the draft of tomorrows Top 10 MySQL Tips and Mistakes for PHP Developers web presentation (Tuesday, September 25, 2012: 10:00 CET). SQL injection, security and access control, monitoring for indexing and tuning, choosing adequate data types, character sets, how your web application speaks UTF8 correctly, types of connections and their performance properties as well as planning for tomorrow are too important to allow for less slides, Johannes Schlueter and I thought.

Beginners will be presented with a list of pitfalls to avoid. Advanced users profit from the presentation of the latest news put in context. And, of course, we will answer questions. Whoever of us is not speaking at a time is happy to answer your questions in the chat.

A popular NoSQL store claims to have a rich query language. A powerful, portable query language is most important. If not powerful, you have to send multiple commands to fetch the desired data. In the worst case a program must be written which contraditcs the idea of a query language. If not portable, you are back to the 1960th and vendor lock-in. Developing portable applications is impossible. Stepping up from one database to another means rewriting your application. SQL does not have any of these issues. Plus, it is widely known which means low training costs and high understanding of its properties.

SQL - a query language for the relational model

It may seem odd to compare a query language for the relational model (SQL) with access methods of a document store. However, the NoSQL store compared with explains how to map their concepts to SQL in their manual! In the following, I’ll do the same. I’ll consider tables as …