Features:
* Added an option to define a ‘color code’ for a connection. The color will be used as background color in the Object Browser.
* A Query Builder session can now be saved and resumed.
* In Query Builder a table alias can be defined for any table by double-clicking the title bar of the table symbol.
* In RESULT tab results can now be retrieved page-wise. This is ON as default with this build with a defined LIMIT of 1000 rows. For a specific query user can change and for this specific query the setting is persistent across sessions. Also read ‘miscellaneous’ paragraph below.
* Added a context menu to Query Builder canvas.

Bug Fixes:
* Deleting a user would leave non-global privileges orphaned in the ‘mysql’ database. Now we use DELETE USER syntax if server supports.
* Also using EDIT USER dialogue to change host or user specifier for a user would not move non-global privileges. We have split the old ALTER USER dialogue into two: a EDIT USER and RENAME USER dialogue. The latter will use RENAME USER syntax if server supports.
* On Wine Data Sync could generate a malformed XML-string what would case Data Sync to abort.
* Fixed an issue where SSH-tunneling failed with public/private key authentication. Technically the fix is in the PLINK binary shipped with SQLyog.
* SJA failed to send notification mails if Yahoo SMTP servers were used. Note that the fix disables encryption option with Yahoo SMTP servers – but it won’t work anyway due to a non-standard SMTP implementation server-side.
* When importing data from a Universe ODBC-source string data could be truncated.
* The fix in 8.22 for the issue that horizontal scrollbar in GRID would sometime not appear was not complete. It could still happen.
* SQLyog will now trim trailing whitespaces in Connection Manager and Create object dialogs to avoid MySQL Errors..
* Opening a file from ‘recent files’ list could crash SQLyog if a Query Builder or Schema Designer tab was selected and the file specified was not a valid XML file for that tab. This bug was introduced in beta 1.
* When calling a Stored Procedure with more than one SELECT statement from ‘Notifications Services’ only one result set was sent by mail.
* The sja.log file had no line-breaks between what was recorded for two jobs.
* On multi-monitor system resizable dialogues could open on the wrong monitor. New implementation is like this: on multi-monitor systems main program dialogue and ‘first child dialogue’ (example: ALTER TABLE) will open where they were closed (if possible), second and higher child dialogues (example: table advanced properties) will always open on top of its ‘parent’ dialogue. Non-resizable dialogues (such as confirmation boxes) will always open on top of their ‘parent’.
* With multiple SSH-tunnelled connections open stopping and re-executing queries in multiple connections in a fast manner could crash SQLyog.
* If more than one comment occurred before a SELECT statement in the editor, the statement was not identified as a SELECT statement by the Query Profiler and the Query Profiler TAB would not display.
* We did not validate client-side if user checked atoincrement option for a bit column with Create/Alter table dialog.
* If an error occurred while renaming a trigger then trigger was lost as SQLyog was not recreating it back.
* Small GUI fixes.

Miscellaneous:
* The default LIMIT setting for DATA tab has been removed. The setting is not required since we introduced table-level persistence for number of rows displayed. The default for new tables that have not been opened before is 50 – but when user changes the value and next ‘refresh’es SQLyog will save the LIMIT for that particular table persistently across sessions. This in combination with page-wise display in RESULT tab results in a more uniform User Interface for DATA and RESULT tabs.

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

Features:
* Added a context menu to Query Builder canvas.

Bug Fixes:
* Opening a file from ‘recent files’ list could crash SQLyog if a Query Builder or Schema Designer tab was selected and the file specified was not a valid XML file for that tab. This bug was introduced in beta 1.
* When calling a Stored Procedure with more than one SELECT statement from ‘Notifications Services’ only one result set was sent by mail.
* The sja.log file had no line-breaks between what was recorded for two jobs.
* On multi-monitor system resizable dialogues could open on the wrong monitor. New implementation is like this: on multi-monitor systems main program dialogue and ‘first child dialogue’ (example: ALTER TABLE) will open where they were closed (if possible), second and higher child dialogues (example: table advanced properties) will always open on top of its ‘parent’ dialogue. Non-resizable dialogues (such as confirmation boxes) will always open on top of their ‘parent’.
* GUI fixes – mostly related to new features added in beta1.

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

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 used in every case would be that if glibc 2.5 or higher is available on the system you should use the 2.5-based build.  Or simply use the one based on 2.5 if it installs and starts on your system. Upgrading users that are in doubt can continue with 2.3.4-based builds if they have no stability issues.

Bug Fixes:
* When MONyog encountered an SSH error while trying to read a file using SFTP  it could crash. This has been fixed.
* Redundant “Server Restarted” alerts concerning monitored Linux systems could be sent by MONyog. Now MONyog will notify users only once when a system is restarted, and alert will be sent as soon as MONyog detects it.
* When restarting MONyog an error message could be written to the log indicating that an ALTER TABLE SQLite query failed to execute. Technically it was an issue with a Schema version table in the MONyog database.

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

Features:
* Added an option to define a ‘color code’ for a connection.  The color will be used as background color in the Object Browser.
* A Query Builder session can now be saved and resumed.
* In Query Builder a table alias can be defined for any table by double-clicking the title bar of the table symbol.
* In RESULT tab results can now be retrieved page-wise. This is ON as default with this build with a defined LIMIT of 1000 rows.  For a specific query user can change and for this specific query the setting is persistent across sessions. Also read ‘miscellaneous’ paragraph below.

Bug Fixes:
* Deleting a user would leave non-global privileges orphaned in the ‘mysql’ database.  Now we use DELETE USER syntax if server supports.
* Also using EDIT USER dialogue to change host or user specifier for a user would not move non-global privileges.  We have split the old ALTER USER dialogue into two:  a EDIT USER and RENAME USER dialogue. The latter will use RENAME USER syntax if server supports.
* On Wine Data Sync could generate a malformed XML-string what would case Data Sync to abort.
* Fixed an issue where SSH-tunneling failed with public/private key authentication. Technically the fix is in the PLINK binary shipped with SQLyog.
* SJA failed to send notification mails if Yahoo SMTP servers were used. Note that the fix disables encryption option with Yahoo SMTP servers – but it won’t work anyway due to a non-standard SMTP implementation server-side.
* When importing data from a Universe ODBC-source string data could be truncated.
* The fix in 8.22 for the issue that horizontal scrollbar in GRID would sometime not appear was not complete. It could still happen.
* SQLyog will now trim trailing whitespaces in Connection Manager and Create object dialogs to avoid MySQL Errors.
* Small GUI fixes.

Miscellaneous:
* The default LIMIT setting for DATA tab has been removed.  The setting is not required since we introduced table-level persistence for number of rows displayed.  The default for new tables that have not been opened before is 50 – but when user changes the value and next ‘refresh’es SQLyog will save the LIMIT for that particular table persistently across sessions.   This in combination with page-wise display in RESULT tab results in a more uniform User Interface for DATA and RESULT tabs.

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

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

In our Blog (http://www.webyog.com/blog) we have an option to set a ‘mysql’ category for a post.  What posts appear marked with that category get syndicated. Until now nothing more and nothing less. This we manage very strictly. Only principal discussions related to MySQL and release announcements for major new releases (not betas, not small bugfix releases) get into the ‘mysql’ category.

But now somehow a Forums post got syndicated too.   Whether this is a deliberate action by somebody or some kind of systems error, I am not able to tell.  If such may happen due to some systems error or if anybody can syndicate anything there is a chance of copyright violation.

However the primary reason for this post is that I want to make it clear that we do not intend to spam planet.mysql with feeds from every post in our Forums! And we are not able to understand what happened this time.

Features:
* Added a monitor for InnoDB deadlocks (as exposed by SHOW ENGINE INNODB STATUS -statement).

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

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 delicate information (customer data, payroll data etc.).  We have completely rewritten the MONyog authentication system.  It is now possible to create multiple user profiles and give access for a specific user to a subset of servers available only.  Additionally specific ‘admin’ functionalities (access to edit server settings, to KILL queries and to execute FLUSH STATUS) can be disabled for a user.

As MONyog is no longer just a tool that organizes what the server exposes on SHOW statements – but rather a ‘bundle’ of tools – we have realized that not all tools are useful to every MONyog customer. MONyog is no longer a “one-size-fits-all” application. MONyog caters to a very diverse range to customers. In some organizations MONyog may be used by a single person only, and in other organizations by dozens of people. Some users will not use the Query Analyzer at all (because they only run standard applications where they are not in control of schema and query design anyway). And so on.  The Ultimate edition is for those users in particular that have full control over their database and their applications and who need multiuser authentication.  The Enterprise edition provides the basic monitoring functionalities as well as the Query Analyzer – but not multi-user authentication.  The Professional edition is an entry-level version with the (original) basic monitoring functionalities. Refer to the comparison sheet for full details.

We thought it is now the right time to have multiple editions of MONyog. This also means that people can start with the lower edition and gradually move to a higher edition if the need arises. This will also reduce the overall complexity and total cost of ownership for several customers.

We have also migrated all existing MONyog customers to MONyog Ultimate and Ultimate upgrade prices are kept moderate.  So if you are already a MONyog customer your Total Cost of Ownership remains same while you continue to enjoy the powerful tools and features of Ultimate.

Release notes in traditional form can be viewed here.

Feel free to leave your feedback in the comments section.

Bug Fixes:
* ‘Test connection’ would succeed even if a non-existing database was specified in the database field. Connection would next fail.
* Database name (if any) would erase on clicking OK in error dialog in connection window.
* HTML exports could drop the first character of string output.
* With multimonitor setup and SQLyog on the right screen some rarely used dialogues would pop up on left screen.
* Copy database/table will now display ‘connecting to source/target server’ while connecting.  If establishing connection took more than a few seconds users could have the impression that nothing was happening.
* An extra RESULT tab could appear when executing a query.  This bug was introduced in 8.2. Professional and Enterprise editions were affected.
* In notification wizard sending mail would fail if there was no semicolon after the query and “include original query” option was checked.
* With more than 65 536 (2^16) rows displayed in GRID, the GRID scrollbar would expose strange behavior. We were using a scroll control using 16 bit integers internally.  New scroll control handles +4 billion rows.
* In Wine when displaying very wide tables and result sets (like 500+ columns) the column header could disappear. The underlying reason was that Wine failed to render a gradient as transparent but rendered it as opaque instead.
* Horizontal scrollbar in GRID would sometime not appear when executing a query returning a large number of columns if not scrollbar was required for previous query.
* With larger than ‘normal’ DPI setting the BLOB Viewer header would not display properly.
* ‘Export as SQL-dump’ dialogue was redesigned to allow for longer files paths.

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

However note that the full-featured “MONyog” (as you know it) was was renamed to “MONyog Ultimate”.  Full details will be available with the upcoming GA release. A new licensing scheme is planned from 3.7 GA. But note: this will not affect existing users.

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