SQLyog MySQL GUI 8.2 Has Been Released.

From SQLyog 8.2, we have introduced 3 editions of the commercial version of SQLyog. When we had first released SQLyog in 2003, it had a very few features. We have been aggressively adding new features for the last 6 years. Now SQLyog has got a huge number of tools and features.

Not all tools are useful to every SQLyog customer. In particular we had several requests for a cheaper ‘entry’ edition with the most popular features: HTTP-tunneling, SSH-tunnelling and autocomplete. This is now available as Professional edition.

SQLyog is no longer an “one-size-fits-all” application. SQLyog caters to a very diverse range to customers. Some use it as MS-Access type application for simple database needs while others might use it only to profile and tune queries for a large scale production environment. The Ultimate edition is for those users in particular that have full control over their database and their applications.

We thought it is the right time to have multiple editions of SQLyog. This means that people can start with the lower edition and gradually move to a higher edition if the need arises. This will also reduce the overall complexity and total cost of ownership for several customers.

The various editions of the commercial version SQLyog are Professional, Enterprise and Ultimate. You can find the comparison sheet here.

We have also migrated all existing SQLyog Enterprise customers to SQLyog Ultimate. The yearly upgrade and prices of SQLyog Ultimate are same as SQLyog Enterprise upgrade prices. So if you are already an Enterprise customer your Total Cost of Ownership remains same while you continue to enjoy the powerful tools and features of Ultimate.

Feel free to leave your feedback in the comments section.

Below follows release notes in traditional form:

Changes (as compared to 8.18) include:

Features:
* Added a ‘Schema Optimizer’ feature. Based on “procedure analyse()” it will propose alterations to data types for a table based on analysis on what data are stored in the table. The feature is available from INFO tab/HTML mode. Refer to documentation for details.
* A table can now be added to Query Builder canvas multiple times. A table alias is automatically generated for second and higher instance of the table. This is required for special queries like self-JOINs (note: table alias support in Query Builder is an ongoing process).
* In the ‘Import External Data’ wizard same import settings can now be applied to all tables in one operation.
* In MESSAGES tab we are now displaying the query if error occurs during execution in order to make it easier to identify what query raised an error when executing multiple statements.

Bug Fixes:
* ‘Import External Data Tool’ -TRIGGERS did not use the Primary Key for the WHERE-clause if a PK existed on source (all columns were used with the WHERE instead). This could cause problems with tables having Floating Point data.
* A malformed XML-string could cause failure to connect with HTTP tunneling. This was a rare issue only.
* After DROP a ’stored program’ followed by CREATE same, autocomplete would not recognize the ’stored program’ unless after a program restart.
* ‘duplicate table’ has an option to duplicate triggers defined ON that table, but the way we named the new trigger could cause inconsistencies. Now the new trigger will be named ‘oldtriggername_newtablename’.
* Autocomplete was not functional with names of Triggers and Events.
* In MESSAGES tab font could change if non-ASCII characters were displayed.
* ALTER TABLE failed to rename a column when old and new column name only differed by letter-case. Actually the dialogue just shut down.
* A calculation error could cause export tools to create BULK INSERT statements larger than specified by user.
* Import External Data Tool will now always map any autoincrement type from ODBC sources to a MySQL autoincrement integer. Before this datatypes that could autoincrement on source but not in MySQL (example: a SQL Server ‘decimal autoincrement’) failed to import.
* Now Import External Data Tool will convert SQL Server ‘GETDATE()’ to MySQL ‘now()’. Before this an error occurred at import with GETDATE()’s.
* Fixed a Object Browser flickering issue when refreshing.

Packaging and licensing:
* The licensing scheme for SQLyog has changed: there is now the free Community version (unchanged) and 3 different commercial licensing models: Professional, Enterprise and Ultimate. Refer to comparison matrix for details . All existing Enterprise users were upgraded to Ultimate at no cost. Also note that this 8.2 version requires a new registration code as compared to 8.1x. Existing  Customers will get from our Customer Portal.  Please ensure that you have the new registration code available when installing. Also note that Professional, Enterprise and Ultimate installer files are now all named ‘SQLyog82.exe”. TRIAL is named ‘SQLyog82Trial.exe’ and Community name is ‘SQLyog82Community.exe’. The reason for this change is that it simplifies maintenance of the webshop records and download area files for us.
* TRIAL now has ULTIMATE features with the exception that there is a restriction on how many tables and other objects can be handled in a single SJA job (similar to what was previously the case with ENTERPRISE TRIAL).

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

Comments(13)

The primary reason for this release are the bug fixes (included with both 8.18 and 8.2 RC2):

* Schema Sync failed to set the auto-increment flag when syncing a table having this flag to a table not having. This bug was introduced in 8.13.
* SMTP authentication and notification could fail with passwords having special characters.
* Solved a crash with Query builder while creating VIEWs.
* INFO tab/HTML format was showing incorrect value for table’s data size having values in Gigabytes.

Additionally 8.18 includes  Bug Fixes already available in 8.2 beta and RC’s:
* The display of the optimized query from EXPLAIN EXTENDED is now truncated to 2 KB. With long BLOB/TEXT data there will need to be some limit.
* Schema Sync will now query Information_Schema for a VIEW definition. MySQL sometimes returns ‘databasename.viewname’ and not just ‘viewname’ when using SHOW CREATE .
* The fix in 8.15 for the issue that Windows Vista and higher could warn that SQLyog was not properly installed was not complete. It could still happen.

Additionally 8.2 RC2 includes:
* Schema optimizer will now throw a warning if table is empty. Also interface now has link to help/documentation.

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

Comments(0)

Changes (as compared to beta 1) include:

Bug Fixes:
* A calculation error could cause export tools to create BULK INSERT statements larger than specified by user.
* Import External Data Tool will now always map any autoincrement type from ODBC sources to a MySQL autoincrement integer. Before this datatypes that could autoincrement on source but not in MySQL (example: a SQL Server ‘decimal autoincrement’) failed to import.
* Now Import External Data Tool will convert SQL Server ‘GETDATE()’ to MySQL ‘now()’. Before this an error occurred at import with GETDATE()’s.
* Schema Sync will now query Information_Schema for a VIEW definition. MySQL sometimes returns ‘databasename.viewname’ and not just ‘viewname’ when using SHOW CREATE.
* Fixed a Object Browser flickering issue when refreshing.
* The fix in 8.15 for the issue that Windows Vista and higher could warn that SQLyog was not properly installed was not complete.  It could still happen.

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

Comments(0)

Changes (as compared to 8.17) include:

Features:
* Added a ‘Schema Optimizer’ feature. Based on “procedure analyse()” it will propose alterations to data types for a table based on analysis on what data are stored in the table. The feature is available from INFO tab/HTML mode.  Refer to documentation for details.
* A table can now be added to Query Builder canvas multiple times.  A table alias is automatically generated for second and higher instance of the table. This is required for special queries like self-JOINs (note: table alias support in Query Builder is an ongoing process).
* In the ‘Import External Data’ wizard same import settings can now be applied to all tables in one operation.
* In MESSAGES tab we are now displaying the query if error occurs during execution in order to make it easier to identify what query raised an error when executing multiple statements.

Bug Fixes:
* ‘Import External Data Tool’ -TRIGGERS did not use the Primary Key for the WHERE-clause if a PK existed on source  (all columns were used with the WHERE instead). This could cause problems with tables having Floating Point data.
* A malformed XML-string could cause failure to connect with HTTP tunneling. This was a rare issue only.
* After DROP a  ’stored program’ followed by CREATE same,  autocomplete would not recognize the ’stored program’ unless after a program restart.
* ‘duplicate table’ has an option to duplicate triggers defined ON that table, but the way we named the new trigger could cause inconsistencies. Now the new trigger will be named ‘oldtriggername_newtablename’.
* Autocomplete was not functional with names of Triggers and Events.
* In MESSAGES tab font could change if non-ASCII characters were displayed.
* The display of the optimized query from EXPLAIN EXTENDED is now truncated to 2 KB. With long BLOB/TEXT data there will need to be some limit.
* ALTER TABLE failed to rename a column when old and new column name only differed by letter-case.  Actually the dialogue just shut down.

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

Comments(0)

Changes (as compared to 8.16) include:

Bug Fixes:
* When connected to a 5.0 server compiled without PROFILING option and with Query Profiler/SHOW PROFILE  feature enabled SQLyog would still send PROFILING-related queries.  It was not properly detected that the server did not support this. MySQL versions from 5.1 and up (also when compiled without PROFILING option) were not affected.
* In DATA and RESULT tabs/text mode unicode/non-ASCII characters could cause a change of the font that was used for displaying data. This was an old bug from when introducing full unicode support in 6.0.
* In RESULT tab BLOB/TEXT data would sometimes not display beginning of data in GRID. This bug was introduced in 8.15.

Miscellaneous:
* EXPLAIN EXTENDED option is now disabled as default in Query Profiler.

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

Comments(0)

Changes (as compared to 8.15) include:

Bug Fixes:
* Exports as Excel-XML was broken in 8.15 . Empty strings and ZERO’s occurred instead of data.
* ‘Search and replace’ could truncate the result. Also this bug was introduced in 8.15.

Miscellaneous:
* SQLyog Application Manifest was updated to return version information.

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

Comments(0)

Changes (as compared to 8.14) include:

Features:
* Added an option to execute SHOW WARNINGS automatically if the ‘warning-count’ is not 0. The output will appear in MESSAGES tab. Note: this is not implemented for HTTP-tunneling.
* Improved the memory handling in GRIDS with BLOB/TEXT columns. This fixes some slugginess when scrolling a GRID containing such data.

Bug Fixes:
* A dump containing VIEWs created on an early 5.0-server could fail to restore on recent servers. The underlying reason is a bug with the ‘default’ column in the output of SHOW FULL FIELDS on the early 5.0 servers. But we can avoid using this information and this is what we did now.
* Copy database/table from a 3.x or 4.0 server to a more recent server failed with column names containing special characters.
* If a sqlyog.ini files exists in installation folder it should be copied to ‘AppData’ folder. This is required for upgrading from versions before 6.06. However with latest releases an empty file was created in ‘AppData’.
* The ‘Import External Data Tool’ could truncate strings when importing data from a 4D database. It is actually a bug in the 4D ODBC driver but we found a workaround.
* SSL-connections failed if authentication keys were created with cipher option.
* SQL-exports generated INSERTS for MERGE and FEDERATED tables.
* In INFO-tab/text-mode we will now not highlight ’string literals’. A comment with an odd number of quotes would make following lines display with ’string literal’ highlighting/coloring.
* When connected with SSH-tunneling to a Windows machine with Cygwin SSHD the bash.exe process created for each connection did not close again.
* CREATE TABLE … advanced options did not set some create-options to ‘default’.
* Execution of some queries would be slow with Query profiler/EXPLAIN extended selected. Most important queries with a UNION were affected. Technically it was an issue with the Query Formatter code and how it ‘hooked’ into the program. This bug was introduced in 8.0.
* Windows Vista and higher could warn that SQLyog was not properly installed due to lack of an Application Manifest. It was false alarm but now such Manifest is included with the installer.

Miscellaneous:
* Functionality change: Before this release we stripped out the database name from Stored Program and View SQL-code when generating SQL-dumps and when copying a database to another host. Also Schema Sync did with VIEWs. This was in order to make it easy to import/copy to another database.  However with tables named identical to the database and when database names was a substring of a table name it failed sometimes.  We realize now that SQL code inside Stored Programs and Views may be so complex that parsing for the database name and stripping it is not safe.  With this release we have stopped this ’stripping’ and Stored Programs and Views will be dumped by SQLyog identically to what  ‘mysqldump’ does.

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

Comments(0)

Changes (as compared to 8.15 RC) include:

Bug Fixes:
* Execution of some queries would be slow with Query profiler/EXPLAIN extended selected. Most important queries with a UNION were affected.  Technically it was an issue with the Query Formatter code and how it ‘hooked’ into the program. This bug  was introduced in 8.0.
* Copy database/table could be slow if  BULK INSERTS option was selected in ‘preferences’. This bug  was introduced in 8.15 beta 1.
* 8.15 RC could crash when executing a LOAD DATA statement. This first RC was build with a recent 5.1 client library. Before 8.15 RC we used a 5.0 library.  We have now reverted back to 5.0 (5.0.86 client library is used with this release). Issue with the 5.1 client library is not fully understood but it may be related to known memory issues reported with it.

Miscellaneous:
* Functionality change: Before this release we stripped out the database name from Stored Program and View SQL-code when generating SQL-dumps and and when copying a database to another host. Also Schema Sync did with VIEWs. This was in order to make it easy to import/copy to another database. However with tables named identical to the database and when database names was a substring of a table name it failed sometimes. We realize now that SQL code inside Stored Programs and Views may be so complex that parsing for the database name and stripping it is not safe. With this release we have stopped this ’stripping’ and Stored Programs and Views will be dumped by SQLyog identically to what ‘mysqldump’ does.

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

Comments(0)

Changes (as compared to 8.15 beta) include:

Bug Fixes:
* Copy database/table from a 3.x or 4.0 server to a more recent server failed  with column names containing special characters.
* If a sqlyog.ini files exists in installation folder it should be copied to ‘AppData’ folder. This is required for upgrading from versions before 6.06.  However with latest releases an empty file was created in ‘AppData’.
* The ‘Import External Data Tool’ could truncate strings when importing data from a 4D database. It is actually a bug in the 4D ODBC driver but we found a workaround.
* SSL-connections failed if authentication keys were created with cipher option.
* SQL-exports generated INSERTS for MERGE and FEDERATED tables.
* In INFO-tab/text-mode we will now not highlight ’string literals’. A comment with an odd number of quotes would make following lines display with ’string literal’ highlighting/coloring.
* When connected with SSH-tunelling to a Windows machine with Cygwin SSHD the bash.exe process created for each connection did not close again.
* CREATE TABLE .. advanced options did not set some create-options to ‘default’

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

Comments(0)

Changes (as compared to 8.14) include:

Features:
* Added an option to execute SHOW WARNINGS automatically if the ‘warning-count’ is not 0.  The output will appear in MESSAGES tab.  Note: this is not implemented for HTTP-tunnelling.
* Improved the memory handling in GRIDS with BLOB/TEXT columns. This fixes some slugginess when scrolling a GRID containing such data.

Bug Fixes:
* A dump containing VIEWs created on an early 5.0-server could fail to restore on recent servers. The  underlying reason is a bug with the ‘default’ column in the output of SHOW FULL FIELDS on the early 5.0 servers.  But we can aviod using this information and this is what we did now.

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

Comments(2)