Hi,

We are delighted to unveil MONyog 4.0 — a major new release. Listed below are overviews of some of the major features.

Tracking changes to your MySQL configuration

Maintaining server configuration and tracking changes to it plays a vital role in the maintenance of MySQL servers. DBAs may be responsible for hundreds of servers and keeping an eye on the configuration settings for all of them could be difficult to say the least. With MONyog 4.0 now you can compare global MySQL configuration of multiple servers side-by-side, with all changes highlighted so that differences are visually discernible at a glance. Wondering why server A isn’t performing as well as server B when they share the exact same load? The answer could lie in the configuration files!

What’s more is that MONyog now lets you track changes to the global configuration of your MySQL server no matter if the configuration parameters were …

Important note: Please note that if you have installed a MONyog 4.0 (beta) release you cannot install this one unless first completely removing the 4.0 installation including the complete MONyog data folder.

Changes (as compared to 3.77) include:

Bug Fixes:
* Monitors/Advisors on InnoDB Deadlocks were truncating the output message and hence in some cases, users were unable to view both queries involved in the deadlock. This has been changed such that the first 2048 characters of both queries are displayed.
* On Windows 7 systems changes to MONyog’s .INI file from external programs had no effect upon restart (as Windows reverted the changes). Now throughout MONyog’s lifetime the .INI file will be locked so that a user may only edit the file manually when MONyog is not running (but users can use the MONyog interface to change any setting while MONyog is running). Any …

Changes (as compared to 3.73) include the bug fixes:

* Log analysis could use high CPU if the option to replace literals with a placeholder was not selected and the literal string ‘ “‘ (space + doublequote) occured in the log file.
* CSV-export from Query Analyzer only exported 200 rows (the same number as displayed in the browser view). Now CSV-export will export all rows. Also the UI makes it now clear that the browser displays the 200 uppermost rows according to current sort criteria.
* An error message regarding an integer overflow could occur in Monitor/Advisors page for some values. The SQLite datatype used could be too short for some specific data.
* Login to MONyog could fail if MONyog was running behind a proxy.

Downloads: http://webyog.com/en/downloads.php
…

At work we have been looking for tools to monitor MySQL and at the same time provide as much diagnosis information as possible upfront when an alarm is triggered. After looking around at different options, I decided to test MONyog from Webyog, the makers of the better known SQLyog. Before we go on, the customary disclaimer: This review reflects my own opinion and in no way represents any decision that my current employer may or may not make in regards of this product.
First ImpressionYou know what they say about the first impression, and in this where MONyog started with the right foot. Since it is an agent-less system, it only requires to install the RPM or untar the tarball in the server where you're going to run the monitor and launch the daemon to get started. How much faster or simpler can it be? But in order to start monitoring a server you need to do some …

Changes (as compared to 3.72) include:

* If SHOW ENGINE INNODB STATUS returned an error that was not privilege-related, MONyog reported MySQL as non-available.  That could happen for instance if MySQL was started with –skip-innodb option. This bug was introduced in 3.71 with the support for InnoDB deadlock detection.
* A bug in the MONyog startup script could on Linux have the result that MONyog was still reported as running if it had been killed or had crashed.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Changes (as compared to 3.71) include:

Features:
* The number of builds for Linux has been increased to the double number of what it was before.  In addition to the builds based on glibc version 2.3 we now distribute builds based on glibc 2.5.  Also we add builds for use with even older glibc 2.3 based Linux that what we had before. There are now builds based on both glibc-2.3.2  and 2.3.4 (the one based on 2.3.4 is the one we had before). We had a few  reports of random crashes (typically occurring up to a few times per week) occurring on recent 64 bit CentOS servers and in one case also a RHEL5.  The glibc 2.5-based build fixes this. Although we only had such reports on 64 bit Linux of  ‘Red Hat Family’ we also included 64 bit tar.gz for all Linux platforms and 32 bit RPM builds.  The general advice on which build (glibc 2.3-based versus 2.5-based) should be …

Changes (as compared to 3.7) include:

Features:
* Added a monitor for InnoDB deadlocks (as exposed by SHOW ENGINE INNODB STATUS -statement).
* In case of a program crash on Linux, MONyog will save a core dump like the Windows version already does.  The dump is saved in ../MONyog/bin folder.

Bug Fixes:
* EXPLAIN from Processlist page could fail with syntax error due to a missing SPACE character in the statement.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Dear MariaDB users,

MariaDB 5.1.42, a new branch of the MySQL database which includes all major open source storage engines, myriad bug fixes, and many community patches, has been released. We are very proud to have made our first final release, and we encourage you to test it out and use it on your systems.

For an overview of what’s new in MariaDB 5.1.42, please check out the release notes.

For information on installing MariaDB 5.1.42 on new servers or upgrading to MariaDB 5.1.42 from previous releases, please check out the installation guide.

MariaDB is available in source and binary form for a variety of platforms and is available from the …

MONyog MySQL Monitor 3.7  Has Been Released.

From MONyog 3.7 we have introduced 3 editions of the commercial version of MONyog. When we had first released MONyog 2 years back, it was already an almost complete tool for monitoring MySQL servers based on what the MySQL server exposes on SHOW statements.  Since then we have added features that are not basic server monitoring features in the strict sense but additional or supplementing features.  Most important the Query Analyzer was added around one year ago.

Multi-user authentication is a long standing request from customers belonging to large organizations – or just having the need for monitoring lots of MySQL servers. There may be multiple server administrators. There may be development/test servers that the developers of that organization should be able to monitor, but is may also be unwanted to give them access to see details from servers having …

Happy new year!

Just before Christmas the number of downloads of MONyog (from distinct email addresses) crossed 100,000. Here is the situation as of now:

This is of course a nice Christmas present for us to have. But more important: it reflects that today – as opposite to the situation just a few years ago – that even average MySQL users have understood that tuning the server configuration as well as the schemas and the queries used by applications is essential.

The default settings for the MySQL server are not appropriate for a heavy-loaded server and even the standard configuration files (or configuration ‘templates’) shipped with the server will not have the specific settings required for optimal configuration in most situations. And even the best server configuration won’t help much if databases and queries are poorly designed. We benefit from the growing understanding of this but also believe we have …