The MySQL developer tools team is pleased to announce 6.1 Beta 2 – the start of the public beta testing phase of MySQL Workbench 6.1

MySQL Workbench 6.1 is the upcoming major update for the official MySQL graphical development tool.
Introducing over 30 new features, this version has many significant enhancement focusing on real-time performance assessment and analysis from the SQL statement level to server internals and file IO. You’ll see this in additions to the SQL Editor as well as new dashboard visualization and reporting that takes advantage of MySQL Server 5.6 and 5.7 Performance Schema, and enhancements to the MySQL Explain Plans.

Additionally Workbench 6.1 this leveraging work from various teammates in MySQL Engineering in introducing a schema called “SYS” that provides simplified views on Performance Schema, Information Schema, and other areas.
Special thanks to the server optimizer …

“Many tools now exist to run database software without installing software. From vagrant boxes, to one click cloud install, to a cloud service that doesn’t require any installation, developer ease of use has always been a path to storage platform success.”–Brian Bulkowski.

The fifth interview in the “Big Data: three questions to “ series of interviews, is with Brian Bulkowski, Aerospike co-founder and CTO.

RVZ

Q1. What is your current product offering?

Brian Bulkowski: Aerospike is the first in-memory NoSQL database optimized for flash or solid state drives (SSDs).
In-memory for speed and NoSQL for scale. Our approach to memory is unique – we have built our own file system to access …

Under Parallel Network Query, servers are numbered according to the table join
order of query (forming server pipeline) and each server processes its own
tables.  Query result is generated by concatenating processed tables of each
server along the server pipeline.

Parallel Network Query may also be used to speed up slow server by distributing
tables of the query to multiple servers for processing which effectively
aggregates server resources (such as disk I/O bandwidth and CPU/cores).

See Technology and Benchmarks page.

Will be giving a lightning talk at Percona Live 2014 – santa clara :)

In the world of replication, The Binlog is every ones favorite. 

But what about the Relay log, Don't you feel it can do more ?

Yes, It can. How about, if it can serve the purpose of the GTID 

feature without GTID.

https://www.percona.com/live/mysql-conference-2014/sessions/relay-log-unsung-hero

#MySQL  ( alternative to GTID )  #gtid

I’m very excited to share that Ubuntu Bug #1256931 has just been updated. MySQL 5.6 will be installable from the universe archive in trusty, with 5.5 remaining in the main archive.

Trusty Tahr (14.04) is a long term release (LTS) for Ubuntu, with support until 2019. It’s due out in April.

MySQL Utilities is one of those gems that every MySQL user should know about. They simplify and help automate a wide range of tasks and activities that everyone from casual users to seasoned DBAs may need to carry out on their MySQL setup from time to time, all the way from cloning users, copying databases […]

In addition to my recent post, I just had to go into using the –use-tts for specific tables and selective backup sets.

As all my schemas were employeesn, I thought it would be a good idea to run:

mysqlbackup -uroot --socket=/tmp/mysql.sock --backup-dir=/home/mysql/MEB/restore \
--with-timestamp --use-tts --include=employees* backup

as I want all the tables. If I only wanted a specific table, say ‘salaries’ I could have done:

mysqlbackup -uroot --socket=/tmp/mysql.sock --backup-dir=/home/mysql/MEB/restore \
--with-timestamp --use-tts --include=employees*\.*salaries backup

and backup just the ‘salaries’ tables but from all the employeesn databases.

then.. be a mean little dba:

drop database employees;
drop database employees10;
drop database employees11;
..
..
drop database employees2;
drop database employees20;
drop database …

In addition to my recent post, I just had to go into using the –use-tts for specific tables and selective backup sets.

As all my schemas were employeesn, I thought it would be a good idea to run:

mysqlbackup -uroot --socket=/tmp/mysql.sock --backup-dir=/home/mysql/MEB/restore \
--with-timestamp --use-tts --include=employees* backup

as I want all the tables. If I only wanted a specific table, say ‘salaries’ I could have done:

mysqlbackup -uroot --socket=/tmp/mysql.sock --backup-dir=/home/mysql/MEB/restore \
--with-timestamp --use-tts --include=employees*\.*salaries backup

and backup just the ‘salaries’ tables but from all the employeesn databases.

then.. be a mean little dba:

drop database employees;
drop database employees10;
drop database employees11;
..
..
drop database employees2;
drop database employees20;
drop database …

The MySQL developer tools team at Oracle is excited to announce the availability of MySQL Workbench 6.0.9.

MySQL Workbench 6.0 is the GUI Development and Administration tool for MySQL.

Changes in MySQL Workbench 6.0.9 (2014-02-05)

This section documents all changes and bug fixes applied to MySQL Workbench since the release of 6.0.8.

Functionality Added or Changed

•  The restore operation can restore to a different schema.

Bugs Fixed

•  MySQL Workbench now builds on Debian 7.0-unstable.
•  Ubuntu 13.10 is now supported.
•  Fedora 20 is now supported
•  On Linux, the Cancel button was written as “Cance” on some systems, depending on the GTK theme used on the system.
•  Sometimes, when exporting an EER diagram to SQL, the generated SQL code did not include “DROP …

In this post I go into some performance metrics and time spent on using MySQL Enterprise Backup instead of mysqldump, and seeing how far I could go with some parallel configuration.

Setup:

It’s on an old laptop:

–Ubuntu 12.04 LTS, 32bit Intel Pentium M 1.86Ghz, 2Gb –Source disk:  internal 80Gb ATA ST9808211A –Destination:  external 1Tb SAMSUNG HD103SI –MySQL Enterprise Edition 5.6.15 –MySQL Enterprise Backup 3.9.0 –Employees sample database duplicated via MySQL Utilities 1.3.6 (on Win7 PC) to generate a ~5Gb MySQL Server. And to simulate data size, I used the MySQL Utilities:

mysqldbcopy --source=root:pass@host:3356 --destination=root:pass@host:3356 employees:employees1 \
employees:employees2 employees:employees3 employees:employees4 ... employees:employees18 \
employees:employees19 employees:employees20

…