UPDATE: Almost solved! See at the end.

A clean installation of a database server is one where everything goes according to the expectations. It used to be easy: you only had to do what the manual says, and, presto! you would see your database server installed and ready to use. If something went wrong, you got one or more error messages that informed you of what needs to be fixed.

Sometimes, rarely, it happened that you got also a warning message, telling you that while the installation was successful, you could improve it by fine tuning this and that. No big deal.

Gone are those times. A clean installation nowadays is a much harder exercise, if not impossible. Let’s give it a try using MySQL 5.7.7.



Attempt #1 using mysql_install_db
The first error you could do when using a new version of MySQL is assuming that basic operations are …

[…] PlanetMySQL Voting: Vote UP / Vote DOWN Full article:NDB 7.4 & SYS schema: When getting locks, detecting the guilty SQL & o.s.pid. […]

VividCortex is sponsoring and exhibiting at Velcoity EU in Amsterdam October 28 - 30th. Stop by our booth to get a free product demo and see how we can revolutionize your database monitoring.

Baron Schwartz will also be speaking on Probabilistically Sampling A Stream Of Events With A Sketch.

Click here for more details and registration.

VividCortex is sponsoring and exhibiting at Velcoity EU in Amsterdam October 28 - 30th. Stop by our booth to get a free product demo and see how we can revolutionize your database monitoring.

Baron Schwartz will also be speaking on Probabilistically Sampling A Stream Of Events With A Sketch.

Click here for more details and registration.

Have you been considering VividCortex but putting off a free trial? Are you a user who wants to get the most of the product? Are you a huge fan who simply wants to hear the brains behind the product give you the inside scoop?

Join us on Tuesday, September 15 at 2 p.m. ET (6 p.m. GMT), for a live walk through of VividCortex on production systems from our CEO, Baron Schwartz. He will use the product to demonstrate the following:

• Using our top queries feature to quickly find queries that need attention
• Finding and diagnosing stalls with Adaptive Fault Detection
• Comparing queries before and after code deployments, to find workload changes
• Understanding how your databases and queries are driving CPU, I/O and other operating system work

Have you been considering VividCortex but putting off a free trial? Are you a user who wants to get the most of the product? Are you a huge fan who simply wants to hear the brains behind the product give you the inside scoop?

Join us on Tuesday, September 15 at 2 p.m. ET (6 p.m. GMT), for a live walk through of VividCortex on production systems from our CEO, Baron Schwartz. He will use the product to demonstrate the following:

• Using our top queries feature to quickly find queries that need attention
• Finding and diagnosing stalls with Adaptive Fault Detection
• Comparing queries before and after code deployments, to find workload changes
• Understanding how your databases and queries are driving CPU, I/O and other operating system work
…

The MySQL manual says:
"mysql Logging
On Unix, the mysql client logs statements executed interactively to a history file. By default, this file is named .mysql_history in your home directory. To specify a different file, set the value of the MYSQL_HISTFILE environment variable."
The trouble with that is: it doesn't tell you what you don't need to know. So I'll tell you.

Heritage

The history-file concept that MySQL and MariaDB are following is indeed "on Unix" and specifically is like the GNU History Library. There is a dependence on external libraries, Readline or …

As we are collecting an ever increasing amount of data and analyzing it, data storage products with alternate file structures have become popular, such as LSMs (log structured merge files) which is implemented in Cassandra and Hbase, as well as fractal indexes found in TokuDB/MX, which is an alternate file structure plugin for mysql and [...]

Someone asked me the other day about some of the more obscure metrics available from a database server’s internals, and wanted access to those. As it happens, we have a feature that lets you see every metric on your systems—yes, every metric, which is typically many thousands, sometimes millions.

First, though, let’s look at what this user was examining. We ship VividCortex with a prebuilt set of templates for graphing popular systems, to reduce time-to-insight as much as possible. (No more Google searching for good graph templates and fighting to get them installed!) They look like this:

There’s quite a variety of templates, dozens for some kinds of servers that have a lot of metrics to expose. But these prebuilt templates aren’t the best solution in some cases. For example, some of the charts will have scores of metrics, and it can be hard to see them sometimes, especially when some are large and some are small:

Someone asked me the other day about some of the more obscure metrics available from a database server’s internals, and wanted access to those. As it happens, we have a feature that lets you see every metric on your systems—yes, every metric, which is typically many thousands, sometimes millions.

First, though, let’s look at what this user was examining. We ship VividCortex with a prebuilt set of templates for graphing popular systems, to reduce time-to-insight as much as possible. (No more Google searching for good graph templates and fighting to get them installed!) They look like this:

There’s quite a variety of templates, dozens for some kinds of servers that have a lot of metrics to expose. But these prebuilt templates aren’t the best solution in some cases. For example, some of the charts will have scores of metrics, and it can be hard to see them sometimes, especially when some are large and some are small: