Changes (as compared to 4.0) include:

Bug Fixes:
* Implemented code that makes OpenSSL (what is used by our SSH-library) explicitly thread-safe and thus fixing an issue where specific cryptographic function calls under very heavy load could cause a crash.
* Fixed a SQLite corruption issue that on Windows could cause failure to stop the MONyog service. The issue did not mean that MONyog as such stopped working as long as it was running.
* If both value for ‘user’ and ‘host’ were filtered in processlist-based sniffer the interface would display NULL for both.

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

Comments(0)

We are pleased to announce the release of SQLyog – MySQL GUI 8.6 GA. This release adds functionalities requested by users for some time, and fixes a number of bugs. Most important enhancements:

User management has been updated with a brand-new interface, has been completely rewritten and also now fully communicates with the MySQL server the recommended way using GRANT and REVOKE syntax. We believe that with this release we have provided the best available ever GUI for MySQL User Management.

For users that prefer to work in a spreadsheet-like interface when filtering and sorting data the options to do this have been enhanced: There is now a ‘custom filter’ option to be used when filtering on a value that does not exist in the result set displayed – or even is not stored in the table at all. Additionally you may now define the substring to be filtered on in more flexible ways than before.

In the editor we added “parenthesis’es matching”. With complex statements (JOINs on derived tables, SUBQUERIES, statements with nested functions and similar) this will make it much easier to identify the structure of the statement. Just position the cursor after a parenthesis and the actual parenthesis and its match will highlight.

We have improved performance by optimizing code in code segments executed most frequently. Additionally we have deployed more debugging and performance measuring tools. This includes – but is not restricted to – moving our build environment to latest Visual Studio environment (2010 edition).

Note that with this release we have stopped supporting Windows 2000. It has for some time been increasingly difficult to continue this support. It is actually quite hard to find a recent system where Windows 2000 will run without errors and we have over the few last years spent quite a lot of effort fixing issues occurring only on this variant of Windows. We believe that the effort is better used ensuring optimal performance on recent and still supported Windows variants – not at least Windows 7, what fastly is taking the position of the dominating Windows variant. The move to Visual Studio 2010 shall be seen in this context. But of course XP, Vista (and the same generations of Windows server variants: 2003 and 2008) are still supported as well as Wine.

Links to Beta/RC release blogs with detailed information.
* http://www.webyog.com/blog/2010/08/17/sqlyog-mysql-gui-8-6-rc3-released/
* http://www.webyog.com/blog/2010/08/06/sqlyog-mysql-gui-8-6-rc2-released/
* http://www.webyog.com/blog/2010/08/06/sqlyog-mysql-gui-8-6-rc-released/
* http://www.webyog.com/blog/2010/08/03/sqlyog-mysql-gui-8-6-beta3-released/
* http://www.webyog.com/blog/2010/07/22/sqlyog-mysql-gui-8-6-beta2-released/
* http://www.webyog.com/blog/2010/07/20/sqlyog-mysql-gui-8-6-beta1-released/

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

Comments(3)

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 specified in my.ini/my.cnf, are server defaults or if somebody with SUPER privilege has executed a SET GLOBAL statement.

Improved customization framework

Many MONyog users have long since complained that the customization feature was complex and hard to use: One had to be well-versed in object-oriented JavaScript concepts to even make a minor change. Moreover, unless you manually backed up your customizations, you’d loose all of them if you decided to upgrade! That was motivation enough for us to redesign the entire framework.

With MONyog 4.0 knowledge of writing basic JavaScript functions is more than sufficient to customize any Monitor/Advisor or roll out your very own set. A simple form-based interface with verbose instructions makes it very easy to define a new Monitor/Advisor.

We understand that not every user will make use of the 220+ Monitors/Advisors that we ship with MONyog. So why waste all the computing power? You can now disable a subset of the Monitors/Advisors and keep only the ones you use. If you change your mind later, you can always re-enable them again.

MONyog 4.0 provides a unique customization interface. Now you won’t have to worry about loosing your changes, making mistakes (you can always revert to the original!), or feel scared to experiment.

Improved stability and lots of minor features and bug fixes

As always, this release too contains a lot of bug fixes. MONyog has undergone severe stress testing and is monitoring 200 without issues in our test environment now. From this release we have reduced the number of Linux binaries. In version 3.72 we introduced packages specific to glibc versions. It was necessary at that time to ensure stability on both older Linux distros (RHEL3-generation) as well as the most recent distros using glibc version 2.5. But we never liked it ourselves. It could confuse users – and sometimes did. Since then we have been researching and testing different packaging concepts so that a single binary will do the job on all distros.  This release contains a single 32 and a single 64 binary – each with the option of a .tar.gz archive and a RPM installer.

MONyog customers can download the latest installers from Webyog’s Customer Portal.

We are very excited about this release, and hope that you will like it. We would love to hear from you.

Regards,

Team MONyog

Comments(4)

Changes (as compared to 8.6 RC2 ) include:

Miscellaneous:
* With this build we have changed our build environment from Visual Studio 2003 to 2010.
* Windows 2000 is no longer supported.

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

Comments(0)

Important note: Please note that a 4.0 release cannot be downgraded to 3.x as the database schemas are incompatible and the installer will not handle downgrades – only upgrades. However you can install this 4.0 beta 3 on top of any previous release.

Changes (as compared to beta2) include:

Features:
* All fixes and features already released in 3.x have been ported to this build.  This includes the handling of SQLite caches now requiring much less memory.  Also this build has been checked in depth with leak-finder tools on both Linux and Windows.  Refer 3.8 release notes for details.

Bug Fixes:
* Fixed some issues with specific counters including issues where ‘undefined’ or ‘NaN’ were returned incorrectly.
* Graphs in ‘all time’ and ‘delta’ timeframes for the counter ‘Cache Misses’ for as well InnoDB Cache, MyISAM key cache and Query cache groups were not displaying but threw the error “Invalid XML data” (these counters were added in beta 1).
* Previously accepted values for the “ChartValue” property in Dashboard charts were “Current” and “Latest”. This has caused confusion since both terms mean the same thing in this context, although technically “Current” refers to the current value of the metric and “Latest” to the “Delta” value. Moreover, the documentation mentions “Actual” and “Delta” as accepted values. To eliminate this confusion, the “ChartValue” property now accepts the values “Current” and “Delta” – “Current” referring to the current value of the metric, and “Delta” to the difference between the metric in the previous two collections.

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

Comments(0)

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 made to the file when MONyog is not running will be reflected by it once it is restarted.
* If MySQL Error Log monitoring was enabled for a particular server, the first two data collections for that server would cause large network traffic to occur if the MySQL error log was very large. This was because the entire log file was read in the first collection. Now only the last 1MB of the file is read.

Miscellaneous:
* All libraries have been upgraded to their latest versions. Although, from a user-perspective, the changes are minimal, this has alleviated several memory leaks and other performance issues.
* This release has been checked in depth with with the best leak-detection tools available for both Linux and Windows.  All discovered leaks have been fixed.
* The cache parameters for the SQLite library have been modified with this release to allow for registering more servers on the same system as before. Before MONyog’s memory usage used to grow continually with time as each open SQLite handle has an associated cache which could grow to any size, irrespective of system capacity. The cache size per handle has been reduced and the total SQLite cache size will never exceed 1 GB with this build.

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

Comments(0)

This release contains a single bug fix for a bug introduced in 8.6 RC released earlier today: updating data from RESULT tab failed as a SQL-statement generated contained an empty tablename.  The issue occurred when a RESULT tab was populated from ‘execute’ (F9/F5) and not from ‘execute for update’ (F8).

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

Comments(0)

Changes (as compared to 8.6 beta 3) include:

Features:
* Added support for “parenthesis’es matching” in the editor. In the editor you may find what parenthesis/bracket matches another one by simply positioning the cursor after a bracket. The actual bracket and its match will highlight. Note that this feature will work with any string – whether valid SQL or not. Both plain parenthesis’es, square brackets and curly braces are supported (independently of each others).
* If “save password” is checked for a connection, then focus in Connection Manager will be on the connection name – else it will be on the password. Before focus was always on password when Connection Manager was opened.
* User Management now fully supports MySQL ‘anonymous users’. Actually SQLyog never did before and the 8.6 betas crashed when trying to manage such (versions before 8.6 could not create such users but did not crash when managing them). Now both username and hostname may be left as an empty string. A confirmation popup will appear, though.
* Improved performance by optimizing code when SQLyog was internally performing string comparisons (what it does a lot).

Bug fixes:
* Fixed a GDI leak occurring when switching between TABS in the GUI (editor TABS or connection TABS).

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

Comments(0)

Changes (as compared to 8.6 beta2) include:

Features:
* The new User Management dialog (introduced in beta1) is now resizable.
* Added options to filter on ‘%value’ and ‘value%’ in both the ‘Filter’ menus and ‘Custom Filter’ dialogs.
* All TIME datatypes (also (YEAR(2)) are now fully supported with sorting and filtering in RESULT tab. Year(2) will sort like 70..99..00..69 (like the server itself does).
* CTRL+INS and SHIFT+INS keyboard shortcuts will now copy and paste (like CTRL+C and CTRL+V) in GRIDS.

Bug fixes:
* When opening a ANSI-encoded file with non-ASCII characters the encoding would not be detected correctly, and the content would garble (no issue with UTF8 and (Windows) UTF16-encoded files).  This bug was introduced in 8.3.
* SQL exports added redundant Unix-linebreaks, what would cause some editors to display an empty line.  This bug was introduced in 8.4.
* Fixed some minor bugs with custom filter in RESULT tab.
* The Windows Explorer dialog for selecting files to be opened could display garbage characters at the beginning with non-English locales. The reason was SPACE characters incorrectly added by SQLyog.
* SQLyog could crash when connecting from ‘import external data’ wizard to a source database with a huge number of tables in it.

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

Comments(0)