Blog

SQLyog MySQL GUI 12.03 Released

  • peter_laursen
  • November 25th, 2014
  • Releases, SQLyog
  • Important note: With the 12.0 release we changed registration keys. The new key is available for registered users from our Customer Portal. Users upgrading from a pre-12.0 version should have the new key available before installing. Until SQLyog 12.x is registered with the proper key, it will only display the registration dialog.

    Changes (as compared to 12.02) include:

    Features:
    * Data Sync will now run in a single transaction using REPEATABLE READ transaction isolation mode on source.

    Bug fixes:
    * The fix in 12.02 related to (DATE)TIME datatypes using fractional seconds was not complete.  In some cases Schema Sync could still add quotes where it should not.
    If the target for Schema sync differed from the currently selected database in the main program dialog, inconsistent database name could display in some cases. A consequence was that SQLyog mistook what was the current active database and SQLyog GUI would keep showing incorrect active database afterwards, until it was changed.
    * In Schema Sync some items could incorrectly be blue-colored and redundant statements would be generated for those affected.

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

    MONyog MySQL Monitor 6.21 Has Been Released

  • peter_laursen
  • November 11th, 2014
  • MONyog, Releases
  • Important note: With the 6.1 release we have changed registration keys. The new key is available for registered users from our Customer Portal. Users upgrading from a pre-6.1 version should have the new key available before installing. Until MONyog is registered with the new key, it will not be collecting data from your servers.

    Changes (as compared to 6.2) include:

    Bug Fixes:
    * In Monitors page,  the small trend charts (in current and delta timeframes) were not displayed for some monitors.
    * Charts were not displayed in Monitors page .. history/trend if data series contained “N/A” values.
    * MONyog was not able to connect to MySQL server if password contained a leading or a trailing empty space.
    * In rare cases, some server(s) could stop showing in the UI after MONyog restart.
    * Fixed a rare irresponsiveness (“hang”) occuring when starting data collection after editing server details.
    * The option to stop the current running saved session was not available in Real-Time in some cases.
    * A number of minor GUI fixes.

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

    SQLyog MySQL GUI 12.02 Released

  • peter_laursen
  • October 23rd, 2014
  • Releases, SQLyog
  • Important note: With the 12.0 release we changed registration keys. The new key is available for registered users from our Customer Portal. Users upgrading from a pre-12.0 version should have the new key available before installing. Until SQLyog 12.x is registered with the proper key, it will only display the registration dialog.

    Changes (as compared to 12.01) include:

    Features:
    * Exports to CSV and Excel XML can now optionally include BOMs (Byte Order Marks) or not. Before this, BOMs were not an option. Some Windows programs will require BOMs in order to recognize the encoding as UTF8.

    Bug fixes:
    * The fix in 11.3 for databases named identically except for lettercase would fail in some cases.  One such case was if database default charset was utf8mb4.
    * The checkbox in CREATE/ALTER TABLE dialog for setting ON UPDATE CURRENT_TIMESTAMP failed for TIMESTAMP and DATETIME columns using fractional seconds. MySQL 5.6+ from Oracle was affected. MariaDB 10 was not.
    * Also in in CREATE/ALTER TABLE dialog, for TIMESTAMP and DATETIME columns using fractional seconds a default specified as CURRENT_TIMESTAMP(n) (with ‘n’ being a number in the range 1..6)  was incorrectly ‘quoted’ and thus failed.

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

    MONyog MySQL Monitor 6.2 Has Been Released

  • peter_laursen
  • October 10th, 2014
  • MONyog, Releases
  • Important note: With the 6.1 release we have changed registration keys. The new key is available for registered users from our Customer Portal. Users upgrading from a pre-6.1 version should have the new key available before installing. Until MONyog is registered with the new key, it will not be collecting data from your servers.

    Features:
    * The Real-Time interface in MONyog has been completey rewritten. In addition to a more consistent/intuitive GUI it is now able to collect data from multiple MySQL servers simultaneously (one collection of Real-Time data per server). Once data collection for a server has been started it will continue untill stopped by user, also if browser connection is closed in between. The sole exception is that  Real-Time data collection for a server  will stop after 3 days if no activity has happened inside the particular Real-Time session.
    Added an option to set line terminator for csv reports.

    Bug Fixes:
    * Renaming a registered server to a new name already in use would not raise any error. Instead data for the affected server would not display anymore.
    * In rare cases clicking ‘test SSH settings’ -button would not display any response.
    * When registering a “Postmaster Enterprise SMTP server” in MONyog, mail notifications failed to be sent.
    * ‘diagnostics report’ failed to download when MONyog was running behind a HTTP (‘reverse’) proxy server.
    Clicking on editing SMTP settings from server registration page did not redirect to tools page and thus editing was not possible from here. The problem was alone a problem with the particular hyperlink.  From the tools page everyting worked as expected.
    * The following gtid-related variables in MariaDB 10 could trigger false notifications: gtid_binlog_pos, gtid_binlog_state, gtid_current_pos, gtid_slave_pos and last_gtid.
    * MONyog failed to establish SSH connection to Linux servers using the “OpenSSH-HPN” SSH implementation.
    * When an identifier contained digits (such as ‘abc12′, ‘ab12ab’ etc.), the Query Analyzer, the WayBack Machine and Real-TIme interface would consider these digits literals, and they would be replaced with ‘?’.
    * If MONyog did not have sufficient privileges to the MONyog /Data folder, adding a new server could crash MONyog.
    * In rare cases replication page could fail to render properly.

    Miscellaneous
    Dashboard page was renamed to ‘Charts’.
    The tab-order of MONyog’s interface has been rearranged.
    *
    Also note that ‘WayBack  machine’ interface is still available (unlike what was the case with the 6.2 beta, where we experimentally removed it)

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

    MONyog MySQL Monitor 6.2 beta1 Has Been Released

  • peter_laursen
  • September 5th, 2014
  • MONyog, Releases
  • Important note: With the 6.1 release we have changed registration keys. The new key is available for registered users from our Customer Portal. Users upgrading from a pre-6.1 version should have the new key available before installing. Until MONyog is registered with the new key, it will not be collecting data from your servers.

    Changes (as compared to 6.1) include:

    Features:
    * The Real-Time interface in MONyog has been completey rewritten. In addition to a more consistent/intuitive GUI it is now able to collect data from multiple MySQL servers simultaneously (one collection of Real-Time data per server). A detail to note is that  Real-Time data collection for a server  will stop after 3 days if no activity has happened inside the particular Real-Time session. 

    Bug Fixes:
    * Renaming a registered server to a new name already in use would not raise any error. Instead data for the affected server would not display anymore.
    * In rare cases clicking ‘test SSH settings’ -button would not display any response.
    * When registering a “Postmaster Enterprise SMTP server” in MONyog, mail notifications failed to be sent.
    * ‘diagnostics report’ failed to download when MONyog was running behind a HTTP (‘reverse’) proxy server.
    Clicking on editing SMTP settings from server registration page did not redirect to tools page and thus editing was not possible from here. The problem was alone a problem with the particular hyperlink.  From the tools page everyting worked as expected.

    Miscellaneous.
    *
    Dashboard page was renamed to ‘Charts’.
    *
    The tab-order of MONyog’s interface has been rearranged.
    *
    ‘WayBack  machine’ interface has been removed. It is now possible to use Real-Time Interface for collecting historical activity.

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

    SQLyog MySQL GUI 12.01 Released

  • peter_laursen
  • August 18th, 2014
  • Releases, SQLyog
  • Important note: With the 12.0 release we changed registration keys. The new key is available for registered users from our Customer Portal. Users upgrading from a pre-12.0 version should have the new key available before installing. Until SQLyog 12.x is registered with the proper key, it will only display the registration dialog .

    Changes (as compared to 12.0) include:

    Bug fixes:
    * Version 12.0 introduced a bug where the copy options from the icon bar did not function. Same functionalities from menu and context menu were not afffected.

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

    SQLyog MySQL GUI 12.0 Released

  • peter_laursen
  • August 7th, 2014
  • Releases, SQLyog
  • Important note: With this release we have changed registration keys. The new key is available for registered users from our Customer Portal. Please have the new key available before installing. Until SQLyog is registered with the new key, it will only display the registration dialog .

    Changes (as compared to 11.52) include:

    Features:
    * In addition to UTF8, exports to CSV and Excel XML can now be written with a number of non-unicode charsets/encodings. Note that in the SQLyog interface we identify those with their “MySQL name” and not what they may be termed in other contexts (‘latin1′ and not ‘ANSI/Western’ for instance).
    * The CREATE/ALTER TABLE dialog now has a column of checkboxes where the “ON UPDATE CURRENT_TIMESTAMP”-clause can be specified by user for TIMESTAMP columns – and also for DATETIME columns if the server connected to is 5.6+.
    * DATA and RESULT tabs can now be ‘unsorted’ from a selection in the context menu.  This is in particular useful if you have sorted on multiple columns . In this case ‘unsorting’ could be a little tricky.

    Miscellaneous:
    * The title bar now displays if SQLyog running is a 32 bit or 64 bit version.
    * Added the keyboard shortcut F4 for CREATE (table/view/stored procedure/stored function/trigger/events/index depending on current Object Browser selection).

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

    SQLyog MySQL GUI 11.52 Released

  • peter_laursen
  • July 18th, 2014
  • Releases, SQLyog
  • Changes (as compared to 11.51) include:

    Features:
    * ‘session restore’ will now also restore the current default database for every connection to what is was when the program was closed.
    * Added options to save and open session savepoints manually. The options are added to the file menu.  This is working independently of the automatic session restore feature. With this it is possible to have a number of session savepoints for different use cases saved to the system.
    * When one or more connections saved in a session savepoint failed to open, the connections were discarded. When the program was closed next time the automatic session savepoint would be overwritten, and all queries, schema designs and query designs belonging to affected connections would be lost.  Now, when a connection fails, a copy of the automatic session savepoint file will be created and user will be prompted to copy it for future use (using the new option to open a savepoint manually).
    * ‘copy database’ now has an option to create the target database.

    Bug fixes:
    * Wrong execution time could display in MESSAGES tab.

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

    Webinar – Monitoring MySQL and MariaDB databases with MONyog. Register now

  • Chetan
  • June 26th, 2014
  • MONyog, MySQL, News
  • Monitoring MySQL and MariaDB databases without a powerful tool like MONyog can be challenging. However, if you already use MONyog you might not be using it to it’s full potential. In this webinar, we will introduce you to the entire feature set of MONyog followed by a Q&A session.

    You’ll also be delighted to know that one lucky winner gets MONyog Ultimate worth $399 for free. So, make sure you book your spot.

    Date: Tuesday, July 8, 2014
    Time: 10:00 am PT
    Presenter: Rohit Nadhani (CEO, Webyog)

    Update: Congratulations to Vandana Sharma on winning a MONyog Ultimate license worth $399.

    MONyog MySQL Monitor 6.1 Has Been Released

  • peter_laursen
  • June 25th, 2014
  • MONyog, Releases
  • Important note: With this release we have changed registration keys. The new key is available for registered users from our Customer Portal. Please have the new key available before installing. Until MONyog is registered with the new key, it will not be collecting data from your servers.

    Changes (as compared to 6.02) include:

    Features:
    * Added more counters and advisors for MySQL 5.6 configuration.
    * Added an extensive set of counters for monitoring the TokuDB storage engine. The monitor groups for this are not visible as default, but can be enabled from the ´Customize’ interface.

    Bug Fixes:
    * Fixed a rare SQLite database corruption under very heavy load and with Custom SQL Objects enabled.
    * Changing refresh interval setting for Processlist page was not possible for non-admin users.

    Miscellaneous:
    * MONyog installed on the Amazon Cloud from the Amazon Machine Image (“AMI”) we provide as an option, will now start first time with the Amazon instance ID as the admin password and not an empty password as before. This change could take some days to propagate across the Amazon Cloud.

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

    Page 1 of 4312345...102030...Last »