Getting data into Hadoop is not difficult, but it is complex if you want to load 'live' or semi-live data into your Hadoop cluster from your Oracle and MySQL databases. There are plenty of solutions available, from manually dumping and loading to the good and bad sides of using a tool like Sqoop. Neither are easy and both prone to the problems of lag between the moment you perform the dump and

Running MySQL in the cloud offers many benefits, including extremely fast provisioning and deployment, managed security, and (mostly) easy operations. But nothing comes for free, and as with all things on this wonderful planet, those benefits come with certain limitations. Until recently, one of the significant drawbacks of MySQL on Amazon RDS was limitation of […]

With Fabric's official GA release this week, I thought I would post a spin on how to setup a development environment loosely based on the Fabric Quick Start guide in the manual.

The notable change, is the use of MySQL Sandbox for bootstrapping each of the MySQL instances.

Step 1: Install the MySQL Utilities + Python Connector

In my case, I downloaded:

• mysql-utilities-1.4.3-osx10.7.dmg Mac OS X 10.7 (Architecture Independent), DMG Archive
• mysql-connector-python-1.2.2-osx10.7.dmg Mac OS X 10.7 (Architecture Independent), DMG Archive

The GUI install in both cases works as expected. Next, Next, …

MySQL has status variables “questions” and “queries” which are rather close but also a bit different, making it confusing for many people. The manual describing it might not be very easy to understand:

Queries
The number of statements executed by the server. This variable includes statements executed within stored programs, unlike the Questions variable. It does not count COM_PING or COM_STATISTICS commands.
 Questions
The number of statements executed by the server. This includes only statements sent to the server by clients and not statements executed within stored programs, unlike the Queries variable. This variable does not count COM_PING, COM_STATISTICS, COM_STMT_PREPARE, COM_STMT_CLOSE, or COM_STMT_RESET commands.

In a nutshell if you’re not using prepared statements the big difference between those is what …

Is it correct that 100% CPU here means 100% of 8 vCPU's? So I assume MEB uses 1 thread per CPU for pastoralization? Or is one item being compressed with multiple CPU's? This could maybe make a difference for databases with one huge table.

The post Puppet and MySQL: A How-To Guide appeared first on Pythian.

The post Life at Pythian as a MySQL DBA appeared first on Pythian.

First, I would like to invite you to my webinar, “Monitoring All (Yes, All!) MySQL Metrics with Percona Cloud Tools,” on Wednesday, June 25 at 10 a.m. Pacific Daylight Time, where I will talk on the
new features in Percona Cloud Tools, including monitoring capabilities.

In this post I’d like to show the cool and interesting things we’ve implemented in Percona Cloud Tools, including the recently released agent that Daniel also talks about here in this post.

Basically our agent allows users to collect ALL MySQL metrics plus important …

There is one new feature in MySQL 5.6 that didn’t get the attention it deserved (at least from me ) : “DATA DIRECTORY” for InnoDB tables.

This is implemented since MySQL 5.6.6 and can be used only at the creation of the table. It’s not possible to change the DATA DIRECTORY with an ALTER for a normal table (but it’s in some case with partitioned ones as you will see below). If you do so, the option will be just ignored:

mysql> CREATE TABLE `sales_figures` (
    ->   `region_id` int(11) DEFAULT NULL,
    ->   `sales_date` date DEFAULT NULL,
    ->   `amount` int(11) DEFAULT NULL
    -> ) ENGINE=InnoDB DEFAULT CHARSET=latin1
    -> DATA DIRECTORY = '/tb1/';
Query OK, 0 rows affected (0.11 sec)
mysql> alter table sales_figures engine=innodb data directory='/tb2/';
Query OK, 0 rows affected, 1 warning (0.21 sec)
Records: 0  Duplicates: 0  Warnings: 1
mysql> show warnings; …

We are pleased to announce another MySQL User Group meeting scheduled for June 5 in Madrid, Spain. Keith Hollman, the MySQL Principal Sales Consultant will be talking about MySQL & Oracle strategy and MySQL Cluster. A small demo of MySQL Cluster will be part of the presentation. 

Details about the event: Date: June 5, 2014 Time: 7:00 pm-8:30 pm Place: Edificio Telefonica, Gran via 28, Madrid, Entrada por C/ Valverde 2
We are looking forward to seeing you in Madrid!
See more information & registration.