SQLyog MySQL GUI 8.2 introduces Data-type optimizer and licensing changes

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

Join the newsletter

13 Comments

Add yours
  1. 2
    James Dempster

    I’m pretty sure you used to have a Pro version. Which was then removed.

    I’d paid for the previous Pro version because I didn’t want all the enhanced features, and I didn’t want the nag screen.

    Am I expected to pay again now that I want the bug fixes? Or do I have to put up with the nag screen?

    • 3
      Chirag

      James,

      Yes, we had a Pro version, ‘Pro 5’ to be precise. It was priced at $9 & had *only* the features of Community edition minus nag screens. The current offering, SQLyog Professional offers more. Please check this comparison sheet.

      To conclude, it was not the discontinuation of the Pro 5 version that had left you with out access to latest releases but the expiry of maintenance period. As blog won’t be the right medium to discuss sales related things, I’d request you to contact us at http://webyog.com/support & we’ll be happy to assist you in extending the maintenance period.

      Regards,
      Chirag

  2. 5
    sean

    Christmas present?
    I had QueryProfiler in Enterprise – now it is taken away.

    Never a great idea to charge people the same and give them less.

  3. 6
    Chirag

    Sean,

    Please note that all the SQLyog Enterprise customers are upgraded to SQLyog Ultimate free-of-cost. So, if you owned a copy of SQLyog Enterprise before, you still get QueryProfiler & as a bonus Data-type optimizer.

    Regards,
    Chirag

  4. 7
    Richard Raymond

    I just received a 12/13/09 email from you folks that included the following information:

    “Note for SQLyog Enterprise customers: There has been a change in licensing policy. All SQLyog Enterprise customers have been upgraded to SQLyog Ultimate free-of-cost. Refer this blog post for more details.”

    The referred blog said, “We have also migrated all existing SQLyog Enterprise customers to SQLyog Ultimate.”

    What does that mean for people like me who are not current? As an example, I have the SQLyog Enterprise edition, but version 8.04. If I am, in fact being upgraded to “Ultimate” how do I avail myself of this opportunity?

    Thanks,
    Dick Raymond

  5. 8
    peter_laursen

    *Every* customer who purchased SQLyog Enterprise before December 5th has been upgraded to SQLyog Ultimate. It does not matter if the free upgrade period has expired for user or not. Also user who purchased SQLyog Enterprise 4 years ago are now registered with SQLyog Ultimate and will be able to upgrade to latest Ultimate at discounted upgrade price.

    Users that want to prolong the free upgrade period can login to our Customer Portal (http://www.webyog.com/CustomerArea). For purchases where free upgrades have expired a link to upgrade will display. Also users will (unless they deselected this option) be notified about expiry by mail.

  6. 10
    Michael Brandon

    Please delete the last comment!
    You have not fixed the bug.

    When going from ssh to ssh, it treats the target as if its the source, so it syncs source to source and so finds no need to update anything! That is why it was so fast.

    I am now back to using ssh to http tunneling.

    PLEASE get this fixed asap!!!

  7. 11
    peter_laursen

    @Michael – I believe that this happens because you use the same local port setting for two SSH connections. No program can see *where the tunnel leads* (SSH does not expose that) – it can only see *the local port used*. So if one tunnel is open using one local port and another tunnel is next opened using same port it will connect the the same server as the first tunnel does. It always was user’s responsibility to ensure that local port setting for multiple connections did not conflict (exactly like when using PLINK from a command window)

    However we will release 8.21 soon (probably tomorrow – Friday) where the local port will be ‘picked’ automatically by SQLyog/SJA in cooperation with the OS socket layer at runtime. This will ensure that multiple SQLyog connections/instances and/or other programs using SSH will not collide.

    If you want to discuss more about this before or after 8.21 release (if I misunderstood for instance) please create a support ticket or post in our Forums.

  8. 12
    peter_laursen

    I will also add that it could happen that a PLINK instance was kept running in rare situations (like a SQLyog/SJA crash for instance or if user killed the SQLyog process (and not the ‘process tree’) from Task Manager). Connecting to same local port as used by such orphaned PLINK instance could result in same situation: connecting to an unexpected server.

    Should this happen with 8.21+ it will not be a problem as the local port used by the running/orphaned PLINK instance will not be ‘picked’, as the OS socket layer will not return that particular port as a free port to SQLyog/SJA and it will not be used again as long as that PLINK instance is running.

    But you are right that we should have fixed it before. It is not difficult actually .. we basically just need to specify ‘port 0’ for the connection and the OS will return a free port. Indeed not all users have much idea of the meaning of the local port setting used for SSH-tunnelling.

    Accordingly with 8.21 there will no option (as there will be no need) for user to select a local port.

+ Leave a Comment