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.

This week we talk with former co-host Sarah Novotny about Data at OSCon. Ear Candy is about SQL Courses, and At the Movies is a two and a half hour tutorial about MySQL Scaling Strategies for Developers.

Events
DB Hangops - every other Wednesay at noon Pacific time

Upcoming MySQL events

OSCon 2014 will be held at the Oregon Convention Center in Portland, Oregon from Sunday July 20th through Thursday July 24th.

read more

Section 2: "COMPILE MARIADB IN ECLIPSE"

2.1 Download and prepare sources folder/>

We will need a directory to use as our playground, if you create the user yoda in Section 1:

$ su - yoda
$ mkdir -p ~/playground

Download latest MariaDB 10 sources tar.gz and copy the archive into the above directory, you can latest sources from:

read more

So, the good thing about MEM 3.0 is that it’s agentless, i.e. you don’t need an agent to use Query Analyzer data and see when performance is at it’s worst and dive into the offending SQL’s and explain plans to see what’s happening.

That’s great, however, sometimes it’s not always an easy road to migrate to 5.6 and even if you’re doing so, there’s nearly always a time when you want to continue viewing things in 5.5.x and compare performance between the 2.

The thing is, that in order to see the Explain Plans we need 5.6.14 or upwards (and setting “UPDATE performance_schema.setup_consumers SET enabled = ‘YES’ WHERE name = ‘events_statements_history_long’;” ).

So, here’s how to do it:

– Use the MEM 2.3 Agent & proxy.

It’s really that simple. How simple? (Ref.Man: Using the …