This is just a post to let you 5.0 users know that 5.0.96 is now available.

You may have read about some of the security bugs fixed in the recent 5.0.95, and now 5.0.96 is available (it’s been nearly 9 months since 5.0.94 was released – so this is quite a lot of activity as far as 5.0 is concerned).

So if for some reason you’re still running MySQL 5.0, you should at least upgrade to the latest 5.0.96.

The upgrade process should be smooth and simple if you’re already running 5.0 (just be safe and backup your data first though).

You can download 5.0.96 from here:

http://downloads.skysql.com/archive/index/p/mysql/v/5.0.96

And if you’re interested in the 5.0 changelogs, I have direct links to them here (just look for MySQL 5.0):

…

If you’re attending the conference, be sure to stay the extra day (this Friday) for the SkySQL and MariaDB Consulting Lounge and Solutions Day.

You can register for the Free Solutions Day here (just name, email, company, and country):

http://www.skysql.com/mysql-solutions-day

And if you’re around that day, there will be a SkySQL and MariaDB Consulting Lounge open all day long, so feel free to stop by and speak directly with the SkySQL and MariaDB Experts.

More about the Consulting Lounge can be found here too.

I just wanted to give a quick shout out and say thank you to all who have been sharing talks and exciting news from the conference for those of us who weren’t able to attend!

It’s greatly appreciated!

And please keep up the great work.

In addition to the Optimizer features added in earlier 5.6 Development Milestone Releases, the newly released MySQL 5.6.5 Development Milestone Release adds a few more. I think this is a good time to check how all these new optimizer features impact the performance of the DBT-3 benchmark queries. In this blog post, I will compare the performance of the DBT-3 queries in MySQL 5.5 and MySQL 5.6.5.

Test Setup

I used a DBT-3 scale 1 database (InnoDB tables) that was stored on a traditional hard disk, and the InnoDB database size was a bit more than 2.5 GB. The DBT-3 queries were run in two settings: a disk-bound setting with a very small InnoDB buffer pool (50 MB), and CPU-bound with a 3 GB InnoDB buffer pool (all data in memory). The query cache was …

The Problem

In the past, users were unable to take full advantage of the FLUSH TABLES WITH READ LOCK statement. InnoDB simply ignored the flush to disk part. If the table did not have any dirty pages in the InnoDB buffer that weren’t synced to disk (due to sheer luck) then it was safe to copy the .ibd file to another location. Also, the restore was not without its limitations and complications. The .ibd file could not be copied over to another server because InnoDB during import did not fix up metadata required for a trouble-free import. The main problems during import were:

• If the tablespace ID of the IMPORTing instance had changed, for example if the table had been dropped and re-created, then the import would fail.
• If the table …

Wow! A lot has changed since the last MySQL conference I blogged about in 2007.

MySQL has been acquired twice: once as MySQL by Sun and the second time around bundled with Sun when Oracle bought Sun. The conference is no longer organized by O’Reilly but by Percona. And the MySQL database itself has changed — we were talking about new features in MySQL 5.1, which wasn’t released yet, along with Falcon (where did it go?). 5.1 has long since been released as has 5.5, and we’re now talking about 5.6 instead of 6.0. There was no “Cloud” on the horizon, nor was there MariaDB, XtraDB, Drizzle, Schooner, or any of the other offshoots of MySQL, all of which are creating a new buzz around the product.

Yet, one thing remains constant: the vibrant community around MySQL. In spite of all the changes in technology, ownership, versions, …

Hi everybody,

I’m sure you’re all listening about what is happening at the MySQL annual conference (no ? really ?)
So, you can find bellow all the slides from the MySQL Conference & Expo 2012 :

Source : https://www.box.com/perconalive2012

Find some videos  : http://www.percona.tv/2012/04

Related Posts :

• My slides of MySQL Meetup Viadeo / LeMUG Paris
• [UPDATED] Why you should go to Percona Live (London) ?
• …

The MySQL Developer Tools team is announcing the next maintenance release of it’s flagship product, MySQL Workbench, version 5.2.39.
This version contains MySQL Utilities 1.0.5, a set of command line Python utilities for helping performing and scripting
various administration tasks for MySQL. A complete list of changes in this release of the Utilities can be found at:
http://dev.mysql.com/doc/workbench/en/wb-utils-news-1-0-5.html

MySQL Workbench 5.2 GA

•  Data Modeling
•  Query (replaces the old MySQL Query Browser)
•  Administration (replaces the old MySQL Administrator)

Please get your copy from our Download site. Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

…

If you missed my 3-hour tutorial on “Google-Hacking MySQL and More MySQL Security at the Percona Live: MySQL Conference & Expo this morning, the PDF slides are now available at http://bit.ly/mysqlsectut.

There will also be video, which will appear in the next few weeks.

Note: this article was originally published on http://blogs.innodb.com on April 10, 2012 by Kevin Lewis.

The April 2012 InnoDB labs release introduces a new feature in InnoDB that allows you to choose the location of specific tables.  For example, you can place critical tables onto an SSD drive while leaving the system tablespace on a hard drive.  Conversely, you can store you primary database files on an SSD and put a seldom used but very large archive or reference table on a larger cheaper hard drive.

Innodb now makes use of the following existing syntax in MySQL ;

CREATE TABLE  . . .  DATA DIRECTORY = ‘absolute path of data directory’;

CREATE TABLE  . . .  PARTITION . . . DATA DIRECTORY = ‘absolute path of data directory’;

This syntax is used in MyISAM and Archive engines to make use …