phpMyAdmin for sale?

peter_laursen

I recently came across this article listing SourceForge Community Choice Awards Winners 2008:

http://weblog.infoworld.com/openresource/archives/2008/07/sourceforge_com.html

“Most Likely to Be the Next $1B Acquisition” is phpMyAdmin? Now I am not sure if phpMyAdmin actually is something that can be acquired and if there is any revenue (directly or indirectly) generated from it at all, but in my opinion phpMyAdmin has reached a point close to the end of its life-cycle, and I can hardly imagine there is anything to pay for. Except for very small additions to support new MySQL versions there has - to my best knowledge - been nothing but bug fixes for around 3 years. No new developments. phpMyAdmin basically provides an interface for viewing the content of tables, to execute statements and scripts and view the result. And that’s it.

And don’t miss it - that is useful in lots of situations. If phpMyAdmin is installed on a *AMP server you can access the database from any computer connected to the Internet without having anything installed locally. But the interface is somewhere in between *just usable* and *horrible* (depending on how it is configured and how it integrates in control panel applications etc.)

As time goes by it becomes obvious that
* phpMyAdmin has missed opportunity to provide ‘power tools’ - like synchronization tools, proper migration/import and export tools, GUI environments for schema design and query design, tools for query analysis and optimization etc.
* The simple HTML interface provided by phpMyAdmin is far away from today’s standard of web applications.

I believe there would be a market for a high-quality web based MySQL database administration tool (no matter the license model) if it adopted modern AJAX based web interfaces. The current phpMyAdmin ‘plain HTML interface’ requires that everything (data, images, stylesheets) of the complete page will have to be reloaded or even resent from the server for every page refresh. That results in huge communication overhead, annoying page refreshes and time waste - even in situations where only a small detail on that page needs to be updated. Today’s web users (whether gamers or just gmail users) expect a web interface very close to that of a compiled binary. Because they are used to it like that, and because they know (and see every day) it is possible.

One of the most common remarks from  SQLyog users, that have replied to our recent user surveys, is “What a relief to get rid of phpMyAdmin”.

At Webyog we cannot honestly regret this situation as we benefit from it and do increasingly much for every day. From a more ‘ideal’ point of view one can say it is a shame (and phpMyAdmin indeed should be credited for its huge contribution to the popularity of MySQL in the early days of MySQL). But my guess is the situation is that ‘the train has left the station. No more trains leaving for the foreseeable future. Sorry for you if you did not catch it!’. In other words: I don’t believe the phpMyAdmin community can mobilize the resources to ‘catch the train’ again - also because they (as a community) do not seem to realize how the gap between their application and the best available other options widens for every day.

Also I do not think this situation is special for phpMyAdmin and the phpMyAdmin community actually - on the opposite I think a large percentage of Open Source Community developers simply got out of touch with how the Web has developed over the last 2-3 years. Another good example is the Linux/KDE Konqueror program. I love it because of the many access/connectivity options it provides in one interface, and should I ever shift from Windows to Linux as my primary platform Konqueror would be one of the main reasons .. but (regretfully) it is hardly usable as a webbrowser any more as it did not adopt modern web standards.

Further it is interesting to see how the relationship between PHP and MySQL in general has also changed over the last years. 3-4 years ago they were mostly so closely related that lots of users did not realize the difference and were not able to think of MySQL in other contexts than a PHP-context. We had several complaints at that time from users, that were simply not able to realize that PHP statements and syntax could not be used in the SQLyog SQL editor - and lots of users thought that PHP was a prerequisite for accessing MySQL (and also lots of ISP supporters and even sysadmins told their users so, because even they did not know better!).

But ‘used-to-be patterns’ are breaking up! Examples:
* Since first version 5 release PHP has shipped with the SQLite database. I have seen quite a lot of standard PHP web applications shifting in direction from MySQL to SQLite as their primary/default database option. Also ‘RUBY on the Rails’ project is in that process, I believe. And in particular with ’shared hosting’ that makes good sense in my opinion as everthing - also databases - are stored  in user’s own space on the server (the drawback is of course that direct access to the database bypassing the application can be a problem).
* According to the survey here http://www.paragon-cs.com/mag/issue5.pdf (at the bottom) JAVA is now an equally important client environment for MySQL based applications as is PHP (and this is not because of the acquisition of MySQL by Sun - it started long before that).

Anybody out there want to buy phpMyAdmin (I can spare a few copies!) ?


MONyog 2.51 has been released

peter_laursen

Bug fix:
* Depending on the chosen installation environment and the Linux distro, the RPM build might not install ‘on top’ of a previous installation.  Before installing a new version it was necessary to uninstall the previous version. This is a limitation with all RPM builds released till now.  From this build and onwards it will always be possible to ‘upgrade on top’ of a previous version. Note: this  was an issue with the RPM installer - not the program binary. There is no change in the binary as such and also no change in the Windows installer and the .gz build for Linux.

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


SQLyog 7.01 Has Been Released

peter_laursen

Changes (as compared to version 7.0) include:

Bug fix:
* When SQLyog tried to reconnect while exporting a crash could occur. This bug was introduced in 7.0 with the speed optimization of the export dialogue.

Also SJA for Linux was updated with a fix for a (non-related) issue: Since version 6.5 SJA for Linux would not run on Pentium 3 processors (a ‘illegal instruction’ error was returned).  This is now fixed with this generic build.

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


MONyog 2.5 has been released

peter_laursen

We are pleased to announce that we are now able to release MONyog 2.5 FINAL.

First: for the overall concepts and considerations with this release please refer to this BLOG post (from the release of first beta).

Details for this release (as compared to version 2.06) are:

Features:

MySQL Server Log Analysis: MONyog is now able to retrieve (completely or partially) the General Query Log and the Slow Query Log (whether stored as files or tables on the server) from the MySQL servers it connects to and analyze them.

Query Sniffer: A ‘query sniffer’ is implemented that will record a ‘pseudo log’ on the client (MONyog) side. The sniffer is useful when ‘real logs’ are not available, but also the sniffer has various filtering options what will sometimes make it more useful than the ‘real server logs’ also when they are available.

The log analysis component will (whether operating on a ‘real log’ or a ’sniffer pseudo log’) only display identical queries once but print a ‘count’ for every query. Important information (like execution time, number of instances for this query etc.) will be displayed in a sortable table view.

In the log analyzer ‘Filter settings’ (not to be confused the filter settings of the ‘query sniffer’) there further is an option to ‘replace literals’. The purpose of this option is to eliminate small differences between ‘almost identical’ queries. Currently ‘quoted strings’ and numbers are replaced with the dummy string ‘XXX’ only. We may extend this feature to support more (like special keywords and functions (like NULL, now()), operators etc.) in the next releases. It will depend on the demand for this as compared to the demand for other features. Also note that the current implementation has the ‘imperfection’ that also numbers that are not values (like the ‘1′ in identifiers like `column1`) will be replaced.

More Linux system counters added: Counters related to Linux memory (including swap) usage added.

RPM build now supports SuSE and Mandrake/Mandriva Linux distributions.

Bug fixes:

* Under specific circumstances the MONyog service would stop very slow.
* If network connection was temporarily unavailable the first CPU value after network came back told 100% CPU load.
* The temporary files for storing public/private keys are now being created with very restrictive file permission in Linux. So only the owner will be able to read/write these temporary files. Although these files would exist only for a fraction of second, in earlier versions of MONyog other users in the same Linux system could get access to them within that small timeslice.
* Fixed an issue with trending where graphs would not always display properly for uptime-based counters.
* MONyog.ini file and MONyog database files on Linux are now only readable for user who starts/installs (.gz and RPM build respectively) Monyog (and of course for any user too that was given access by a root user). Before the files were world-readable. This applies to fresh installations only - there is no change with existing installations.
* Solved an issue where slow startup could occur if lots of servers were registered (Technical: If MONyog had not been running for a while, large amounts of data could require deletion from the MONyog database. The queries used to identify those data would generate significant I/O at startup. The retention process is now ’smoothed over time’ and indexes have been added for more efficient deletions).

Important fixes as compared to previous 2.5 betas are:
* Optimized SFTP code. Log Analyzer is now several times faster than what previous Betas were.
* A log file parsing issue with MySQL 5.1.x was resolved.
* Fixed an issue that could occur if some queries in log had binary data. A gibberish error message was displayed.

.

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

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


We are listening

chirag

Hi All,

We had asked for feedback on our products. Thanks for such an overwhelming response. Your feedbacks are listed here.

We are being thanked for our products every now & then by users through various channels (forums, tickets, blog comments, mails etc.). This drill was an effort to bring your voices to netizens’ notice. We are committed to make our users’ life easy by letting our products handle the arcane stuff. It is an honor to build a product that make people rejoice literally…(See Mark Cloyd’s comment).

We have received thousands of responses, however we could only include a few in our web-site. It was very tough to select the final two winners.

The most useful and feature specific feedback was provided by:

1. Mark Cloyd - Owner / Programmer, Mark Cloyd Designs
2. Alan Crabb - Director, Integer Group Ltd.

Congratulations to Mark & Alan. Someone from Webyog will be contacting you soon. Thank you for helping others make a wise decision.


MONyog 2.5 RC2 has been released

peter_laursen

Changes as compared to first 2.5 RC release include:

Bug fixes and Enhancements:
* Fixed a crash with wrong SSH details. This was an issue in Linux only.
* When a folder path (not a file path) to a server log was entered by user, SFTP log retrieval could hang forever. Also this was an issue in Linux only.
* MONyog.ini file and MONyog database files on Linux are now only readable for user who starts/installs (.gz and RPM build respectively) Monyog (and of course for any user too that was given access by a root user). Before the files were world-readable. This applies to fresh installations only - there is no change with existing installations.
* Various optimisations.

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


SQLyog 7.0 has been released

peter_laursen

Changes as compared to version 6.56 include:

Features:

* New GRID design (’zebra’ Office 2007 style) for easier navigation.
* Multiple selection in GRIDs with SHIFT+CLICK.
* Improved Data Synchronization. Now typically 2-8 times faster than before depending on data. Option to generate a SQL sync script was added.
*  Drastically improved the speed of exports.
* New more user friendly design for the Schema Synchronisation (renamed from Structure Synchonisation). Various filter (’hide and ignore’) options were added. Also a long-running Schema Sync compare task can now be stopped.
*  Added automatic and manual update check.

Bug fixes:

* A backup script backing up all databases could fail to restore VIEWs referencing another database than the one where the VIEW was.
* Around 50 other small (mostly GUI-related) fixes for issues reported by users.

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

NB: Please note that as this 7.0 release is a major new release, a new registration code is required for the ENTERPRISE version.  Registered users that still have free upgrades can retrieve their new code from our Customer Portal.


SQLyog 7.0 RC2 has been released

peter_laursen

Changes (as compared to first RC) include:

Features:

* Drastically improved the speed of exports.

Bug fixes:

* Fixed some typical ‘beta bugs’ reported internally as well as by  users.

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


MONyog 2.5 RC has been released

manohar.s

Bug fixes and Enhancements:

  • Optimized SFTP code. This means that the Log Analyzer is now several times faster than previous Betas
  • Fixed an issue with trending
  • Log file parsing issue with MySQL 5.1.x resolved

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


Independent MONyog review by Sheeri Cabral of The Pythian Group

rn

Sheeri Cabral, an active MySQL blogger and two-time winner of MySQL Community Contributor awards has written a great review on MONyog.

Read the full review here

Our favorite highlights:

As an overall review — MONyog is the best out-of-the-box GUI monitoring tool for MySQL that I have seen. It “just works.” As promised, getting up and running quickly is easy, and having a centralized location for monitoring is very useful. The graphs are beautiful and the statistics that are graphed are useful time-savers.

The biggest difference between MySQL’s Enterprise Monitor and MONyog is that MONyog is agentless. At Pythian, we have many clients with differing security requirements. Requiring a daemon process to be running is not something we currently do, and it might be a hard sell for some clients. Even if every client was amenable to it, making sure the daemon is up and running on each MySQL server is tedious. Note that agentless operation works for every feature, including log analysis as well as operating system statistics.