PlanetMysql.ru — информация о СУБД MySQL

We are pleased to announce the release of MONyog 4.7 GA. Below is a brief on new features:

Dashboard

The world is moving towards tablets (I agree iPad in the title is a misnomer) and most of them don’t support Adobe Flash. As you know MONyog dashboard charts were on Flash and did not work on tablets. With this release we have switched to HTML5 charts. Not only do they work on all Smartphones and Tablets, they are faster than Flash charts. Hence, desktop users also gain from this release.

Flash charts used elsewhere in MONyog are also changed to slick HTML5 charts.

Embedded in this post are screen-shots with relevant section zoomed-in on an iPad.

MONyog dashboard in action

Disk Usage Info

Wayback Machine

Who doesn’t like Wayback Machine? Well, MONyog gets one of its own. A neat way of tracking MySQL variables/Status and Queries fired while looking at historic “Number of threads connected” & “Number of slow queries” data. The user gets a chance to see the graphs of “Number of threads connected” & “Number of Slow Queries”, typically a spike on this chart would need attention. Zooming on this spike gives details like Status/Variables/Queries in that zoomed time range. We can also get details at a certain point in time.

Wayback Machine

Replication Tab

Monitoring replication is now even easier. Thanks to the all new ‘Processlist’ like interface to monitor MySQL replication. This tab details the current MASTER & SLAVE STATUS.

MONyog customers can download the latest installer from Webyog’s Customer Portal.

To evaluate MONyog, please download the 30-day trial.

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

Regards,
Chirag
Team MONyog

“Publishing software in English will make you reach most of the global audience” is a myth. Users like software in their own language. For Non-English speaking audience localized software is a necessity. We heard it. SQLyog is now available in Japanese & will be made available in other international languages soon. We are using crowd-sourced human translation services from myGengo for translating SQLyog. I’d also like to add that our website is machine translated using Google Translate.

Embedded below are some related screenshots:

Option to change language

SQLyog in Japanese

If you want to do your own translation, we will soon provide instructions and tools for creating localizations as a ‘drop-in’ solution to an already installed instance. Watch this space for a post on it.

We are very excited about this release would love to have your feedback. What other languages would you like SQLyog in?

Regards,
Chirag
Team SQLyog

We have released SQLyog 9.2 GA with enhancements to the Data Search feature (and more).

Since we introduced the Data Search feature in SQLyog 9.1 we had a lot of positive responses – but also a few critical remarks that using the feature could cause unnecessary server load as well as unnecessarily long response times. Such scenario could arise when searching for a string in a BLOB column used for storing media files for instance. Or when searching all tables of a database when there was only need to search a few tables.

We have addressed this concern by adding filter options that let the user restrict the search to specific data types and to a subset of databases of a server, a subset of tables of a database or a subset of columns of a table.

Also we have added “+” and “-” operators for inclusive and exclusive exact match.

I would like to elaborate a little more on Data Search:

Data Search does not replace SQL, of course. It is a supplementing feature. It is in particular useful when your are searching for something you don’t know what exactly is and don’t know exactly where to find. And when you are just too lazy to write a long SQL statement. As we have posted here before you could consider the Data Search feature as a tool to ‘google your database’ (as google ‘advanced search’ operators are used). But a database has a hierachy and has datatypes what a document has not. So this filtering option is a logical database-related enhancement to the google ‘advanced search’ syntax used for documents.

Let us take an example: Suppose you want to find all instances of email addresses with a specific domain name in all your networked systems (on the Internet as well as Intranet). We have 3 such public systems (our Forums, Blog and FAQ) for our MySQL-related products alone  that are ‘standard applications’ that we did not code ourselves and thus do not know internals about very well. In all those systems people may comment or contact us. Add to this our non-public systems – like our CRM system and our support ticket system (based on our own web application IssueBurner that aggregates everything sent from and received to our contact email addresses to a database). As all the mentioned systems use a MySQL backend we will now easily be able to answer the question “Who have ever contacted us with a @like.this email address, when did it happen and what was the subject/matter?”. Simply because we can find the data in all systems. And anybody in our organization can do (provided that they have access) without knowing details about how and where the different applications store the information.

When we introduced Data Search in 9.1 I actually expected some comments that “this is a feature for amateurs and I do not intend to use it as I am familiar with SQL”. We did not get such comments till now! I think users already found out that it saves a lot of time.

Also in this release we are following up on the ‘Foreign Key lookup’ introduced in 9.0. This is now also functional from the RESULT tab in SQLyog.

And finally In this realease we added a ‘date picker’ GUI for managing DATE, DATETIME and TIMESTAMP columns as well as an option to clone a connection. Both were popular user requests for some time and have now been implemented.

See all details for this and other recent releases here.

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

Until now, MariaDB 5.2 was lacking a yum repository for easy installs and upgrades. It is now available, thanks to OurDelta.

Just follow our very simple installation instructions.

Hi,

We are delighted to announce the release of MONyog 4.5. Listed below are some noteworthy features:

• You did get to know about what needs attention in Monitors/Advisors, but how about looking at all the alerts that need attention grouped on their severity for a certain period? This is what event is all about. An event occurs when the status of a counter changes. Keep your events tab open & you see MONyog alerting you – may it be “server availability” or “replication failure” or many other umpteen things that need attention.
• Many a times, MONyog shows an alert to bring your attention, but you are OK with that & don’t want to fix it. Just close the event & it will appear only when it becomes alert-able again. This is a nice way to accept & dismiss events, so that you can start with a clean slate with a baseline for normal acitivity for that instance.
  
• This one is a real time saver. You register a master & MONyog automatically registers all its slaves. If there are recursive slaves, well yes, they are auto-registered too. This feature is smart to indent slaves according to the hierarchy in the list of servers page. Note that MONyog assumes MySQL (port, username & password) and the SSH details of the slaves are same as that of its master. Once registered, you can edit connection details of slaves if it is different from master & get them monitored by MONyog.
• Long locked queries can cause havoc. With this release you can get alerted whenever a query results in longer locks. You can also ask MONyog to kill long locked queries as and when it happens. These options are present in process-list based sniffer.
• Groups of counters in Monitors/Advisors can now be enabled or disabled for a specific server. Before this release enabling/disabling affected all servers that are being monitored.

This release also contains many more enhancements & bug fixes. Refer the following release notes for details:

• MONyog 4.5 RC Release Notes
• MONyog 4.5 Beta2 Release Notes
• MONyog 4.5 Beta1 Release Notes

MONyog customers can download the latest installer from Webyog’s Customer Portal.

To evaluate MONyog, please download the 30-day trial.

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

Cheers,
Team MONyog

The highlights of this release are:

* A brand new helper function interface: We have implemented an easy-form based interface for customizing helper functions. Any customization of helper functions or user defined functions being used with earlier versions have to be migrated manually to this version. From this version and onwards a GUI-’conflict resolver’ will guide the users very similar to how it works for customized counters.

* Apply settings to all servers of a specific tag: MONyog now has an option to apply a group of settings to all the servers with a specific tag. (Please note: New servers registered later with the same tag are not considered)

* Enhanced readability of MONyog logs: MONyog logs from now on contain the server name along with error making it easy to backtrack.

* Earlier multiple alerts for same issue would be sent if the counter was alertable for more than the specified number of data collections. Now we record what alerts have already been sent and will only send once. Settings in register server page has been updated accordingly.

Minor features & fixes:

* Automatic cleaning of size zero dump files: We have automated deleting dump files of size zero (that could be left behind if MONyog was terminated abruptly).

* Added an option to change the refresh interval from the processlist page.

* Processlist-based sniffer will no longer show the query ‘SHOW FULL PROCESSLIST’ executed by MONyog (Note: This only applies to the processlist-based sniffer and not to the processlist page where user has configurable filtering options).

* Fixed a (SQLite) database lock resulting in failure to update Dashboards and Monitors/Advisors pages.

* When SFTP option was chosen to analyze ‘MySQL general query log’ and SSH was disabled, MONyog still used SFTP to analyze the logs with out throwing any error.

* Small GUI enhancement/improvements.

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

We are pleased to announce this new major release of SQLyog MySQL GUI.

The major enhancements with this release are:

* Information in tabbed interface can be reordered.
Just like you will find it in all modern browsers, TABs can now be reordered using drag’n’drop in the GUI. The option is available for connection tabs as well as Query/Query Builder/Schema Designer tabs.

* Fast and convenient data entry from the keyboard.
We have added ‘FORM view’ option (in addition to ‘GRID view’ and ‘TEXT view’ already available) for managing data in DATA and RESULT tabs. ‘FORM view’ will display one row at a time and is in particular convenient when entering data from the keyboard.

* Query Formatter
The SQLyog Query Formatter is now completely rewritten. In principle all types of SQL statements are now supported and all limitations with the old implementation are lifted.

* Several editor enhancements including:
The Editor now has a ‘folding option’. Multi-line code and comment blocks between bracket-pairs, BEGIN-END pairs, C-style comment pairs (/* and */), WHILE-END WHILE pairs, LOOP-END LOOP pairs, REPEAT-END REPEAT pairs and CASE-END CASE pairs can now be ‘folded’ in/out (ie: hidden or unhidden).

Add to that numerous stability fixes, GUI improvements and more. Read full details here.

We hope you will like this new version – and do not hesitate to contact us if you have comments, suggestions or whatever.

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

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 – or even is not stored in the table at all. Additionally you may now define the substring to be filtered on in more flexible ways than before.

In the editor we added “parenthesis’es matching”. With complex statements (JOINs on derived tables, SUBQUERIES, statements with nested functions and similar) this will make it much easier to identify the structure of the statement. Just position the cursor after a parenthesis and the actual parenthesis and its match will highlight.

We have improved performance by optimizing code in code segments executed most frequently. Additionally we have deployed more debugging and performance measuring tools. This includes – but is not restricted to – moving our build environment to latest Visual Studio environment (2010 edition).

Note that with this release we have stopped supporting Windows 2000. It has for some time been increasingly difficult to continue this support. It is actually quite hard to find a recent system where Windows 2000 will run without errors and we have over the few last years spent quite a lot of effort fixing issues occurring only on this variant of Windows. We believe that the effort is better used ensuring optimal performance on recent and still supported Windows variants – not at least Windows 7, what fastly is taking the position of the dominating Windows variant. The move to Visual Studio 2010 shall be seen in this context. But of course XP, Vista (and the same generations of Windows server variants: 2003 and 2008) are still supported as well as Wine.

Links to Beta/RC release blogs with detailed information.
* http://www.webyog.com/blog/2010/08/17/sqlyog-mysql-gui-8-6-rc3-released/
* http://www.webyog.com/blog/2010/08/06/sqlyog-mysql-gui-8-6-rc2-released/
* http://www.webyog.com/blog/2010/08/06/sqlyog-mysql-gui-8-6-rc-released/
* http://www.webyog.com/blog/2010/08/03/sqlyog-mysql-gui-8-6-beta3-released/
* http://www.webyog.com/blog/2010/07/22/sqlyog-mysql-gui-8-6-beta2-released/
* http://www.webyog.com/blog/2010/07/20/sqlyog-mysql-gui-8-6-beta1-released/

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

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 MONyog now lets you track changes to the global configuration of your MySQL server no matter if the configuration parameters were specified in my.ini/my.cnf, are server defaults or if somebody with SUPER privilege has executed a SET GLOBAL statement.

Improved customization framework

Many MONyog users have long since complained that the customization feature was complex and hard to use: One had to be well-versed in object-oriented JavaScript concepts to even make a minor change. Moreover, unless you manually backed up your customizations, you’d loose all of them if you decided to upgrade! That was motivation enough for us to redesign the entire framework.

With MONyog 4.0 knowledge of writing basic JavaScript functions is more than sufficient to customize any Monitor/Advisor or roll out your very own set. A simple form-based interface with verbose instructions makes it very easy to define a new Monitor/Advisor.

We understand that not every user will make use of the 220+ Monitors/Advisors that we ship with MONyog. So why waste all the computing power? You can now disable a subset of the Monitors/Advisors and keep only the ones you use. If you change your mind later, you can always re-enable them again.

MONyog 4.0 provides a unique customization interface. Now you won’t have to worry about loosing your changes, making mistakes (you can always revert to the original!), or feel scared to experiment.

Improved stability and lots of minor features and bug fixes

As always, this release too contains a lot of bug fixes. MONyog has undergone severe stress testing and is monitoring 200 without issues in our test environment now. From this release we have reduced the number of Linux binaries. In version 3.72 we introduced packages specific to glibc versions. It was necessary at that time to ensure stability on both older Linux distros (RHEL3-generation) as well as the most recent distros using glibc version 2.5. But we never liked it ourselves. It could confuse users – and sometimes did. Since then we have been researching and testing different packaging concepts so that a single binary will do the job on all distros.  This release contains a single 32 and a single 64 binary – each with the option of a .tar.gz archive and a RPM installer.

MONyog customers can download the latest installers from Webyog’s Customer Portal.

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

Regards,

Team MONyog

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 users can use the MONyog interface to change any setting while MONyog is running). Any changes made to the file when MONyog is not running will be reflected by it once it is restarted.
* If MySQL Error Log monitoring was enabled for a particular server, the first two data collections for that server would cause large network traffic to occur if the MySQL error log was very large. This was because the entire log file was read in the first collection. Now only the last 1MB of the file is read.

Miscellaneous:
* All libraries have been upgraded to their latest versions. Although, from a user-perspective, the changes are minimal, this has alleviated several memory leaks and other performance issues.
* This release has been checked in depth with with the best leak-detection tools available for both Linux and Windows.  All discovered leaks have been fixed.
* The cache parameters for the SQLite library have been modified with this release to allow for registering more servers on the same system as before. Before MONyog’s memory usage used to grow continually with time as each open SQLite handle has an associated cache which could grow to any size, irrespective of system capacity. The cache size per handle has been reduced and the total SQLite cache size will never exceed 1 GB with this build.

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