I will be talking about Big Data with MySQL and Hadoop at
title="MySQL Connect 2013" href="http://www.oracle.com/mysqlconnect/index.html" target="_blank">MySQL Connect 2013 (Sept. 21-22) in San Francisco as well as at
href="http://www.percona.com/news-and-events/percona-university/washington-dc" target="_blank">Percona University at Washington, DC (September 12, 2013). Apache Hadoop is a very popular Big Data solution and we can nowadays easily integrate it with MySQL. I will start with a brief introduction of
Good news everyone! I recently presented a webinar:
href="http://www.percona.com/webinars/percona-server-56-enterprise-grade-mysql" target="_blank">Percona Server 5.6: Enterprise Grade MySQL. It was also recorded so you can watch along or view the slide deck. As with all my talks, I am not simply reading the slides so it really is worth to listen to the audio rather than just glance through the slide deck.
There were a number of great questions asked which I’ll answer below:
It can be hard for software engineers to understand the following principle, however it is very important for improving performance and obtaining immediate scalability options. The principle is “Do Less Work”. That is, run less SQL statements.
With the release of MySQL Utilities 1.3.4, the standalone (not bundled with the MySQL WorkBench GUI) package is now Generally Available and fully supported. This post will focus on a very important change (the ability to run as a daemon rather than in a terminal) to the mysqlfailover utility which allows you to build a light-weight HA database solution using MySQL Replication.
Senior MySQL DBA John Cesario of Go Daddy spoke at Percona Live in April and shared his views on
href="http://www.percona.com/training" target="_blank">Percona MySQL Training. Here’s what he had to say:
As part of uncovering a new security improvement in MySQL 5.6 with the default installation being secured with a unique root MySQL password, the MySQL provided rpm’s installed the MySQL configuration file in /usr.
I feel this maybe a bug, however this is just as an explanation for others to comment on.
The following steps reproduces this.
What if the data you retrieved from the database did not match the data the application claimed to had successfully stored? How comfortable would your organization feel about your skills and the products that are being used to store important information if data integrity was not guaranteed?
MySQL employs a terrible default technique known as silent truncation where the product determines that it knows about your data better than you. Never has the saying “do not assume” because it makes an “ass” out of “u” and “me” been more applicable.
The -N or –skip-column-names is a convenient option with the mysql client to skip the header line of output.
However I found when viewing the output via the terminal, some interesting and unexplained output.