MONyog

MONyog is a cross-platform, easy-to-use and commercial software that lets users easily monitor their MySQL databases from anywhere in the world. It is part of the SQLyog application, which allows users to manage MySQL databases.

Features at a glance

Key features include support for monitoring hacking and security attempts, supports deadlock monitoring, multi-user support, configuration management, real-time monitoring, events manager, and error log monitoring.

Additionally, MONyog features a query analyzer with query sniping, lock and disk monitoring, replication manager, wayback machine, trend and history analysis, dashboard, as well as custom SQL objects and full customization using JavaScript.

It’s cloud ready

MONyog is cloud ready, which means that you can deploy it on a web server and use it from any computer, anywhere. The installation takes only 2 minutes and requires no agents on the host where the MySQL server is installed. It provides real-time monitoring functions that will always show you what are the top running queries, top users, top tables, as well as top locked queries.

Who uses MONyog?

Believe it or not, over 2,000,000 users have bought the MONyog software and it is used by more than 30,000 companies to administer and monitor their MariaDB, Percona and MySQL servers.

Among some of the most important companies that use MONyog, we can mention Google, Apple, Novell, PayPal, 3M, Comcast, CBS, Sony, NASA, Xerox, IBM, Berkeley, DivX, Segway, Disney, Cisco, Verizon, Amazon, Siemens, Fujitsu, Pentax, AOL, Best Buy, eBay and Yahoo!.

Supported operating systems and availability

The software is supported on all Microsoft Windows and GNU/Linux operating systems, successfully tested with both 64-bit and 32-bit instruction set architectures. It is available for download as a 14-day free trial, but a full license will cost 199 USD (160 EUR) for the Professional edition supporting a single MySQL server.

What is new in this release:

• PAM authentication for MySQL and MariaDB servers.
• And, numerous bug fixes.

What is new in version 6.2:

• 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)

What is new in version 9.0 Beta 1:

• Features:
• Added an option (in GRID and FORM view) to look up/search valid values for columns having Foreign Key CONSTRAINTS.
• Added an option to ‘Search Data' in a database or a table. Just enter any string, perform the search and tables with all matches can be accessed - even for UPDATE - with a single click.
• Please refer documentation (help..help menu) for full details on the new major features listed above.
• In CSV-exports NULL-values can be written as a user-specified string. "N' is default for compliance with MySQL (SELECT INTO OUTFILE and LOAD DATA), but for use with other programs (such as spreadsheets) other options may be relevant.
• Added an option to automatically add ‘child' tables to selected tables (before it was only possible to add ‘parent' tables) in Schema Designer.
• Added a "Change Background Color" option in Edit menu.
• Bug fixes:
• Data entered from the GUI to mange ENUM/SET types were not escaped properly what caused problems with the " ‘ " (single quote) and " " (backslash) character.
• Focus in Object Browser was lost when creating a Stored Procedure.
• There is now a button/link to open the log file in each dialog wherever it is referred.
• Fixed an issue where non-binary data were displayed as "(Binary/Image)".
• Now TAB/SHIFT+TAB keys will rotate through buttons, check-boxes and tools in Result/Table Data tabs.
• Fixed a crash occurring when running Schema Sync and a Query Builder or Schema Designer TAB was active in the program main window.

What is new in version 8.8.1:

• Fixed a serious bug in User Management where assigning a new password to a user created a new user instead. This bug was introduced in 8.8.

What is new in version 8.7.1:

• In Form View if a BLOB/TEXT column contained specific sequences of non-ASCII characters the button to open the BLOB viewer would not display correctly.
• When updating from the RESULT tab and when using HTTP-tunnel identifiers were not `backticked`. For same reason the update would fail with identifiers containing SPACE or other characters requiring `backticks` in the statement. This bug was introduced in 8.7.
• ‘Copy Database' GUI did not display the connection name of the source database.
• The fix in 8.7 that autocomplete could sometimes delete the character following cursor position was not complete.

What is new in version 8.6.2:

• SJA now supports an additional -r parameter that tells how big CHUNKS should be when copying to an empty table.
• The -r parameter only has effect with Data Sync jobs and is ignored with other types of jobs.
• This is a command line option only, and is not supported from the GUI Wizard.
• A GUI improvement was made in the Data Sync Wizard, clarifying the difference between syncing "All tables" (existing at any time) and all tables existing at the time of building the job.
• It is now also much easier to select "almost all tables" for a Data Sync job.

What is new in version 8.6:

• User Management is completely redesigned and rewritten.
• There is a ‘custom filter' option in DATA and RESULT tab GRIDs.
• With this option, users can filter on any value from any cell.
• There are options to filter on ‘%value' and ‘value%' in both the ‘Filter' menus and ‘Custom Filter' dialogs.
• There is a tooltip in the 'filter' icon in DATA and RESULT tabs displaying current filter settings.
• CTRL+INS and SHIFT+INS keyboard shortcuts will now copy and paste (like CTRL+C and CTRL+V) in GRIDS.

What is new in version 8.5.4:

• An issue with SSH connection when putty is present was solved.
• PLINK was using the default settings of putty to connect, resulting in an error in connection (introduced in 8.5).
• An issue was solved with SSH connection where SQLyog was reporting Error No. 2003 even if the MySQL port was correct (introduced in 8.5.1).
• If MySQL connection used "anonymous user", SJA would throw an error.
• For create/alter database, the collation drop-down list did not populate values correctly if the TAB key was used to select the charset.

What is new in version 8.5.3:

• SJA was always using port 22 to connect to SSH, but now any valid SSH port can be used to establish a connection with a MySQL server using SSH.
• A PLINK crash which was introduced in SQLyog 8.5 was fixed.

What is new in version 8.5.2:

• An issue with SSH connection when PuTTY is present was solved.
• PLink was using the default settings of PuTTY to connect, resulting in a connection error (introduced in 8.5).
• An issue was solved with SSH connection where SQLyog was reporting Error No.
• 2003 even if the MySQL port was correct (introduced in 8.5.1).
• If a MySQL connection used "anonymous user", SJA would throw an error.
• For create/alter database, collation drop-down list did not populate values correctly if the Tab key was used to select the charset.

What is new in version 8.5.1:

• The ‘Export Table Data As...' option from the object browser menu was exporting just the column headers; this problem was introduced in 8.5 GA.
• In the Notification Services wizard, if a field contained data with quotes, SJA would insert an extra slash along with the field value. Both of these problems were fixed.
• The ‘timeout' for establishing a connection using SSH has been increased from 15 seconds to 30 seconds (15 seconds was too little to establish a connection with slow SSH servers).

What is new in version 8.15 Beta 1:

• An option was added to execute SHOW WARNINGS automatically if the ‘warning-count' is not 0. The output will appear in the MESSAGES tab. Note that this is not implemented for HTTP-tunneling.
• The memory handling in GRIDS with BLOB/TEXT columns was improved. This fixes some sluggishness when scrolling a GRID containing such data.

What is new in version 8.13:

• 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 the authors did not find any way to access encryption functionality from Wine.
• ALTER VIEW will now format the SELECT-part of the VIEW definition.
• All batch jobs will not generate BULK INSERTS larger than 16MB now (as already implemented in Import External Data in 8.11).

What is new in version 8.1:

• Massive speed improvements in the following areas:
• Data synchronization
• Auto complete
• Export as SQL (including Scheduled Backups), CSV and XML
• Major new features:
• Completely revamped Objects tab. The tab has been renamed to "Info". The contents are now available in nicely formatted HTML in addition to the old text format
• Direct import of Access, Excel and CSV files. Now you don't need to create ODBC DSN to import these file types. Just point to the files and SQLyog does the rest
• GUI changes:
• Added an option to ‘preview SQL' in CREATE/ALTER TABLE
• Column width in all GRIDs (not only DATA and RESULT tabs) are now persistent
• New GUI for defining ENUM and SET columns in Create/Alter GUI
• Some reorganisations of menus, improved captions and explanations in dialogues and wizards etc

What is new in version 8.04:

• Crash dumps with no information (zero-size) will now be deleted automatically.
• When saving/copying from the editor, the LETTERCASE modifications 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.
• Previously, only selecting the table object itself did.
• The table information is now available in the OBJECTS tab when a column or index is selected.
• A ‘key' icon is used for identifying the Primary Key in an Object Browser 'Indexes' folder.

What is new in version 7.13:

• A rare crash in Schema Sync was fixed. This issue was discovered when testing internally. No user had reported this.
• Management of column-level privileges was not functional and has been fixed. It was only possible to select a single group of objects in GRIDS with the shift+click modifier, so this has been fixed.
• Autocomplete now uses secure atomic transactions when writing to SQLite databases ("Tags files"). A few reports were made of random program crashes that could be traced down to corrupt SQLite databases. This corruption will not happen any more.

Limitations:

• 14 days free trial