Changes (as compared to 8.2) include:

Features:
* Now SJA will also send mail alert if job aborted due to MySQL error. Before it was only internal SJA error.
* The local port used by SSH-tunneling will now be selected automatically. This will avoid conflicts in case multiple programs use SSH. Also with Data Sync from command-line/scheduler it was possible to use same port for both connections what would effectively sync a server with itself.
* Caption for ‘Parse’ button in Notification Services Wizard was changed to make it clear that it will actually execute the statement(s) entered. There is no way to let the server parse a statement except for executing it.
* Connection windows for SSH connections will now list SSH host details in the title bar.
* Tooltips for an icon will now list the keyboard shortcut performing same action.
* The option to display ‘all’ versus a ‘LIMIT’ed set of rows in DATA tab is now table-specific and saved across sessions (note that – similar to the ‘column width persistence’ feature – connection parameters are not using for identifying a table; only the database name and the table name are).
* Objects in an Object Browser node is now sorted case-insensitive.

Bug Fixes:
* Continuously clicking the ‘Calculate’ button in Schema Optimizer in a fast manner could crash SQLyog.
* The keyword.db file (used by auto-complete and syntax highlighting) is now read only. Various validators for Windows7-compatibility would report that SQLyog wrote to “Program Files” folder at runtime (what it did not).
* When copying to clipboard an out of memory error could occur also when there was enough memory.
* The table menu will now indicate what storage engine is currently used for the table.
* Autocomplete and syntax highlighting did not recognize keywords archive, blackhole, federated, example, maria, pbxt, federatedx, falcon and mrg_myisam.
* Notifications Services/’Send Query to Email address’ option did not send a mail if an error occurred. Now a mail listing the error will be sent.
* We did not validate client-side if user specified a default value for an auto-increment column (what is invalid with MySQL).
* In DATA and RESULT tab the context menu was only working from GRID-cells. Now it also does from GRID headers and ‘whitespace’ in the tabs.
* Updating a ’TIMESTAMP on update CURRENT_TIMESTAMP’ had no effect (the particular column was not listed in the UPDATE-statement sent by SQLyog). This was a necessary restriction before 8.13 but since we – from 8.13 – only list columns that have actually been edited by user, we can now lift this restriction.
* Import External Data – TRIGGERS could fail to update a SQL Server (n)varchar if it contained an empty string.
* If user had selected to save SSH-password locally and later changed the password, the new password was not saved – unless clicking ’save’ button in connection manager interface.
* When importing an external script with no explicit SET NAMES on top, SET NAMES latin1 was executed by SQLyog. Now we won’t do this – and server default charset will have effect for the import in such case.
* Autocomplete did not handle identifiers with the ‘_’ character correctly what could result in too many matches when matching the database with a pattern in editor containing such character.
* Other small GUI fixes.

Miscellaneous:
* This release ships with an updated tunneler file for HTTP-tunneling. In the old tunneler file functions were used that are depreciated in PHP 5.3x.
* The ‘Objects’ menu was renamed to ‘Others’.

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

Comments(0)

Change (as compared to 8.2) include:

Features:
* Now SJA will also send mail alert if job aborted due to MySQL error. Before it was only internal SJA error.
* The local port used by SSH-tunneling will now be selected automatically. This will avoid conflicts in case multiple programs use SSH. Also with Data Sync from command-line/scheduler it was possible to use same port for both connections what would effectively sync a server with itself.
* Caption for ‘Parse’ button in Notification Services Wizard was changed to make it clear that it will actually execute the statement(s) entered. There is no way to let the server parse a statement except for executing it.
* Connection windows for SSH connections will now list SSH host details in the title bar.
* Tooltips for an icon will now list the keyboard shortcut performing same action.
* The option to display ‘all’ versus a ‘LIMIT’ed set of rows in DATA tab is now table-specific and saved across sessions (note that – similar to the ‘column width persistence’ feature -  connection parameters are not  using for identifying a table; only the database name and the table name are).

Bug Fixes:
* Continously clicking the ‘Calculate’ button in Schema Optimizer in a fast manner could crash SQLyog.
* The keyword.db file (used by auto-complete and syntax highlighting) is now read only. Various validators for Windows7-compatibility would report that SQLyog wrote to “Program Files” folder at runtime (what it did not).
* When copying to clipboard an out of memory error could occur also when there was enough memory.
* The table menu will now indicate what storage engine is currently used for the table.
* Auto-complete and syntax highlighting did not recognize keywords archive, blackhole, federated, example, maria, pbxt, federatedx, falcon and mrg_myisam.
* Notifications Services/’Send Query to Email address’ option did not send a mail if an error occurred. Now a mail listing the error will be sent.
* We did not validate client-side if user specified a default value for an auto-increment column (what is invalid with MySQL).
* In DATA and RESULT tab the context menu was only working from GRID-cells. Now it also does from GRID headers and ‘whitespace’ in the tabs.
* Updating a  ’TIMESTAMP on update CURRENT_TIMESTAMP’ had no effect (the particular column was not listed in the UPDATE-statement sent by SQLyog). This was a necessary restriction before 8.13 but since we – from 8.13 – only list columns that have actually been edited by user, we can now lift this restriction.
* Import External Data – TRIGGERS could fail to update a SQL Server (n)varchar if it contained an empty string.
* If user had selected to save SSH-password locally and later changed the password, the new password was not saved – unless clicking ’save’ button in connection manager interface.
* When importing an external script with no explicit SET NAMES on top, SET NAMES latin1 was executed by SQLyog.  Now we won’t do this – and server default charset will have effect for the import in such case.
* Other small GUI fixes.

Miscellaneous:
* This release ships with an updated tunneler file for HTTP-tunneling. In the old tunneler file functions were used that are depreciated in PHP 5.3x.
* The ‘Objects’ menu was renamed to ‘Others’.

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

Comments(0)

Changes (as compared to 3.62) include:

Features:
* You can now specify a comma-separated list of users to be ignored/excluded by notify and/or kill actions for long-running queries in ’query sniffer’ interface.
* Added a ‘diagnostic info’ icon to servers in ‘list of servers’ page. Clicking this will generate a report in plain text with the most basic information about the server.
* Added an option to stop/start data collection for a server in ‘list of servers’ page (without opening the detailed pages for this server).
* Enabling/disabling data collection from and/or alerting about all servers can be done from tools .. preferences .. maintenance.
* Enabling/disabling data collection from and/or alerting about specific servers can be done by calling the MONyog URL with parameters. This can be scripted and scheduled using any standard method available with the OS. Please refer to documentation for details.
* Mail alerts will now have a direct link to open MONyog login page.
* Added an option to customize colors used in Dashboard.
* If global wait_timeout setting for a server is lower than the sample interval we will now increase session wait_timeout setting in order to avoid the MONyog.log to grow with a “MySQL server has gone away” message for each data retrieval.

Bug Fixes:
* Fixed some issues with validation of user input. For specific data invalid and unusable input could be saved by MONyog. This includes 1) invalid separator between email addresses 2) Entering a decimal where an integer is required.
* SMTP return codes were neither logged nor were specific messages displayed to the user based on them.
* In history/trends an empty graph would display if server details were wrong. Now proper javascript errors are displayed.
* In connection details page for a server the previous/next links would hide with specific menu items selected.
* In History/Trends, warning message (”No data found in this range, try changing history range!”) didn’t show up for the time-frame in which server data collection was disabled.
* If Adobe Flash was not installed, the message to  “install the latest Adobe Flash Player” was displayed more than once.
* Small GUI improvements and fixes.

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:
* Auto-complete and syntax highlighting did not recognize keywords archive, blackhole, federated, example, maria, pbxt, federatedx, falcon and mrg_myisam.
* Notifications Services/’Send Query to Email address’ option did not send a mail if an error occurred. Now a mail listing the error will be sent.
* We did not validate client-side if user specified a default value for an auto-increment column.
* The automatic selection of local port to be used with SSH-tunnelling (as introduced with beta 1) did not work properly on Wine.
* In DATA and RESULT tab the context menu was only working from GRID-cells. Now it also does from GRID headers and ‘whitespace’ in the tabs.
* Other small GUI fixes.

Miscellaneous:
* Note that this beta 2 ships with the 8.2 documentation/help file unchanged (and thus a few screenshots are not up to date).
* This release ships with an updated tunneler file for HTTP-tunneling. In the old tunneler file functions were used that are depreciated in PHP 5.3x.
* The ‘Objects’ menu was renamed to ‘Others’

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

Comments(0)

Change  (as compared to 8.2) include:

Features:
* Now SJA will also send mail alert if job aborted due to MySQL error. Before it was only internal SJA error.
* The local port used by SSH-tunneling will now be selected automatically. This will avoid conflicts in case multiple programs use SSH. Also with Data Sync from command-line/scheduler it was possible to use same port for both connections what would effectively sync a server with itself.
* Caption for ‘Parse’ button in Notification Services Wizard was changed to make it clear that it will actually execute the statement(s) entered. There is no way to let the server parse a statement except for executing it.
* Connection windows for SSH connections will now list SSH host details in the title bar.
* Tooltips for an icon will now list the keyboard shortcut performing same action.

Bug Fixes:
* Continously clicking the ‘Calculate’ button in Schema Optimizer in a fast manner could crash SQLyog.
* The keyword.db file (used by auto-complete and syntax highlighting) is now read only. Various validators for Windows7-compatibility would report that SQLyog wrote to “Program Files” folder at runtime (what it did not).
* When copying to clipboard an out of memory error could occur also when there was enough memory.
* The table menu will now indicate what storage engine is currently used for the table.
* Other small GUI fixes

Miscellaneous:
* Note that this beta1 ships with the 8.2 documentation/help file unchanged (and thus a few screenshots are not up to date).

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

Comments(0)

Changes (as compared to 3.62) include:

Features:
* You can now specify a comma-separated list of users to be  ignored/excluded by notify and/or kill actions for long-running queries in  ’query sniffer’ interface.
* Added a ‘diagnostic report’ icon to servers in ‘list of servers’ page.  Clicking this will generate a report in plain text with the most basic information about the server.
* Added an option to stop/start data collection for a server in ‘list of servers’ page (without opening the detailed pages for this server).
* Enabling/disabling data collection from and/or alerting about all servers can be done from tools .. preferences .. maintenance.
* Enabling/disabling data collection from and/or alerting about specific servers can be done by calling the MONyog URL with parameters. This can be scripted and scheduled using any standard method available with the OS. Please refer to documentation for details.
* Mail alerts will now have a direct link to open MONyog login page.
* Added an option to customize colors used in Dashboard.

Bug Fixes:
* Fixed some issues with validation of user input. For specific data invalid and unusable input could be saved by MONyog. This includes 1) invalid separator between email addresses 2) Entering a decimal where an integer is required.
* SMTP return codes were neither logged nor were specific messages displayed to the user based on them.
* In history/trends an empty graph would display if server details were wrong.  Now proper javascript errors are displayed.
* In connection details page for a server the previous/next links would hide with specific menu items selected.
* Small GUI improvements and fixes.

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

Comments(0)

Changes (as compared to  3.61) include:

Bug fix:
* When using the option (introduced in 3.6) to alert for long-running queries from the Query Sniffer interface, such long-running query could raise multiple alerts.

Miscellaneous:
* Added ‘User and Host’ information for long running query alert.

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

Comments(0)

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)

Changes (as compared to 3.6) include.

Bug Fix:
* If notifications were enabled, program threads were not always closed properly what ultimately could lead to a program ‘hang’. This bug was introduced in 3.6.

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

Comments(0)

Hi,

We are pleased to announce MONyog 3.6 – a major new release. Listed below are the major features included in this release.

Real-time query monitoring and sniping

MONyog provides a whole bunch of tools for finding problem SQL (Slow Query Log, SHOW PROCESSLIST snapshots, MySQL Proxy, etc). These tools are great if you want to find problem SQL in an application and tune those queries. However, using these tools to find problem is almost always a post-mortem exercise. In certain situations you may want real-time notifications for long running queries. MONyog 3.6 gives you exactly that. MONyog can continuosly monitor queries in real-time and send notifications (on Mail or SNMP) for queries that take more than a specified amount of time to execute. You can also specify an option to kill such queries.

Better server management

Several of MONyog’s customers monitor hundreds of MySQL servers using a single instance of MONyog. Managing large number of servers has just gotten a whole lot easier. With tagging, you can categorize your servers into logical groups, and avoid clutter.

Many people had requested the option to add servers programatically. That was one of the primary motivations for documenting the entire MONyog schema. Some customers want to register hundreds of servers quickly without writing any code. For such situations, we introduced the ability to duplicate a connection with a single click. After duplicating a connection, most of the time you just need to change the MySQL IP or Port. You would probably want to retain all other settings.

Improved alerting system

Many users of MONyog have reported that they sometimes receive alerts for insignificant events. And, which is worse, because of this they tend to ignore important alerts! Some of the improvements in the alerting system are:

a) We have introduced the concept of “Delayed alert notifications”. It can now be defined that a problem must have existed for a number of sample intervals continuously (in a row) for an alert to be sent. A global setting for each server is available from GUI. For individual counters the global setting can be overridden by defining the RetryOverride (like ‘RetryOverride:3′) property of the (JavaScript) counter definition

b) You can also choose to be notified when MONyog detects that a problem, which existed previously, has been resolved.

I/O Monitoring for Linux servers

MONyog now provides several monitors on Linux I/O metrics.

Get notified on MySQL restart

We have also added an option to send alerts if server was restarted between two data retrievals. With managed hosting the MySQL server may be restarted automatically as part of routine maintenance or after a server crash. Knowing when this has occurred can be useful.

Lot of minor features and bug fixes

This release also contains many bug fixes, UI improvements and minor features. You can find the complete release notes in the ‘Version History’ section of MONyog’s Help, available online here.

MONyog customers can download the latest installers from Webyog’s Customer Portal.
To evaluate MONyog, please download the 30-day trials.

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

Regards,
Team MONyog

Comments(1)