SQLyog MySQL GUI 11.52 Released

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

    * ‘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.


    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:

    * 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.

    * 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.


    SQLyog MySQL GUI 11.51 Released

  • peter_laursen
  • June 12th, 2014
  • Releases, SQLyog
  • Changes (as compared to 11.5) include:

    * Query Builder and Schema Designer tabs are now handled by ‘session restore’ exactly the way that Query tabs were in 11.5.

    Bug fixes:
    * In a multimonitor setup SQLyog was always opening in the primary monitor if closed in maximized state.
    * In Schema Sync altering an Event could generate an incorrect query.
    * Recent files were not displayed in file menu.  This bug was introduced in version 11.5.
    * ‘sesson restore’ would not always open connection tabs in same order as was the case when program was closed.  This happened if user had re-organized the tab-order manually.
    * Saved SQL files were not being marked as dirty when edited after it was restored by ‘sesson restore’.
    * When the content of an editor tab had just been saved as a file before closing the program, ‘session restore’ would sometimes not save and restore that particular tab.
    * If SQLyog was closed with no connections open, ‘session restore ‘ would still restore the last connection that was open.

    * Upgraded the linked OpenSSL library to version1.0.1h (OpenSSL is used for SSL-connections – not for SSH tunnel).


    MONyog MySQL Monitor 6.02 Has Been Released

  • peter_laursen
  • June 12th, 2014
  • MONyog, Releases
  • MONyog MySQL Monitor 6.01 Has Been Released

  • peter_laursen
  • June 10th, 2014
  • MONyog, Releases
  • Changes (as compared to 6.0) include:

    * Cleaned up the User Interface in Real-Time page. This includes removing the option to restore saved sessions for ‘all selected servers’. Saved sessions for individual servers can still be restored.
    * OpenSSL is updated to version 1.0.1h in all packages distributed.


    MONyog MySQL Monitor 6.0 Has Been Released

  • peter_laursen
  • June 3rd, 2014
  • MONyog, MySQL, Releases
  • Changes (as compared to 5.72) include:

    * The MONyog API is enhanced with more options to manage servers registered in MONyog. Options now include calls to add/edit/remove servers. Refer documentation for full details.
    * MONyog now supports Query analysis using Performance Schema tables (events_statements_summary_by_digest and events_statements_history_long tables). This feature is supported only for MySQL 5.6.14 and MariaDB 10.0 and above.
    * Explain plan is available in Query analyzer for Slow_log table based logging and Processlist sniffer.
    * An example query is now shown in detailed query view in Query analyzer if queries replaced with literals is selected.
    * MONyog now has a configurable option to define the max. query length displayed.  Beyond this MONyog will truncate the query. The setting has effect for Query Analyzer, Real-time and Way Back Machine interfaces. Default is now 10000 characters and maximum setting is 64000 characters. However please note that this does not apply when Performance_Schema is used with the Query Analyzer as P_S itself truncates.  For details please see the note at the bottom.

    Bug Fixes:
    * Explain option was not available in locked and locking queries for Real-Time sessions.
    * In some rare case MONyog logged SQLite errors while running Real-Time sessions.
    * MONyog could crash when connecting using a ‘Named Pipe’ on Windows. Actually we never promised support for Named Pipes.  But we should not crash, of course, and it works with Named Pipes now.
    * When monitoring MySQL v5.6 with replication using GTIDs (global transaction IDs), MONyog reported false notification alert for the ‘gtid_purged’ variable, when notifications for change in server configuration was enabled. This particular variable  was overlooked in 5.72 where there was a similar fix.
    * Yet another fix for a LDAP group authentication issue.
    * Query literals with hex values were not replaced with ‘?’ in Query analyzer.
    * When using SSH-tunnel, connections created by the CSO (Custom SQL Object) feature were not always closed properly, and the MySQL error log as well as ‘aborted_clients’ status variable would record aborted connectons.

    * When GTID’s (Global Transaction ID’s) were used with replication, MONyog’s replication page would display a lot of information about changing GTIDs.  This is now hidden in the primary interface, but can still be displayed in detailed view.
    * MONyog now displays the binary version on commandline when the command switch –version (or -v) is used.

    An additional comment on using the Query Analyzer with P_S:
    * Note that Performance_Schema truncates queries after 1024 characters and always replaces literals with a wildcard (in other words: P_S contains a summary/an aggregation only). So query listing not replacing literals is not possible with this option. And finally also observe that no other tool (or user) should be writing (including deleting or truncating) to events_statements_summary_by_digest and events_statements_history_long tables if this option is used as there is only one of each table for all users (it is not a temporary table or a materialized view or similar private for the user). This is a design limitation with the tables in P_S as such and not a MONyog issue. MONyog itself may (optionally) truncate the P_S tables when they reach 80% of their capacity (and thus MONyog could have impact on other tools or users using the same tables). This truncation is disabled as default, but you may need to enable it if the capacity of the tables is set too low to record all queries occuring.


    SQLyog – Introducing Session Restore

  • Chetan
  • May 21st, 2014
  • MySQL, News, Releases, SQLyog
  • Ever had this nightmare of your system crashing, or you accidentally closing SQLyog and losing all your open tabs and queries? Don’t worry, we have you covered!

    Introducing Session Restore. You can now restore your previous session along with all queries and history tab the way you left it. Here’s a quick video:

    Session Restore is available for all SQLyog users. Existing customers can download the latest build from Customer Portal. To evaluate SQLyog, please download a 30-day trial.

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

    Team SQLyog

    SQLyog MySQL GUI 11.5 Released

  • peter_laursen
  • May 19th, 2014
  • Releases, SQLyog
  • Changes (as compared to 11.42) include:

    * ‘session restore’ now saves and restores content of open Query tabs and History tabs. As regards History tab please observe that its content will not be allowed to grow beyond 50,000 queries. When the 50,001st query is added the 1st is removed at runtime and so on. This is not something new – it was always like that. However with the addition of History tab to ‘session restore’ this is now even more relevant as using ‘session restore’ for long time (months, years) with the same connection could cause the History tab content to grow beyond reasonable limits (possibly affecting performance of ‘session restore’ and consuming excessive memory) if History was allowed to grow without limits. Finally please observe that internal storage format for saved sessions have changed between the 5.0 beta and this GA. For this reason sessions saved by the beta will not be opened by this GA release. We are sorry for this inconvenience caused to our beta users.
    * As a consequence of above user is not prompted to save open Query tabs when the program is closed and ‘session restore’ is enabled. User is still prompted when closing a single connection tab or a single query tab..
    * With ‘session restore’ enabled, session is now also saved automatically in the background every 10 seconds.
    * A Query tab can be renamed (from the context menu of the tab itself). ‘session restore’ will open the tab with the user-defined name.
    * Added the HTTP content-type ‘application/xml’ as an option for HTTP tunnel.
    * Import external data will now create  tables with the database collation of the database imported to, provided that database charset is utf8. Note that we cannot do this if database charset is not uft8 as imported tables are always created as utf8 and comparable collations do not always exist for unicode and non-unicode charsets in MySQL.

    Bug fixes:
    * Fixed a crash when executing a single bracket ( “(” ) as a statement.
    * Import External Data could fail when creating indexes on imported TEXT columns as the tool did not specify the mandatory index prefix length.

    * The HTTP-tunneler has been updated with this release and users making use of HTTP tunnel must update the tunneler on their MySQL host.  The previous tunneler – released with SQLyog 8.8 more than 3 years ago – used the function ‘set_magic_quotes_runtime()’ that has been deprecated for some time in recent PHP versions. Till now we have suppressed any errors resulting from this, but this is a permanent solution.


    Suddenly MyISAM became transaction-aware.

  • peter_laursen
  • May 12th, 2014
  • MySQL
  • DROP DATABASE IF EXISTS `gtid_test`;
    CREATE DATABASE `gtid_test`;
    USE `gtid_test`;

    CREATE TABLE `tab1` (
    `a` INT

    CREATE TABLE `tab2` (
    `b` INT

    SET autocommit=0;

    INSERT INTO `tab1` VALUES (1);
    INSERT INTO `tab2` VALUES (1);

    UPDATE `tab1` SET `a` = 5 WHERE `a` = 1;

    – Error Code: 1785
    — When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.

    This happens with MySQL 5.6 GTIDs (Global Transaction IDs) enabled and it is documented here: “updates to tables using nontransactional storage engines such as MyISAM cannot be made in the same statement or transaction as updates to tables using transactional storage engines such as InnoDB.”

    To reproduce the above test case you need the options –log-bin, –log-slave-updates, –gtid_mode=ON and –enforce_gtid_consistency=ON

    If you have some tool doing UPDATES to multiple tables in a single transaction and if you have schemas using a mix of InnoDB and MyISAM tables the tool will fail.

    This is just a (one more!) reminder that upgrading to MySQL 5.6 is *a major thing to do* if you intend to use new features added. Be careful to test on a staging environment that all tools and scripts, that you need for your daily survival, still work as expected.

    GTIDs in MariaDB 10.0 are not affected and I find the MariaDB GTID implementation superior. MyISAM always was ‘transaction-agnostic’. The storage engine as such still probably is (the new restriction must have been implemented in the server layer and not the storage engine layer). But Oracle managed (a very bad way IMO) to introduce a GTID implementation that kills a major MyISAM feature (its ‘transaction-agnosticity’) and introduced potential risks when using legacy tools and scripts.

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