Changes (as compared to 11.11) include:

Bug fixes:
* Autocomplete would sometimes hang or crash while editing stored procedures
* Export table data as SQL generated an incorrect create table in the 64 bit version
These were introduced in v11.0

Miscellaneous:
* Support for the client side ‘cleartext plugin’ has been removed as SQLyog is now compiled with a new client library which does not support this feature. Note that this has only relevance for users using PAM authentication with an Oracle Enterprise server. It is not relevant for the users of the freely downloadable servers from Oracle or any ‘fork’ such as MariaDB or the Percona Server.

Downloads: https://www.webyog.com/product/downloads/
Purchase: https://www.webyog.com/shop/

Changes (as compared to 5.57) include:

Features:
* Added a feature in realtime to include or exclude queries based on the search string / regular expression.

Bug fixes:
* Purging mechanism was not working properly (this bug was introduced in MONyog 5.57).
* Tag/Group names are in alphabetical order now..
* MONyog can now “Kill query” on Amazon RDS instances.
* The rendering of Dashboard page is further improved.

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

Changes (as compared to 11.1) include:

Bug fixes:
* Enum field drop down was not available in table data or result tab when http connections were used – introduced in v10.0
* Schema sync could generate an incorrect alter table statement for addition of foreign keys – introduced in v11.0
* SQLyog was not decoding the dsn password and the ssh passphrase/password after reading it from the xml file. – introduced in v11.1
* SQLyog 64 bit was extremely slow on some systems.

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

While coding, every second counts. And when the complexity of the database increases, you need to find new ways of speeding up your coding workflow. Let us admit it, we developers prefer to get all our work done using keyboard shortcuts, without having to switch to the mouse.

To streamline your entire coding experience and to speed up database navigation, here are a couple of useful keyboard shortcuts to make the most out of object browser filter in SQLyog.

Keyboard shortcuts:

1. Ctrl + B – sets focus on object browser for operations related to Object Browser.
2. Ctrl + [Up arrow] – brings focus to server/top-most element in Object Browser.
3. Ctrl + E – sets focus to Query Editor to write queries.
4. Ctrl + Shift + B – brings cursor focus on Object Browser filter.
5. Right Arrow – Expand treeview element
6. Left Arrow – Collapse treeview element
7. Esc – Removes applied Object Browser filter on the selected element.

Filter actions:

1. To filter databases, type when the server level element is selected in the Object Browser.
   

   Element selected	Filter applied
   Server/ root	Databases
   Databases	Tables
   Tables	Tables
   Columns	Tables
   Views	Views
   Stored procedures	Stored procedures
   Functions	Functions
   Triggers	Triggers
   Events	Events

2. To open table content, press enter when a table is selected in the Object Browser
3. You can bring focus to Object Browser from anywhere in SQLyog. If the root element in Object Browser is selected, on pressing keys, databases will be filtered, otherwise tables in that particular database will be filtered.

With the above tips, you will definitely save precious time by speeding up database navigation in SQLyog. If you would like to read more SQLyog quick tips, drop a comment below and we will follow up this series of blog post with your suggestions.

Changes (as compared to 11.01) include:

Features:
* Encoding of all passwords in all job files in the same way that the passwords are encoded in the SQLyog.ini file. The job files created with older versions of SQLyog will work with the new version. However, job files created with version 11.1 will not work with previous versions of SQLyog/SJA.
* A setting in the connection manager for enabling the MySQL Cleartext Authentication Plugin. This sends the password in clear text and is to be used only if the user has a secure connection and a specific need for this. For example, if the server has PAM authentication enabled, then the password needs to be sent in clear text.
* An option in the Connection Manager to keep a connection alive by pinging the server (using mysql_ping) at a user-specified interval.
Note about Keep-Alive Interval:
1. This should only be used if setting a high session timeout does not prevent disconnection
2. There could be a small lag if a query is executed at the exact same time as the ping. This is because the ping has to finish executing before the query can be executed.
3. The interval specified should be the highest possible interval which still prevents disconnection.

Bug fixes:
* Incorrect mapping of the double data type when importing from access in import external data.
* Fixed a crash which would occur while dropping an index when table data was in focus - introduced in v10.
* In Visual Data Compare, an incorrect query could be generated if the primary key column was not the first column in the table – introduced in v10.5.
* COLLATE clause was not handled properly in Schema Sync
* If the difference between the structure of 2 tables was only the character set, then Schema Sync could incorrectly generate a comma in the alter table statement.
* Session timeout value was not stored in the job files.
* DataSync in SJA for linux 64 bit would fail in some cases due to incorrect typecasting.

Miscellaneous:
* Changes in the order of execution of statements when opening a new connection. Now the user specified init-command(s) will be executed after SQLyog’s init-command(s).

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

Changes (as compared to 11.1 beta 1) include:

Features:
* Added an option in the Connection Manager to keep a connection alive by pinging the server (using mysql_ping() ) at a user-specified interval.
Note:
1. This should only be used if setting a high session timeout does not prevent disconnection
2. There could be a small lag if a query is executed at the exact same time as the ping. This is because the ping has to finish executing before the query can be executed.
3. The interval specified should be the highest possible interval which still prevents disconnection.

Bug fixes:
* COLLATE clause was not handled properly in Schema Sync
* If the difference between the structure of 2 tables was only the character set, then Schema Sync could incorrectly generate a comma in the alter table statement.

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

Changes (as compared to 11.01) include:

Features:
* Encoding of all passwords in all job files in the same way that the passwords are encoded in the SQLyog.ini file. The job files created with version 11.1 will not work with previous versions of SQLyog/SJA. However, job files created with older versions of SQLyog will work with the new version.
* A setting in the connection manager for enabling the MySQL Cleartext Authentication Plugin. This sends the password in clear text and is to be used only if the user has a secure connection and a specific need for this. For example, if the server has PAM authentication enabled, then the password needs to be sent in clear text.

Bug fixes:
* Incorrect mapping of the double data type when importing from access in import external data.
* Fixed a crash which would occur while dropping an index when table data was in focus - introduced in v10.
* In Visual Data Compare, an incorrect query could be generated if the primary key column was not the first column in the table – introduced in v10.5.

Miscellaneous:
* Changes in the order of execution of statements when opening a new connection. Now the user specified init-command(s) will be executed after SQLyog’s init-command(s).

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

This is the current (and supposed to be the last) MONyog release in the 5.5x series.  Refer online documentation for details of changes in this and previous releases.  The major scope of all releases in 5.5x series has been improving stability, performance and responsiveness under heavy load -  such as large number of servers both registered and displayed at the same time, user activity by multiple users at the same time, ‘query sniffer’ running in the background etc.  We have worked with a number of customers using MONyog in such demanding environments during the 5.5x development phase.

Changes in this 5.57 release (as compared to 5.56) include:

Bug fixes:
* The rendering of Monitors and Dashboard page was slow with large number of servers both registered and selected and when multiple users were connected simultaneously displaying the page. It could take one minute or more in some cases. It is now a matter of seconds.
* With a large number of servers registered, editing details for one was slow. Also this could take around 1 minute, and the improvement is in the same range as above.
* Event manager’s database (Events.data) is now moved from global level to server level in order to prevent locking problems with a large number of servers. MONyog will migrate data first time it starts after the upgrade.
* Fixed a multi-threading issue that in rare cases could crash MONyog while registering more than one server at the same time.
* Fixed a rare crash in MONyog while viewing replication tab.
* Fixed a rare crash in MONyog while resolving CSO’s (“Custom SQL Objects”).
* MONyog could fail to send mail alerts if a single mail contained alerts for more than one monitor.
* MONyog was showing errors in Query Analyzer, Realtime and Processlist pages when a query contained characters used for specifying HTML tags.
* If a registered server was not a slave but marked as such in Advanced Settings .. Replication, MONyog was leaking connections every time it was collecting data and finally connections (from MONyog as well as other clients) could fail due to ‘max_connections’ setting being exceeded.
* For MySQL InnoDB-related monitors were showing “(n/a)”. The reason was removal of the ‘have_innodb’ server variable in MySQL 5.6.

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

Changes (as compared to beta 1) include:

Bug fixes:.
* The rendering of Monitors and Dashboard page was slow with large number of servers both registered and selected and when multiple users were connected simultaneously displaying the page. It could take one minute or more. It now renders in few seconds 2nd and following times details for a server are displayed – first time it still may take longer however. This optimization was started in beta 1 for the Monitors page, but is now extended to Dashboard page as well.
* Event manager’s database (Events.data) is now moved from global level to server level in order to prevent locking problems with a large number of servers. MONyog will migrate data first time it starts after the upgrade.
* Fixed a multi-threading issue that in rare cases could crash MONyog while registering more than one server at the same time.
* Fixed a rare crash in MONyog while viewing replication tab.
* Fixed a rare crash in MONyog while resolving CSOs (“Custom SQL Objects”).
* MONyog could fail to send mail alerts if a single mail contained alerts for more than one monitor.
* MONyog was showing errors in Query Analyzer, Realtime and Processlist pages when a query contained characters used for specifying HTML tags.
* If a registered server was not a slave but marked as such in Advanced Settings .. Replication, MONyog was leaking connections every time it was collecting data and finally connections (from MONyog as well as other clients) could fail due to ‘max_connections’ setting being exceeded.

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

Bug fixes:
* Fixed 2 issues introduced in ‘Import External Data’ when rewriting program code for 64-bit compilation as of version 11.0: 1) A job file with a (NDB-cluster) TABLESPACE specification and a WHERE clause failed to load in the wizard 2) non-ASCII defaults defined on non-unicode/ANSI string columns on source would be mapped against a UTF8 byte pattern and would garble for same reason.
* Fixed a rare crash occurring when dropping indexes from the Object Browser repeatedly.

Downloads: http://www.webyog.com/product/downloads
Purchase: http://webyog.com/shop