SQLyog is a professional-grade GUI tool for the MySQL RDBMS.
SQLyog is available for the Windows operating system starting
from Windows XP/Windows 2003 to Windows 8/Server 2008 R2. It will
also work under Linux, Unix and Mac OS X using the Wine
environment. Moreover, a subset of SQLyog Enterprise/Ultimate
functionalities are available with the free SQLyog Job Agent
(SJA) for Linux as a native Linux utility. This makes it possible
to specify and test ‘scheduled jobs’ on a Windows environment and
port execution parameters seamlessly to a Linux environment.

Why Use a Database Administration Tool

Database administration tools provide a GUI/Web interface to
automate database tasks like querying tables, find and replace
operations, and any other task that you might want to run on a
database. With respect to MySQL, it offers the free MySQL Workbench.
Although it’s far more …

This maintenance release of SQLyog, MySQL GUI introduces a
new feature – REGEX search in Object Browser – and adds
a few bug fixes.

Changes as compared to MySQL GUI 12.4.1
include:

Important notice:

* The tunneler file for HTTP-tunnel has been updated
with this release and must be replaced on the server.
Earlier HTTP-tunnel required PCRE-support in the
server-side PHP-environment. Now it does not.

Features:

* Search function in Object Browser now supports regular
expressions.

Bug Fixes:

* Fixed a rare connection failure using SSH-tunnel to
specific BSD systems.
* Removed unnecessary virtual column check for older servers with
no support for this.
* Fixed a crash when a …

This maintenance release introduces a long requested feature –
HEX-dumping of binary data – and adds a number of
non-critical bug fixes.

Changes as compared to MySQL GUI 12.4
include:

Features:

* Added an option to HEX-dump binary data in Export as
SQL and in Scheduled Backup.
* In read-only mode FLUSH-statements can now be executed
from the GUI as well as editor, except for ‘FLUSH TABLE WITH READ
LOCK’ (as we don’t allow acquiring explicit LOCKS in
read-only mode).

Bug Fixes:

* On enabling HTTP, SSL or SSH checkbox in the connection
manager, the checkbox wasn’t redrawn automatically. The checkbox
were re-drawn only on hovering over them or switching to another
tab in the connection window
* In Table Diagnostics, clicking on Analyse executed same query …

This release introduces a new major feature – ‘read-only’
connections – as well as Kerberos authentication
support and a few bug fixes.

Changes as compared to MySQL GUI 12.3.3
include:

Features:

* Added an option for defining a connection as ‘read-only’.
There is a checkbox in the connection settings and when
checked the title bar will inform user about the ‘read-only’
state. In ‘read-only’ state statements that write cannot be
executed. For more details please see note at the bottom.
* Added support for the MariaDB auth_gssapi (Kerberos) plugin.
This plugin is available with the latest 3.0 (alpha)
Connector/C from MariaDB. But there seems to be a
huge popular demand for this already, and we have backported
it to the 2.3 connector version we use in SQLyog. Note that
support …

* Fixed an issue where Import External Data -jobs failed to
authenticate SMTP.
* The sja.log would record syntax errors on recent servers if
Scheduled Backup was running with ‘Flush Master’ option.
The generated backup file was OK. ‘Flush Master’ was deprecated
in MySQL 5.6 and replaced with ‘Reset Master’. We now
use ‘Reset Master’ with such servers.
* In email settings of Import External Data wizard it was
possible to leave the subject empty.
* When re-ordering columns, an ON UPDATE -clause could be lost in
specific cases.
* Fixed cases where index-level comments were not saved and …

* If an INIT_CONNECT setting in server configuration specified
SET AUTOCOMMIT = 0 and global AUTOCOMMIT was 1 (or non-existent
as in MySQL 4.1 and 5.0), the ‘transactions’ menu in SQLyog would
incorrectly display AUTOCOMMIT as 1 after connection.
* Same code change as above also fixes a crash that could occur
with 4.1 servers.
* Transactions support would fail to initialize with servers
running global ANSI mode. SQLyog will not work in ANSI mode but
connection and initialization should work, so that user as the
first step may specify a supported session sql_mode (from the
editor or from ‘advanced’ tab in connection …

This release fixes a rare crash as well as a regression
bug introduced in 12.3.0.

Changes as compared to SQLyog MySQL GUI 12.3.0
include:

Bug Fixes:

* 12.3.0 introduced a slowness when displaying the saved
connections list with a large no. (100+) of saved connections.
This is fixed now.
* Fixed a rare crash occurring sometimes when typing in the
editor inside an invalid query longer than 128 characters.
Auto-complete was at fault.

This release introduces a new major feature – GUI
transaction support – as well as some minor features and
bug fixes.

Changes as compared to MySQL GUI 12.2.6
include:

Features:

* GUI transactions support. This new feature is available in
Enterprise and Ultimate editions. Also please see note
below.
* Added a tooltip on column headers in Data tab informing
about column name, column type and length.
In Result tab the tooltip will display column name only, as
the result returned by MySQL does not have information of
storage type details.
* Added GUI support for index-level comments in CREATE/ALTER
TABLE.

Bug Fixes:

* Fixed an issue where GUI could ‘hang’ when executing queries
with very large subqueries.
* Fixed an issue with the …

This release fixes two rare crashes and also we have upgraded the
(MariaDB) C-connector to latest version (2.3.1). Most important
this solves an issue when connecting to Amazon RDS using SSL.
This was not possible before.

Changes as compared to MySQL GUI 12.2.5 include:

Bug Fixes:

* SQLyog was not able to connect to RDS instances using SSL
encryption. Attempting to do so returned the error “Failed
to connect to MySQL: SSL connection error: certificate verify
failed”.
* After having a connection open for very long time, SQLyog
could crash when closing this connection.
* Corrupted connection information in the ‘session
restore’-database could cause a crash. We had one
reproducible report of this, but please note that there is
no indication that SQLyog itself caused the corruption. It
may be due to a hardware error, for …

Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.