We are very pleased to announce the release of MONyog 2.5 Beta 1. This is a major upgrade from the previous releases.

MySQL currently lacks advanced query profiling tools like SQL Server’s Query Profiler. While the current breed of MySQL monitoring tools provide monitoring and advisory information on various system metrics, they don’t help in pinpointing the problematic queries. No amount of hardware upgrades or tuning of mysql.cnf / mysql.ini parameters can match the performance gains that can be achieved when problematic queries and identified, rewritten and/or appropriate indexes are created.

MONyog 2.5 helps in identifying problem SQL by

1) Analyzing the general query log
2) Analyzing the slow query log
3) If the above mentioned logs are unavailable then MONyog query sniffer can capture the results of SHOW PROCESSLIST at user-defined …

Bug fixes:

* The new version 3 release of Mozilla Firefox (now in RC) had a flickering issue with MONyog and the login page did not load correctly in that browser version.

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

Bug fixes:

*  OS monitoring issue in Fedora Core 6 Zod was fixed

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

Performance improvement:

* Earlier MONyog was semaphore intensive. That could result in reaching the ‘limit of semaphores that can be created by the kernel’ in some systems. MONyog 2.04 will use less semaphores. Another symptom was that a large number of small and zero-size files could be left behind (in system TEMP folder on Windows and in MONyog/bin folder on Linux). This is also solved with this.

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

Bug fixes:

* Structure Sync could miss the concluding quote around column comments. This bug was introduced in 6.5.
* Migration from SQL Server could fail with empty tables.
* Migration (UPDATE and DELETE) triggers could fail with specific schemas on source (afffected were small tables with short column types only - like integers and very short string types). This bug was introduced early in 6.x with the full Unicode support added here.
* Migration could generate non-matching columns-count with specific schemas. This was also introduced early in 6.x
* Message about ?Successful rows? could display twice in Migration (sja.log). Note: This was a cosmetical issue with the message only. Rows were only migrated once!

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

Bug fixes:
* In some situations where SSH connections failed (including if MONyog was not able to connect to MySQL, wrong SSH authentication details for tunnelling etc.), sockets were not being closed and it could result in that many sockets were kept in CLOSE_WAIT state. (note: connections to MySQL not using SSH were not affected!)

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

MySQL Lifecycle Policy Calendar

The official MySQL Lifecycle Policy calendar terminates the end of the Active Support Lifecycle for MySQL 4.1 at the end of this year. The product is then entering the Extended Support Lifecycle. Please click on the image and read "What is the difference between Active Lifecycle and Extended Lifecycle support?" to understand the implications of this.

As a service to the busy, here are SuSE 10.0 RPMs of 5.0.19 a/o 2005-12-27 — use the spec-file to roll your own from the sources. This is a QND build, no warranty given, no responsibility taken.

As a service to the busy, here are SuSE 9.3 RPMs of 5.0.13 a/o 2005-09-09 — use the spec-file to roll your own from the sources. This is a QND build, no warranty given, no responsibility taken.

As a service to the busy, here are SuSE 9.3 RPMs of 5.0.12 a/o 2005-08-30 — use the spec-file to roll your own from the sources. This is a QND build, no warranty given, no responsibility taken.