Changes (as compared to beta 2 ) include:

Features:
* Added an option in GUI to specify a sql_mode for the connection as well as for using the GLOBAL mode for the SESSION. The ” (‘empty’) SESSION mode is default for new connections, but you may change from Connections Manager ‘advanced’ tab.
* Added CTRL+ALT+L keyboard shortcut for switching GRID and FORM mode.

Bug fixes:
* Scrolling has been improved while multiple result sets are present.
* When formatting multiple SQL queries SQLyog removed empty lines between queries.
* There was no option not to save connection details when connecting with new connection details. The Connection Manager  fix in 8.7 missed that point.
* Sometimes the text view in result tab would truncate the last line of the data. This was introduced in 8.8 Beta2.

Miscellaneous:
* ‘Notifications Services’ was renamed to ‘SQL Scheduler and Reporting Tool’

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

Comments(0)

Cloud, cloud, cloud. Cloud computing has become the phrase du jour, says one analyst from Gartner. But with many moving to cloud for its obvious benefits, it can no longer be ignored. An offshoot of cloud computing is utility computing. What interests us here is Database-as-a-Service, in particular MySQL on cloud.

Coming back to our original question – Is your MySQL monitoring tool cloud ready? Well, many monitoring tools need agents on server to be monitored. For obvious reasons database-on-cloud vendors don’t allow one to install anything on the servers. With Amazon launching RDS (which is nothing but MySQL instance on cloud) there is a pressing need for tools that can monitor MySQL on cloud. Database-as-a-Service space is getting hotter by the every passing day. Few more vendors that I can reckon are – ClearDB, Xeround & FathomDB.

Another key feature of cloud is scalability. You can add more resources or servers in a click of button. Can your MySQL monitoring tool scale in tandem with the increasing servers on cloud?

Cloud is also known for how fast one can get started. You can setup & start using most of the cloud services in matter of minutes. How fast & easy is it to setup your MySQL monitoring tool?

We are pleased to announce the release of MONyog 4.2 – MySQL Monitor & Advisor, one of the most significant releases till date. MONyog is by design cloud ready. It requires no agents on the server & hence can monitor MySQL instances running on cloud. Here is a post from my colleague on monitoring Amazon RDS with MONyog. According to our internal benchmark reports a single instance of MONyog can monitor 500+ servers (even at 1 sec collection intervals) effortlessly. Perfect match for database-on-cloud solutions. Additionally MONyog is light weight. It has its own tiny web-server & does not ask you to install Apache, Java etc. It can get up & running in under 2 minutes.

Start your evaluation of MONyog – MySQL Monitor & Advisor here. Let us know your thoughts. We are all ears.

Cheers,
Team MONyog

Comments(3)

This release significantly improves MONyog’s performance under heavy load and fixes minor bugs.

Bug fixes
*  MONyog could crash while monitoring hundreds of servers through SSH tunneling with a small data collection interval (1 or a few seconds).
*  Charts in the I/O section under Monitors/Advisors or Dashboard displayed wrong history (last 14 seconds had the same values as the value in the 15th second).
* Sometimes, while analyzing the slow query log, some timestamps contained the default Unix timestamp.
* If the name of a counter or caption of dashboard chart contained single quotes, the chart displayed “Invalid XML Data”.
* Filtering while displaying the Sniffer output was not working when there was a change in the filter conditions.
* The Linux command ‘Service MONyogd status’ did not always  display the correct result.
*  The Processlist page in MONyog threw ‘constraint failed’ error when the process ID was a large number.

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

Comments(1)

Happy New Year 2011!

Thanks for participating in Christmas Giveaway Contest. It was challenge for us to select 2 best among all those nice videos. We know a lot of effort goes into creating such videos. Thanks again for the love. The 2 iPad 3G winning videos are:

Congratulations to Kjeld & Brian. Please contact us at info@webyog.com with your postal address. A select few videos will start appearing on the site soon.

Cheers,
Chirag
Team Webyog

Comments(1)

Changes (as compared to beta1 ) include:

Bug fixes:
* Modified the SQLyog installer to prevent installing on an unsupported platform.
* Fixed a bug in automatic indentation introduced in 8.7. The cursor was not indented correctly following the previous line if indentation was more than one SPACE or TAB character.
* An orphaned PLINK instance could be left running when closing a SSH connection.  It would typically happen with rather slow servers or connections and when connection was closed very shortly after it was established.
* The memory handling improvements for DATA and RESULT tab in beta1 were not complete in RESULT tab.
* All SPACES were stripped out when displaying the query at the bottom of RESULT tab. This bug was introduced in beta1.

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

Comments(0)

Changes (as compared to 8.71 ) include:

Important notice:
* With this release the PHP-script used for HTTP-tunneling has been updated. This is required to support SOCKET connections with HTTP-tunneling. Upgrading users that use HTTP-tunneling will have to replace the file on their server(s) – also if they do not use SOCKET connections.

Features:
* In Schema Sync and ‘copy database’ connections are now identified with their color code as defined in the connection manager.
* In ‘Import External Data’ import of Foreign Keys/relationships are now disabled as default when importing from Access and the interface has been clarified in this respect. The reason is that unless Access security settings are changed for the database it is not possible to import Foreign Keys/relationships and an error would occur if not security settings allowing for exposing relationships were defined.
* Implemented a tooltip on Query tabs (including Query Builder and Schema Designer tabs) displaying full path to file (if any).
* With HTTP-tunnel there now is an option to specify a MySQL socket file for connection to MySQL. Note that in that case MySQL ‘host’ and ‘port’ settings are ignored (if any).
* Hexadecimal and binary/base2 strings can now be entered for any datatype using ” x’..’ ” and ” b’..’ ” notation in GRIDs. SQLyog will now not ‘quote’ such values starting with “x’” and “b’” when performing DML operations from the GRIDs.
* Implemented support for the BIT datatype. In DATA and RESULT tab BIT’s will now display using ” b’..’ ” notation what in combination with the point above ensures that BIT data are updateable. Note that with HTTP-tunnel this is not functional in RESULT tab as PHP does not provide sufficient meta-information for a result set to decide column-widths.
* Drastically improved memory management in DATA and RESULT tabs. This allows for larger result sets in memory and improves scrolling. This also fixes a bug introduced in 8.7 where scrolling could render wrong values displayed in the GRID.

Bug fixes:
* SQLyog will now never use TIMESTAMP(14) but only TIMESTAMP. TIMESTAMP(14) returns an error in MySQL 5.5.
* Fixed a truncation when importing data from ‘standalone’ Primebase server (note: not MySQL with PBXT storage engine. This never was a problem).
* When editing a very large ENUM-list SQLyog could crash.
* Schema Designer did not properly keep track of names of renamed tables.
* Fixed a truncation of display in Form View with specific character sequences.
* Right-clicking a JOIN line/symbol in Query Builder could fail to bring up the JOIN properties dialog.
* The SQLyog editor highlighted a keyword followed by a dot as a keyword instead of recognizing it as an identifier.
* While ‘rebuilding tags’ autocomplete did not return database objects.
* The option in ‘preferences’ to ‘generate queries using backticks’ did not have effect when double-clicking an identifier name into the editor. This is fixed and additionally now also autocomplete will ´backtick`objects if the preferences’ option is selected.
* Lots of GUI fixes and lots of internal optimizations.

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

Comments(3)