MySQL DBA and Developer Certification Exams are now in beta! Besides covering the new material in MySQL 5.6, you now have to pass one exam to earn the certification where previously you needed to pass two exams. Signup at Pearson Vue and reserve your exam. Testing will start in October.

The exams for older certifications will not be available after October 31st and the Certification Paths for DBA 5.0, Developer 5.0, Cluster DBA 5.1, and Associate will end at the end of the year. Those certifications are still valid once earned forever. For more details.

The MariaDB project is pleased to announce the immediate availability of the MariaDB Java Client 1.1.5. This is a Stable (GA) release. See the Release Notes and Changelog for detailed information on this release and the About the MariaDB Java Client page in the MariaDB Knowledge Base for general information about the client.

Download MariaDB Java Client 1.1.5

Release Notes …

Percona is glad to announce the release of Percona XtraDB Cluster 5.5.33-23.7.6 on September 18, 2013. Binaries are available from the downloads area or from our software repositories.

New Features:

• Default State Snapshot Transfer method, defined in wsrep_sst_method variable has been changed from mysqldump to …

You may have already seen the news: Oracle is launching an updated certification for MySQL Developers, based on MySQL Server 5.6.  This is exciting to me for several reasons that I want to share:

Only one exam

Earlier versions of the MySQL Developer certification required sitting for two separate exams.  One goal in redefining the certification process was to make it more accessible to candidates, and reducing the cost – in both time and money – developers need to invest in examinations.  This obviously presented a challenge to cover the same material – actually more, when you consider MySQL 5.6 features – in fewer questions, but we feel we’ve done it.

Content from the experts

Content creation for this exam has drawn from many different volunteers from a wide range of MySQL teams including Training, …

TokuMX v1.2.1 introduces two simple new features to help you understand the performance characteristics of your database: lock diagnostics and index usage statistics. We’d like to take you through a few examples of what these features are and how to use them.

Lock Diagnostics

Since we introduced TokuMX, one of the most frequent complaints has been about “lock not granted” errors.  These arise when a long-running operation takes document-level locks, and other clients timeout while waiting to acquire the same locks.

This is a new problem in TokuMX that doesn’t exist in MongoDB, because MongoDB doesn’t have document-level locks.  It has a single lock per database, and if an operation takes a long time, it simply …

Sometimes MySQL just doesn't choose the most efficient way to execute a query. GROUP BY is a good example. A customer recently wanted to add a unique key over some columns of a large (~50GB) table, and they first had to find duplicates. In this case, no suitable index was available that would help with the query. That means "Using temporary". And of course MySQL's GROUP BY also sorts by default, which means "Using filesort".

The goal here is just to find duplicates, or more specifically to find the lowest primary key value out of some group of rows with identical values for a subset of columns in the table. I think there is a much more efficient way to solve this problem.

I proposed a temporary table with the primary key column and a hash of the concatenated columns to be used for the grouping. This ended up allowing the customer to finish in 10 minutes an operation that originally resulted in a 30GB …

Disclaimer
The views expressed on this blog are my own and do not necessarily reflect the views of Oracle.

Introduction
There are database usage patterns, where tables grow big at times and many rows are deleted from them later. InnoDB does never shrink a table space. In these cases we can end up with big data files, which contain a lot of unused pages. It is a waste of disk- and I/O- resources to back them up.

Users have manifold requested that MySQL Enterprise Backup does not back up unused InnoDB data pages. Some want smaller backups, some want less I/O, some want shrinked table spaces.

MySQL Enterprise Backup 3.9.0 can help with smaller backups. The effect on I/O is not that remarkable. InnoDB data files must be expanded to their original size when they are restored. Backup cannot accomplish a shrinkage of InnoDB table spaces.

In the following I will try to explain, how …

Early this year Oracle released  MySQL 5.6 – Best MySQL Release Ever. This release delivered not only quality, but also quantity in terms of number of features. See a comprehensive list here . The blogs below also refer to the massive changes introduced in 5.6
http://www.mysqlperformanceblog.com/2013/01/27/mysql-5-6-improvements-in-the-nutshell/
http://www.flamingspork.com/blog/2013/03/05/mysql-code-size/

It is no mean task to deliver so many features with high quality that too for a feature rich product like MySQL. This was made …

Reblogged this on Sutoprise Avenue, A SutoCom Source.

Here’s a look at using MySQL Enterprise Backup in a specific example:

Consider a Backup Policy – Full Backup of the environment. – Complemental Incremental backups & online BinLogs. And the Restore: – Logical Restore. – Online, Zero impact. – Partial, single database, group of tables. The Backup A working environment, with 4 databases, of which 2 will require restoration. Full backup with MySQL Enterprise Backup:

mysqlbackup --user=root --socket=/tmp/mysql.sock \
  --backup-dir=/home/mysql/voju5/backup/ \
  --with-timestamp backup

Test preparation Create 4 different databases, where the structure & content is the same.

create database v5_1; use v5_1; create table `voju5` (
  `ID` int(7) NOT NULL AUTO_INCREMENT,
  `Name` char(20) NOT NULL DEFAULT '‘,
   PRIMARY KEY (`ID`) ) ENGINE=InnoDB;
create database v5_2; use v5_2; create table `voju5` (..);
create database v5_3; use v5_3; create table …