We are pleased to announce the release of SQLyog – MySQL GUI 8.6 GA. This release adds functionalities requested by users for some time, and fixes a number of bugs. Most important enhancements:

User management has been updated with a brand-new interface, has been completely rewritten and also now fully communicates with the MySQL server the recommended way using GRANT and REVOKE syntax. We believe that with this release we have provided the best available ever GUI for MySQL User Management.

For users that prefer to work in a spreadsheet-like interface when filtering and sorting data the options to do this have been enhanced: There is now a ‘custom filter’ option to be used when filtering on a value that does not exist in the result set displayed

Hi,

We are delighted to unveil MONyog 4.0 — a major new release. Listed below are overviews of some of the major features.

Tracking changes to your MySQL configuration

Maintaining server configuration and tracking changes to it plays a vital role in the maintenance of MySQL servers. DBAs may be responsible for hundreds of servers and keeping an eye on the configuration settings for all of them could be difficult to say the least. With MONyog 4.0 now you can compare global MySQL configuration of multiple servers side-by-side, with all changes highlighted so that differences are visually discernible at a glance. Wondering why server A isn’t performing as well as server B when they share the exact same load? The answer could lie in the configuration files!

What’s more is that

Important note: Please note that if you have installed a MONyog 4.0 (beta) release you cannot install this one unless first completely removing the 4.0 installation including the complete MONyog data folder.

Changes (as compared to 3.77) include:

Bug Fixes:
* Monitors/Advisors on InnoDB Deadlocks were truncating the output message and hence in some cases, users were unable to view both queries involved in the deadlock. This has been changed such that the first 2048 characters of both queries are displayed.
* On Windows 7 systems changes to MONyog’s .INI file from external programs had no effect upon restart (as Windows reverted the changes). Now throughout MONyog’s lifetime the .INI file will be locked so that a user may only edit the file manually when MONyog is not running (but

Hi,

We are pleased to announce the release of SQLyog – MySQL GUI 8.5 GA. Below are some pointers:

• As the title suggests this release comes with tabbed interface for different connections. We need not have to emphasize the usability of a tabbed interface vs. a windowed one. All web browsers have already demonstrated it to us. Now in SQLyog, you can switch between different connections in a snap! We didn’t forget to add keyboard shortcuts to jump from one tab to other. Most – if not all – shortcuts for tabs of a standard web browser would work with SQLyog. Multi-coloring of connection tabs & object browser pane adds to the ease of use. Chances of one executing queries in one server than the other by mistake would be rare as the brain would easily grasp the connection by it’s color. Demoed below is

Changes (as compared to 3.73) include the bug fixes:

* Log analysis could use high CPU if the option to replace literals with a placeholder was not selected and the literal string ‘ “‘ (space + doublequote) occured in the log file.
* CSV-export from Query Analyzer only exported 200 rows (the same number as displayed in the browser view). Now CSV-export will export all rows. Also the UI makes it now clear that the browser displays the 200 uppermost rows according to current sort criteria.
* An error message regarding an integer overflow could occur in Monitor/Advisors page for some values. The SQLite datatype used could be too short for some specific data.
* Login to MONyog could fail if MONyog was running behind a proxy.

Downloads:

Changes (as compared to 3.72) include:

* If SHOW ENGINE INNODB STATUS returned an error that was not privilege-related, MONyog reported MySQL as non-available.  That could happen for instance if MySQL was started with –skip-innodb option. This bug was introduced in 3.71 with the support for InnoDB deadlock detection.
* A bug in the MONyog startup script could on Linux have the result that MONyog was still reported as running if it had been killed or had crashed.

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

Changes (as compared to 8.22) include:

Features:
* Added an option to define a ‘color code’ for a connection. The color will be used as background color in the Object Browser.
* A Query Builder session can now be saved and resumed.
* In Query Builder a table alias can be defined for any table by double-clicking the title bar of the table symbol.
* In RESULT tab results can now be retrieved page-wise. This is ON as default with this build with a defined LIMIT of 1000 rows. For a specific query user can change and for this specific query the setting is persistent across sessions. Also read ‘miscellaneous’ paragraph below.
* Added a context menu to Query Builder canvas.

Bug Fixes:
* Deleting a user would leave non-global privileges orphaned in the ‘mysql’

Changes (as compared to 3.71) include:

Features:
* The number of builds for Linux has been increased to the double number of what it was before.  In addition to the builds based on glibc version 2.3 we now distribute builds based on glibc 2.5.  Also we add builds for use with even older glibc 2.3 based Linux that what we had before. There are now builds based on both glibc-2.3.2  and 2.3.4 (the one based on 2.3.4 is the one we had before). We had a few  reports of random crashes (typically occurring up to a few times per week) occurring on recent 64 bit CentOS servers and in one case also a RHEL5.  The glibc 2.5-based build fixes this. Although we only had such reports on 64 bit Linux of  ‘Red Hat Family’ we also included 64 bit tar.gz for all Linux platforms and 32 bit RPM builds.  The general

Changes (as compared to 3.7) include:

Features:
* Added a monitor for InnoDB deadlocks (as exposed by SHOW ENGINE INNODB STATUS -statement).
* In case of a program crash on Linux, MONyog will save a core dump like the Windows version already does.  The dump is saved in ../MONyog/bin folder.

Bug Fixes:
* EXPLAIN from Processlist page could fail with syntax error due to a missing SPACE character in the statement.

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

MONyog MySQL Monitor 3.7  Has Been Released.

From MONyog 3.7 we have introduced 3 editions of the commercial version of MONyog. When we had first released MONyog 2 years back, it was already an almost complete tool for monitoring MySQL servers based on what the MySQL server exposes on SHOW statements.  Since then we have added features that are not basic server monitoring features in the strict sense but additional or supplementing features.  Most important the Query Analyzer was added around one year ago.

Multi-user authentication is a long standing request from customers belonging to large organizations – or just having the need for monitoring lots of MySQL servers. There may be multiple server administrators. There may be development/test servers that the developers of that

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

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.

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

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 now yum (RPM) or apt-get (DEB) MariaDB 5.1.39, courtesy of OurDelta and in close cooperation with Monty Program Ab. Simply follow the info on the CentOS, Debian or Ubuntu pages.

(note: give the mirrors some hours to sync up)

Quick overview

• See the Release Notes for relevant bugfixes.
• Drop-in replacement for stock MySQL 5.0 or 5.1 (If you’re coming from stock MySQL, see the MariaDB extras/differences overview).
• If you are upgrading from 5.0, please review the

MySQL 5.0.87-d10 OurDelta builds are now available (32 and 64-bit):

• Debian: Etch (4), Lenny (5)
• Ubuntu: Hardy (8.04), Intrepid (8.10), Jaunty (9.04), Karmic (9.10)
• RHEL/CentOS: 4, 5
• Binary tarballs: generic Linux, built on Ubuntu Hardy

You can now apt-get your way to MariaDB 5.1, courtesy of OurDelta and in close cooperation with Monty Program Ab. To get started, simple follow the info on the Debian and Ubuntu pages.

Quick overview

• For MariaDB we use different repository directories to ensure that you can’t accidentally upgrade or revert major versions without you explicitly choosing to do so.
• At this point we have Ubuntu Hardy, Intrepid, Jaunty and Karmic for you, as well as Debian 4 (Lenny). Etch (Debian 4) is waiting on a small fix (thanks to Antony Curtis for helping with that).
• The package names start with mariadb*,

These are now available for download from

• Binaries: http://master.ourdelta.org/bin/
  32 and 64-bit Linux tarballs
  32 and 64-bit OSX tarballs and DMGs
  
• Source tarball: http://master.ourdelta.org/src/

For the GRAPH Engine documentation, see http://openquery.com/graph/doc. It’s not another general purpose engine, it’s a computation engine. Different beast altogether, but darn useful!

Since it’s new code, it’s only in the -Sail patchset (bleeding edge).

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.

Hi,

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

Error Log Monitoring

Monitoring the MySQL error log is absolutely critical for any MySQL DBA. Ignore the error log at your own peril! Many of our customers wanted an out-of-the-box solution for monitoring the error log. With the latest release, MONyog becomes the first MySQL Monitoring Tool to monitor the MySQL Error logs. MONyog can optionally send notifications over SMTP or SNMP for MySQL error log events that require attention.

As usual, none of the features of MONyog require you to install agents or additional software on hosts running MySQL.

Changes (as compared to 8.12) include:

Features:
* SQLyog can be started with a ‘-dir’ switch like “SQLyogENT -dir somefolder”. This -dir switch specifies where SQLyog will look for the sqlyog.ini file and where all writable files will be saved. This was mainly implemented for users that want to have all SQLyog-related files on a removable drive or some kind of encrypted storage. Note that if you use the setting in ‘preferences’ to store TAGS file some specific place the ‘preferences’ setting will still have effect, also if the -dir switch is used.
* Improved/rearranged the GRIDS in Data Sync and Import External Data wizards.
* SJA mail functionality now supports SSL/TLS encryption. This applies to SJA for Linux and SJA for Windows running on Windows, but not  SJA for Windows running on Wine, as we did

Important note when upgrading from versions before 3.1:
* MONyog now requires a registration code.
* Do not forget to replace the MONyog.lua script if you use the Query Analyzer with proxy-based sniffing.
* RPM users must uninstall pre-3.1 versions before installing this one.
Please read 3.1 release notes for details.

Changes as compared to 3.11 include:

Features:
* All charts displayed by MONyog can now be exported as PDF/JPG/PNG (from chart context menu).
* Query Analyzer will now sort in descending order as default first time (before it was ascending).

Bug fixes:
* Validation of connection details was not proper when saving.
* In Query Analyzer options that do not

One of most loved feature of SQLyog is the snappy and responsive user interface. Many of our users and customers prefer SQLyog over other tools because of this particular reason.

One reason for the zippy interface could be that SQLyog is entirely developed in C/C++, which tends to be faster than other languages when it comes to raw speed. I don’t want to start a flame war here, but our customers seem to like this fact. Using C/C++ allows us to use the native MySQL C client libraries that gives the best performance as compared to other ways of communicating with MySQL. Using C/C++ also ensures that there are no external dependencies on any bulky frameworks and the download file is relatively small.

Although using a language that complies directly to machine instructions helps a lot, but true speed comes from better algorithms. A similar analogy in the

Hi,

We will be present at MySQL Conference & Expo, 2009. If you are around Silicon Valley, don’t forget to meet the team behind your favorite MySQL tools at Booth #317. We are happy to offer a flat 20% discount on all purchases made during this month. Use the coupon code: uc2009 during the purchase.

Also, we are pleased to announce the release of MONyog 3.06.

Changes (as compared to 3.05) include:

Bug fixes:
* Installation on Windows could fail with a js32.dll-related error. Waiting a few seconds and ‘retry’ would solve this but now the error does not come.
* Fixed a ‘false alert’ related to settings for temporary tables (the error occurred because of comparing an integer with a non-integer).

Changes (as compared to 8.03) include:

Features:
* Crash dumps with no information (zero-size) will now be deleted automatically.
* When saving/copying from the editor the LETTERCASE modfications for keywords and functions will now be preserved.
* Selecting a ‘child’ object for a table (columns and indexes) will now refresh the DATA tab if DATA tab is open. Before only selecting the table object itself did. Also the table information is now available in OBJECTS tab when a column or index is selected.
* Now also a ‘key’ icon is used for identifying the Primary Key in an Object Browser ‘Indexes’ folder,
* When a GRID cell is only partly visible, doubleclicking it will move the grid position so that cell/row will become visible (before it worked like that with singleclick - we changed to doubleclick as

Peter has done the prep work for building on Lenny, see our Debian page for info on how to configure apt for easy updating (Lenny comes with 5.0.51).