Changes (as compared to 3.02 include – and also note that 3.03 was never released for the public):

Features:
* Optimizations in the handling of the MONyog embedded database. In particular users with a very large retention timeframe setting and rather short sample interval (resulting in large databases) will benefit from that.

Bug fixes:
* The above will also fix an issue where MONyog seemed to ‘hang’ when saving connection details for a connection having large database files.

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

Comments(0)

Changes (as compared to 8.02) include:

Features:
* New major feature: column width persistence in GRIDs.  Once you have defined a column width for a combination of database/table/column the defined column width will always be used.  Note that connection details are not used for identifying columns with this new functionality so with replicated and identically named synchronized databases it is sufficient to define in one place.  Alias’ed columns in results are handled by the column name  and not the alias. Non-column results (like constants, results of expressions/functions, returns of SHOW etc.) are not supported currently.  The feature can be turned on/off. Note that if both this new option and the old  ”Truncate column headers … ” is checked in program ‘preferences’ the “Truncate ..” option will be ‘overridden’ by the new column width persistence feature.
* ‘Find’ dialogue will now remember last used values.
* Added an option to open a file in a new tab (Editor tab and Schema Designer tab).
* Added an option to use ‘hard SPACES’ for tabulation in the editor (with this checked the code will display identically when copied to other programs).
* In editor you can now start typing a query in any position and <ENTER> will position cursor in same position of the next line.
* Added ‘view data’ option to the context menu of a VIEW.
* In Query Builder PK-columns are now marked with a (beginning) ‘*’ .
* In Object Browser introduced a new ‘key’ icon for PK-columns.
* ‘Find’ was implemented in BLOB viewer. Currently there is only the Ctrl+F shortcut to  do this  and no other GUI option (no button or whatever).
* In Schema Sync added a ‘refresh’ option in the dropdowns for <source> and <target> databases.
* The program dialogues for  SHOW variables/processlist/status, SHOW warnings with CSV-import and Table advanced properties are now resizable.

Bug Fixes:
* Fixed an issue where SQLyog failed to SET NAMES when reconnecting.
* Exporting floating point data as Excel XML could truncate data.
* Quite a lot of fixes for (mostly cosmetical) GUI issues.
* Fixed some ‘flickering’ issues.

Miscellaneous:
* For 16×16 icons we now use the icons from before 8.0.  The new icons had too many details for this resolution.   Also now users that prefer the old icons can have them!

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

Comments(3)

Changes (as compared to 8.01) include:

Features:
* Both SQLyog and SJA will now detect if Base64 encoding is required for HTTP-tunnel.

Bug Fixes:
* Importing external scripts with a large number of DDL-statements was slow with Auto Complete turned on (due to redundant updations of the Auto Complete database).
* Deseleting a single object (like a single table) in the export dialogue also deselected all objects in other categories (like all non-table objects).

Funtionality changed:
* CHUNK setting (for exports) now also has effect for non-HTTP-tunneled connections. Using this option is required if it takes more time to retrieve data from a table than server ‘net_write_timeout’ setting.
* SQLyog will now not reconnect if connection is lost during imports. Instead an error message will prompt (the reason for this is that session variables defined on top of the script would be reset to server defaults with reconnection. As a result (and most important) special characters could garble and other errors could occur as well).
* When trying to INSERT or UPDATE spatial data types from the DATA/RESULT tab SQLyog will now throw an error. Spatial data must be handled from the editor (but a result set from a table with spatial columns can be updated from RESULT tab if there are no spatial columns in the result).

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

Comments(0)

Changes (as compared to 8.01) include:

Features:
* Both SQLyog and SJA will now detect if Base64 encoding is required for HTTP-tunnel.

Funtionality changed:
*  CHUNK setting  (for exports)  now also has effect for non-HTTP-tunneled connections.  Using this option is required if it takes more time to retrieve data from a table than server ‘net_write_timeout’ setting.
*  SQLyog will now not reconnect if connection is lost during imports.  Instead an error message will prompt (the reason for this is that session variables defined on top of the script  would be reset to server defaults with reconnection.  As a result (and most important) special characters could garble and other errors could occur as well)..
* When trying to INSERT or UPDATE spatial data types from the DATA/RESULT tab SQLyog will now throw an error.  Spatial data must be handled from the editor (but a result set from a table with spatial columns can be updated from RESULT tab if there are no spatial columns in the result).

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

Comments(0)

Changes (as compared to 3.01 include):

Bug fixes:
* The alerts and advisors for slave ‘read-only’ mode were in conflict.  We will now advise for a slave (in production) that ‘read-only’ mode should be ON (only the replication thread can write) and alert accordingly.
* Add/Edit connection failed with connection names using SPACE character.
* Proxy connection was not established when proxy was started for a server present in a remote system.

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

Comments(0)

Hi,

We are pleased to announce MONyog 3.0 – a major new release. MONyog is rapidly becoming a cost-effective alternative to expensive proprietary tools for MySQL monitoring.

Unlike databases like SQL Server & Oracle, MySQL does not provide powerful APIs to gather extensive profiling information about each and every query. MySQL developers and DBAs have largely used on a combination of the following techniques to find problem SQL:

1. SHOW PROCESSLIST
2. Slow Query Log and General Query Log
3. SHOW PROFILES (available from MySQL Community version 5.0.37)
4. Capturing and filtering tcpdump output

To overcome the shortcomings of profiling features in the MySQL server, MySQL Proxy was introduced which allows developers to route queries via MySQL Proxy and then extract profiling information from MySQL Proxy. (It also provides other features like load balancing, query rewriting, etc.)

MONyog 3.0 can now collect profiling info from MySQL Proxy. All you need to do is to start MySQL Proxy with a lua script provided with the MONyog distribution and then configure MONyog to collect data from MySQL Proxy. With the introduction of MySQL Proxy support, MONyog becomes the only GUI MySQL monitoring tool in the market to support the following features for finding problem SQL:

1. SHOW PROCESSLIST snapshots at regular intervals
2. Slow Log and General Query Log Parser
3. MySQL Proxy support.

Another major change in MONyog is completely revamped monitors and advisors. Most of the monitors and advisors in MONyog 1.x and 2.x were written by Webyog engineers. While we have been developing MySQL tools for the last 5 years, coding MySQL monitors and advisors is not one of our core strengths. Our core competence is in developing slick GUI tools at a fraction of the price of our competitors. So we sought help. Percona, with their huge experience in MySQL internals and MySQL tuning was a perfect choice. With the help of Percona, we have rewritten most of the monitors and advisors in MONyog 3.0.

Embedded below is the Screencast on how MONyog helps you in finding Problem SQL
Screencast on Query Analyzer from Team Webyog.

Last but not the least, you can use all features of MONyog 3.0 without installing any agents or additional software on your production MySQL servers! Download a copy of the trial now from http://www.webyog.com/en/downloads.php. Do send us your valuable feedback.

MONyog is an Enterprise monitoring tool for MySQL servers without the high price tag usually attached with Enterprise tools. Pricing starts at $99/server and $999 for Unlimited servers. Additionally, the licenses are “perpetual” and not “subscription based”, so don’t have to cough up money every year if your installed version of MONyog is good enough for your monitoring needs.

Finally, for a complete list of features and bug fixes in MONyog 3.0, please refer to the following posts.

• MONyog 3.0 Release Notes
• MONyog 3.0 beta2 Release Notes
• MONyog 3.0 beta1 Release Notes

Regards,
Team Webyog

Comments(1)

Changes (as compared to 3.0 beta 2 include):

Features:
* MONyog is able to read microseconds from proxy and if available in slow query log and will (for readability) show in milliseconds.
* Sniffer output will now display MAX, first seen time, last seen time, query occurrence %. Also query occurrence % and Lock Time for a query was added to slow query log and query occurrence %  was added in general query log displays.
* Added an option to execute FLUSH STATUS from inside MONyog.

Miscellaneous:
* Grouping of queries is now case insensitive for all forms of query analysis.
* The browser cache support added in beta2 has been temporary removed. There is a problem with Firefox3 with cache and AJAX (update requests were not sent from a cached page – only current cache content was reloaded). Note that FF3 users who had beta2 installed will need to clear the browser cache after installing this build.
* Note that  the ‘qd.lua’ script for PROXY-based sniffer has been both updated and renamed to ‘MONyog.lua’.  For use with this MONyog version the old script must be replaced.

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

Update: MONyog 3.01 has been released with a fix for the following bug.

* For 5.1.x servers, MONyog did not fetch the log details like slow query log and general query log file path in ‘Connection details’ section.

Please download it here.

Comments(1)

Changes (as compared to 8.0) include:

Bug Fixes:
* Query profiler could fail to fetch the result of SHOW PROFILE for (text-wise) long queries.

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

Comments(0)

Hi,

SQLyog 8.0 is a major new version of SQLyog introducing major features like Query Profiler, SQL Formatter and vastly improved look and feel.

Query Profiler:

MySQL has always lacked the sophisticated profiling tools shipped with proprietary databases like SQL Server, etc. MySQL developers have largely depended on EXPLAIN for tuning queries. The SHOW PROFILE patch by Jeremy Cole was introduced in the MySQL Community version 5.0.37 and it provided much more insight into where the query spends its time. However, to take advantage of this feature, MySQL developers were supposed to switch on profiling, run their queries and then filter the profiling data from a table that contained the profiling results of the last few profiled queries. A lot of manual book-keeping is required to take advantage of this  powerful feature. In an ideal situation, the MySQL developer should execute the queries and the profiling info should be available along with the result-set. Unfortunately, none of the MySQL client tools (desktop or web-based) provide intrinsic support for this feature.

Another great tool to profile queries is mk-query-profiler, part of maatkit. It does an incredible job in displaying the changes in STATUS variables due to execution of a query. It also presents the information in a very readable format, making it easy for the developer to tune queries. However, one problem with this tool is the lack of integration with any MySQL GUI client tool. So if an user is using a GUI tool to write queries, she needs to profile queries in a separate step using mk-query-profiler.

SQLyog 8.0 tries to address these problems by integrating all of the above profiling methods in a single intuitive GUI. It takes care of switching on profiling and taking the snapshot of the STATUS variables before and after the execution of query. It then aggregates these data (along with EXPLAIN and EXPLAIN EXTENDED results) and presents the aggregated info in a single window. The user just needs to type the query as usual and all other commands required to capture profiling information are executed behind the scenes by SQLyog. Also, along with the changes in the STATUS variable, the profiler shows a simple description of the STATUS variables that changed due to execution of the query.

In summary, the SQLyog’s Query Profiler helps the user get more insight into the execution of a query by:

• Using SHOW PROFILE information
• Capturing the difference in STATUS variables due to execution of a query
• Using EXPLAIN statement, and
• Using EXPLAIN EXTENDED statement

Embedded below is the screencast on how Query Profiler helps you in optimizing the queries.

SQL Formatter:

There is absolutely no doubt that properly formatted SQL code makes SQL much more maintainable. Most experienced SQL developers make sure that they follow some SQL formatting guidelines to make their code readable and maintainable. However, many times we come across unformatted SQL written by others or sometimes we are too lazy to write properly formatted SQL ourselves! SQLyog 8.0 comes to the rescue! It neatly formats the SQL with the click of a button. This feature is also known as “SQL Beautifier” or “SQL Pretty Printer” in various other software.

SQL Formatter in action

New look and feel, improved icons:

Though SQLyog has added tons of features to its quiver, it looks the same as it did in 2004. So, we thought of overhauling its looks. Result was adding new icons with Vista theme, toolbar containing large icons for frequently used tasks, gradient based tab and grids, etc. Here is a screenshot of SQLyog 8.0.

The All New SQLyog 8.0

Finally, for a complete list of features and bug fixes in SQLyog 8.0, please refer to the following posts. (Note that SQLyog 8.0 was previously named as SQLyog 7.5. Due to the inclusion of many major features it is being released as SQLyog 8.0.)

• SQLyog 7.5 RC2 Release Notes
• SQLyog 7.5 RC Release Notes
• SQLyog 7.5 beta2 Release Notes
• SQLyog 7.5 beta1 Release Notes

Note: For few hours past this announcement you may receive registration code for 7.x when purchasing 8.0. If the code does not work please get the right one form Customer Portal.

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

Regards,
Team Webyog

Comments(20)