Important note when upgrading from versions before 3.1:
* MONyog now requires a registration code.
* Do not forget to replace the MONyog.lua script if you use the Query Analyzer with proxy-based sniffing.
* RPM users must uninstall pre-3.1 versions before installing this one.
Please read  3.1 release notes for details.

Changes (as compared to 3.1) include:

Bug fixes:
* Fixed a bug when converting timestamp format (human readable timestamp, unix_timestamp) when reading server logs. The bug could result in time being displayed 1 hour wrong in Query Analyzer if server was in a timezone using ‘daylight saving time’.
*  A  SQLite database LOCK could prevent access to the ’system’ database. Linux  Operating System counters would then not be available.
* Fixed a GUI issue with IE browser in licensing form page (command button behavior while a command was in process).
* MONyog could crash when user saved specific details (port and password)  from ‘preferences’ .

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

Comments(0)

Changes (as compared to 8.12) include:

Features:
* SQLyog can be started with a ‘-dir’ switch like “SQLyogENT -dir somefolder”. This -dir switch specifies where SQLyog will look for the sqlyog.ini file and where all writeable files will be saved.  This was mainly implemented for users that want to have all SQLyog-related files on a removeable drive or some kind of encrypted storage. Note that if you use the setting in ‘preferences’ to store TAGS file some specific place the ‘preferences’ setting will still have effect,  also if the -dir switch is used.
* Improved/rearranged the GRIDS in Data Sync and Import External Data wizards .
* SJA mail functionality now supports SSL/TLS encryption.
* ALTER VIEW will now format the SELECT-part of the VIEW definition.
* Now all batch jobs will not generate BULK INSERTS larger than 16MB (like already implemented in Import External Data in 8.11).
* In CREATE/ALTER TABLE the charset and collation columns can now be hidden for better overview (most users never use  it).

Bug Fixes:
* Edit menu showed F5 for both Refresh and Execute Query.
* Autocapitalisation settings had effect where they should not.  It has now been disabled in MESSAGES tab and in the error dialogue.
* Non-column results (like functions, expressions etc.) were affected by column-width persistence feature what they should not (it had weird effects sometimes).
* Various places a horizontal scrollbar displayed where it was not requiered.
* Fixed wrong behaviour with GRID scrollbar after resize.
* ALTER TABLE dialogue executed SHOW TABLE STATUS with no LIKE-clause.  That could be slow with a large number of big InnoDB tables in a database.
* PROFILER tab sometimes did not show after executing multiple queries.
* After doing FILTER in DATA tab, LIMIT would be reset to previous value.
* A ‘duplicate key’ error would occur with batch jobs (including Data Sync) if an autoincrement column had a ‘0′ value. We now set ‘NO_AUTO_VALUE_ON_ZERO’ sql_mode for batch jobs.
* On Wine F8 keyboard shortcut was only functional after executing a query.
* When copy database/table from a MySQL server 5.1 or higher to a 3.x or 4.0 server timestamps with ON UPDATE-clause caused a syntax error as ON UPDATE is not valid on such target.  There was no issue when source was 5.0 as we transform the CREATE statement.  But the condition had a bug so it  did not work with 5.1+ .
* It was not possible to enter an empty string in the GUI for ENUM/SET management.
* When queries were inserted from ‘edit .. paste SQL statements’ menu the tokenizer editor component could fail to identify exactly where a statement started and stopped. Reason was that the tokenizer expects Windows linebreaks (\r\n) but templates contained Unix linebreaks (\n).

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

Comments(0)

Changes (as compared to 3.09) include:

Packaging:
* The same binary/installer is now used for any license model (whether TRIAL or whatever number of servers).  A license key defines and controls how many servers can be registered. You may retrieve your license key from our Customer Portal. Before installation please ensure that you have registration details available and also soon after installation has completed please connect to MONyog from your browser and enter registration details.  This change of packaging concept simplifies the release cycle for us,  as there are now much fewer installers that will need to be built and tested.
* Also now all distributed builds will run as a  TRIAL will run for a month (not till  a fixed date)  and in the TRIAL period an unlimited number of servers can be registered.
* Unfortunately and as a consequence of the changed packaging concept it is not possible to install a 3.1 RPM build on top of a previous version as the file name format (ie. version substring) will need to change to be functional by RPM installers (’rpm’ console command and various distribution-specific commands and GUI tools).  Previous RPM versions installed must be uninstalled this time before installing 3.1 (but note that previously collected data will still be preserved and available after this). For Windows .exe and Linux .tar.gz builds there is no such issue.

Features:
* Added option to purge all stored sniffer data.  Also sniffer default settings were changed.  Quite a lot of evaluating users experienced an empty report due to previous default settings.
* Added support for MySQL Proxy version 0.7.1. A new MONyog.lua script is shipped with this build. The old script must be replaced with this one if you  use the proxy-based sniffer option.  This new script also works with MySQL Proxy 0.61.
* Filtering options were re-arranged in Query Analyzer  as per user requests.
* Lots of GUI fixes, clarifications, usability improvements etc.

Bug fixes:
* On RedHat type Linux ’service MONyogd start’ command  would sometimes not start MONyog in first attempt if MONyog process  had been killed or had crashed.
* The mail header of MONyog mail alerts did not handle unicode. Now utf8 encoding is used everywhere.

Miscellaneous (just repeating!):
* Do not forget to replace the MONyog.lua script if you use the Query Analyzer with proxy-based sniffing!
* RPM users must uninstall previous versions before installing this  one!

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

Comments(1)

Changes (as compared to 8.11 ) include:

Bug Fixes:
* Backups did not `backquote` identifiers inside the columns-list of an INSERT statement (ie. “INSERT  .. (col1, col2) VALUES ..” instead of  “INSERT  .. (`col1`, `col2`) VALUES..”). If specific (but not all) keywords were used for naming a column, backups would not restore. This bug was introduced in 8.1.
* A sync script generated with Data Sync had INSERT statements duplicated. Also this bug was introduced in 8.1.
* Fixed a painting issue when switching between DATA tab and RESULT tab.

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

Comments(0)

Changes (as compared to 8.1 ) include:

Bug Fixes:
* A memory corruption could occur when saving a file using ’save as’ (’save’ was not affected) from the editor. Various issues like painting issues and even a crash could then occur.
* Scrolling with mouse scroll-button was not functional in the new GUI  for SET/ENUM management.
* ‘duplicate table’ did not duplicate all ‘table options’ defined for a table - like MAX_ROWS etc. (Also note that Foreign Key CONSTRAINTS are not duplicated either, but that is intentional and not a bug).
* Bulk INSERTS generated by Import External Data Tool will now be restricted to 16 MB in size if max_allowed_packet in server configuration is larger than 16 MB. On specific systems/configurations memory issues were reported .

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

Comments(0)

Changes (as compared to 3.08) include:

Bug fixes:
* If MONyog user for monitoring a replicating slave did not have ‘replication client’ privilege, MySQL availability would be shown as ‘No’ in Monitors/Advisors page (even though ‘test connection’ was successful).
* If mail alerts were enabled, a syntax error in customized javascript could cause a crash.
* Charts for a server  in Dashboard page would not resume updating after a disconnect and reconnect to that server. A browser refresh was required.
* The chart ‘popups’ from Monitors/Advisors page would not populate with historical data from the MONyog database but only with fresh data sampled.
* After sorting in Query Analyzer the expand/collapse state was lost.

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

Comments(0)

One of most loved feature of SQLyog is the snappy and responsive user interface. Many of our users and customers prefer SQLyog over other tools because of this particular reason.

One reason for the zippy interface could be that SQLyog is entirely developed in C/C++, which tends to be faster than other languages when it comes to raw speed. I don’t want to start a flame war here, but our customers seem to like this fact. Using C/C++ allows us to use the native MySQL C client libraries that gives the best performance as compared to other ways of communicating with MySQL. Using C/C++ also ensures that there are no external dependencies on any bulky frameworks and the download file is relatively small.

Although using a language that complies directly to machine instructions helps a lot, but true speed comes from better algorithms. A similar analogy in the MySQL context would be that you might get some benefits from tuning your mysql.cnf/mysql.ini file, but real benefits come only when you find problematic queries in your application and rewrite them and/or create better indexes.

SQLyog uses a set of smart algorithms for its data synchronization tools. These algorithms ensure that we only transfer checksums using multiple threads and do full row transfer only when required. We have an old blog post with some benchmarking results here.

Although our data sync speeds are quite impressive, we were not happy with the results in certain scenarios. This led us to improve the data sync speeds even further with 8.1. We will publish some new benchmarking results soon in our blog.

With 8.1, we have been able to introduce massive speed improvements in the following areas:

• Data synchronization
• Auto complete
• Export as SQL (including Scheduled Backups), CSV and XML

Wait, we are not finished yet with the improvements in 8.1. This release introduces the following major features:

• Completely revamped Objects tab. The tab has been renamed to “Info”. The contents are now available in nicely formatted HTML in addition to the old text format
• Direct import of Access, Excel and CSV files. Now you don’t need to create ODBC DSN to import these file types. Just point to the files and SQLyog does the rest

Last but not the least, we continue to improve the usability with every release of SQLyog. With 8.1 we have made the following GUI changes:

• Added an option to ‘preview SQL’ in CREATE/ALTER TABLE
• Column width in all GRIDs (not only DATA and RESULT tabs) are now persistent
• New GUI for defining ENUM and SET columns in Create/Alter GUI
• Some reorganisations of menus, improved captions and explanations in dialogues and wizards etc

Needless to say, this release contains many bug fixes, UI improvements and minor features.

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

For the complete changelogs, please refer to the following posts:

• SQLyog 8.1 RC3 Release Notes
• SQLyog 8.1 RC2 Release Notes
• SQLyog 8.1 RC Release Notes
• SQLyog 8.1 beta1 Release Notes

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

Regards,
Team Webyog

Comments(5)

Changes (as compared to 8.1 RC2) include:

Features:
* Improved speed of  ‘backup’ (including  ’scheduled backup’) similar to the improvements in RC2 for ‘export’.

Bug Fixes:
* If a file named ’sja’ or ’sja.exe’ existed in SQLyog ‘AppData’ folder, SJA failed to connect with SSH tunnel. A user reported that such ’shadow copy’ was created periodically. Issue is not fully understood (except that Windows looked for PLINK too in ‘AppData’) but the fix works!
*  Fixed a scrolling issue in Data Sync GRID.

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

Comments(0)

Changes (as compared to 8.1 RC1) include:

Features:
* INFO tab/HTML option had added more information.
* The SELECT-part of a CREATE VIEW statement in INFO tab will now be formatted. Also the ‘SQL-preview’ in CREATE/ALTER TABLE dialogue will now be formatted.
* Drastically improved the speed of exports (typically 3-4 times faster). This refer to exports as CSV, XML ,HTML, Excel  XML and SQL. But note: no change with  ‘export as SQL-dump’ and ’scheduled backup’.
* Added ’scheduled backup’ option to Object Browser context menu.
* Some reorganisations of menus, improved captions and explanations in dialogues and wizards etc.

Bug Fixes:
* The dialogue for defining SET/ENUM types introduced in beta1 did not prevent duplicate entries.
* Removed redundant SPACES in CREATE statements.  These SPACES could cause formatting to garble when copying (to a web form for instance).
* Lots of fixes for small (mostly GUI-related) issues reported internally.

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

Comments(0)

Changes (as compared to 8.1 beta 1) include:

Features:
* The caption ‘Migration Toolkit’ was changed to ‘Import External Data’ in menus etc.
* The session.xml file (used by SJA internally) is now not exposed to users in Wizards. The file is created in user’s ‘AppData’ folder when job is invoked from a Wizard. If invoked from command-line files will be created in the folder where the SJA executable is, if not specified differently from command line. The reason for this change is that the two XML files (jobfile and sessionfile) have frequently been confused by users.
* The changes in beta1 were ‘polished’.

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

Comments(0)