Changes (as compared to 7.14) include:

Features:
* Added an option to use Base64 encoding for communicating XML data stream with the HTTP tunneller. Using this option can be required to work around this XML-related bug in PHP: http://bugs.php.net/bug.php?id=45996

Bug fixes:
* On Windows Vista Business edition, SQLyog could crash while closing down. No other Windows OS (and also not any other Vista edition) was affected:
* Schema Sync failed with identically named Foreign Key CONSTRAINTs on identically named colums of basically same type (that could still differ in LENGTH, SIGNED/UNSIGNED specification etc.).

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

Also note that due to the added base64-option it was necessary to change the tunneller script.  To use the program with HTTP-tunnelling the old tunneller script must be replaced with the version shipped with this build.

Comments(0)

Features:
* The ‘query sniffer’ can now connect to and retrieve data from a running instance of the MySQL-proxy program used by one or more clients to connect to MySQL.  A LUA script for controlling the proxy for use with MONyog is provided with this build.  With this sniffer option the SHOW FULL PROCESSLIST statement will not be sent and thus use of ‘query sniffer’ will not put any load on MySQL.
* SSH connections will now attempt more authentication methods in case the first method attempted failed.  This will solve problems reported with tunneling to MySQL on FreeBSD that as per default does not support the full range of SSH authentication methods (and possible similar problems).

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

Also note that there are some bugs with MySQL proxy that you should know.  Most important for use with MONyog are

1) http://bugs.mysql.com/bug.php?id=31018.  Simply do not let the proxy listen on port 4041 and you will not be afffected by this.

2) http://bugs.mysql.com/bug.php?id=41417. This is more serious. If the MySQL server  behind the proxy stops running, the proxy does not return information about this.  As a consequence MONyog will have to be restarted when MySQL is again available.

Comments(0)

Happy Holidays!

Hallelujah! Christmas is back. Time to go shopping again, to make super savings of the year. In our constant endeavor to serve you better, we are obliged to help you make some significant savings on this shopping season. Claim your 30% flat discount on all your purchases. Use the coupon code xmas08. Delay not, this offer is valid only till 31st Dec 2008, 23:00 PST.

Still using SQLyog Community Edition? Held off buying SQLyog Enterprise Edition? This offer is literally too good to pass up. Its time to own your copy of SQLyog Enterprise with all the PowerTools. Check out what Enterprise Edition has to offer.

Worried about your MySQL server’s health? Monitor it like a PRO. Get MONyog – MySQL Monitor & Advisor. Your MySQL DBA in a box! Check what it has to offer.

Want to extend your maintenance period? Don’t think twice, head right away to Customer Area. On extension, you get free access to all future releases of the respective products & unlimited ticket based support for one year.

Regards,
Team Webyog

Comments(0)

Changes (as compared to 2.83) includes:

Features:

* This release adds a ‘base time’ setting in MONyog. This setting (if defined by user) will be used for calculation of uptime-based counters. The reason for this implementation is that if FLUSH STATUS is executed with a MySQL server, specific server status variables will be reset to the same value as would be after a server restart. However the ‘uptime’ status variable itself is not affected by FLUSH STATUS. And as uptime-based counters will relate the value of cumultive status variables with some intial time, using the ‘uptime’ variable as the initial time will result in calculation of misleading values if FLUSH STATUS was executed. So to get true uptime-based counters in MONyog with servers that do not support the ‘uptime_since_flush_status’ variable (and currently only 5.0 COMMUNITY servers from 5.0.37 do – not ENTERPRISE servers and not any other major branch than 5.0 and also not 5.0 before 5.0.37) you will need to define a ‘base time’ in MONyog greater than or equal to the time where FLUSH STATUS was executed last time. Also you can now discard data older than a specific time by using this setting. Refer to documentation for full details.

* Improved the purging logic with the MONyog embedded database. Now also system CPU load is considered and purging operations will be skipped if CPU is high. This is a further improvement to the change in purging logic introduced in version 2.5.

As compared to 2.9 Beta1 this also includes:

Features:

* MONyog can now be running behind an Apache server configured as ‘reverse proxy’. Before this release MONyog’s java script was not accessed due to absolute paths, as a result MONyog pages were not displaying properly.

Bug Fixes:

* Fixed high CPU usage in the ‘query sniffer’ if sniffer “Minimum time taken ” value was set to “0″ (or left blank).

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

Comments(1)

Changes (as compared to 7.13) include:

Bug fixes:
* Schema Sync did not distinguish “default NULL” and “default ” (empty string)” for string types.
* When multiple connections were open in one program instance and one connection was in wait-state (for instance due to a TABLE LOCK), the whole program could become non-responding.
* If a server thread running a query sent by SQLyog was killed, SQLyog would not always detect it. The connection window associated with that thread would then stay in wait-state forever. Due to the ‘multiple connections issue’ as described just above also the whole program could be affected.
* With MySQL servers 4.0 and before and when connecting with HTTP-tunnel, SQLyog could send an invalid SET SQL_MODE statement when copying large amounts of data. The copy operation would then abort. This bug was introduced in 7.12.
* Reconnecting while populating Object Browser could crash SQLyog.
* Fixed 2 rare crashes in Schema Sync and DATA tab (reported internally).
* Fixed a bug with ‘replace’ in editor. ‘replace’ took effect *after* cursor position not *from* cursor position, so if cursor was positioned inside the string to be replaced that particular instance would not replace.
* Refreshing the GRID moved the cursor to ‘home’ position.
* Fixed a bug in Autocomplete transaction handling (introduced in 7.13) that could cause a crash at statup.
* Migration Tool could fail to find rows when migrating from SQL server 2008.

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

Comments(1)