Happy Holidays from Webyog!

It’s been a great year. We have shipped major versions of our products, had record number of downloads and acquired thousands of customers. We wouldn’t be where we are without your support.

As as small token of our appreciation, we will be giving away 2 Kindles to our supporters. To take part in this giveaway all you need to do is:

1. Follow @webyog on Twitter.
2. Tweet on how some specific feature of our products has been useful to you. The two most original and feature-specific entries will win a Kindle.

   For example, rather than Tweeting: “SQLyog rocks!” you should Tweet:
   “The autocomplete feature of SQLyog saves me countless hours of typing everyday”
   OR
   “MONyog has made MySQL replication monitoring less painful”

We’ll choose the winners by searching Twitter for “SQLyog” and “MONyog” among followers. Please send in your entries by 31st Dec 09, 23:59 PST. We will announce the winners in our blog in 1st week of Jan, 2010.

You can also avail a flat 20% Christmas discount on all Webyog products till 31st Dec 09, 23:59 PST. Use coupon code “xmas09″ to avail this discount from our webshop.

Cheers and best of luck!
Team Webyog

Comments(0)

Changes (as compared to  3.61) include:

Bug fix:
* When using the option (introduced in 3.6) to alert for long-running queries from the Query Sniffer interface, such long-running query could raise multiple alerts.

Miscellaneous:
* Added ‘User and Host’ information for long running query alert.

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

Comments(0)

I had one of those situations today that I think every person working with IT experiences from time to time.  I had a problem that took 4 hours to resolve.  Once resolved I realized that doing the right things in the right order (and also memorizing a little better) could have saved me 3 hours and 55 minutes.

The problem was related to SQLyog HTTP-tunneling. When new PHP versions are released it is most often me that verifies that our HTTP tunneling is not broken.  Thus I have followed the PHP 5.3 release cycle from early betas to RC and GA and experienced that very early  PHP 5.3.0 beta  releases did not work with our HTTP-tunnel. However as both 5.3.0 RC and 5.3.0 GA worked fine (as every 5.2.x always did) I executed “SET panic = OFF” against my most important system (old but still a little functional!).

However the panic reoccurred when PHP 5.3.1 was released.  Nothing worked from PHP. I sat for a couple of  hours with a colleague. Small and very simple PHP test applications  did not work with PHP 5.3.1 either on my environment (but worked fine on my PHP 5.2.11 and 5.3.0 configurations). Not a single comma was added to the MySQL general log or error when trying to connect from PHP 5.3.1. The client application hang for considerable time and finally came out with an error that the URL to the PHP script could not be found. Even more frustrating: the test applications and SQLyog/HTTP-tunnel worked fine on another machine with a(should be) identical configuration in Webyog office as well. Needless to say any connection not using PHP also worked fine.

We are aware that some functions in PHP are depreciated in  5.3.x (and will be removed in PHP 6 according to plans).  This may cause problems with our current tunneler on some systems with PHP 5.3.1.  But we have the fix ready to be released with next SQLyog release (and anybody experiencing such problems can contact us for an updated tunneler).  But as 5.3.0 was not affected this was obviously not the problem occurring on my system. It was something else.

We agreed that I should try reinstalling MySQL and Apache from scratch on my system. However before doing so I ran the queries:

SELECT VERSION(); — returned ‘5.1.36-log’
SHOW ENGINES; — returned PBXT as one engine available in addition to the engines from MySQL … hhmmmm …
Now I got it! I remember now that this particular server on this particular system of mine was a forked build with the PBXT engine downloaded from Primebase website.  Installing the standard/official MySQL 5.1.41 solved the problem immediately. PHP 5.3.1 (and thus SQLyog/HTTP-tunnel) connect like a charm.

I am not able to tell what the problem with this server and PHP version is in technical terms.  And probably this server is also now historical so it is probably not very important either now.  But I think Primebase, the MariaDB people, the XAMPP distributors (and everybody building MySQL with PBXT) as well as the PHP developer team should know this issue and try to figure it out (as well as test with their recent builds and PHP 5.3.1), so that it will not happen again.  A forked build should not only work with the (command line) clients shipped with the server but the tools and connectors used by people already.

… (and besides the version string ‘5.1.36-log’ is definitely not good enough for a forked server build).

Comments(4)

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 use it only to profile and tune queries for a large scale production environment. The Ultimate edition is for those users in particular that have full control over their database and their applications.

We thought it is the right time to have multiple editions of SQLyog. This means that people can start with the lower edition and gradually move to a higher edition if the need arises. This will also reduce the overall complexity and total cost of ownership for several customers.

The various editions of the commercial version SQLyog are Professional, Enterprise and Ultimate. You can find the comparison sheet here.

We have also migrated all existing SQLyog Enterprise customers to SQLyog Ultimate. The yearly upgrade and prices of SQLyog Ultimate are same as SQLyog Enterprise upgrade prices. So if you are already an Enterprise customer your Total Cost of Ownership remains same while you continue to enjoy the powerful tools and features of Ultimate.

Feel free to leave your feedback in the comments section.

Below follows release notes in traditional form:

Changes (as compared to 8.18) include:

Features:
* Added a ‘Schema Optimizer’ feature. Based on “procedure analyse()” it will propose alterations to data types for a table based on analysis on what data are stored in the table. The feature is available from INFO tab/HTML mode. Refer to documentation for details.
* A table can now be added to Query Builder canvas multiple times. A table alias is automatically generated for second and higher instance of the table. This is required for special queries like self-JOINs (note: table alias support in Query Builder is an ongoing process).
* In the ‘Import External Data’ wizard same import settings can now be applied to all tables in one operation.
* In MESSAGES tab we are now displaying the query if error occurs during execution in order to make it easier to identify what query raised an error when executing multiple statements.

Bug Fixes:
* ‘Import External Data Tool’ -TRIGGERS did not use the Primary Key for the WHERE-clause if a PK existed on source (all columns were used with the WHERE instead). This could cause problems with tables having Floating Point data.
* A malformed XML-string could cause failure to connect with HTTP tunneling. This was a rare issue only.
* After DROP a ’stored program’ followed by CREATE same, autocomplete would not recognize the ’stored program’ unless after a program restart.
* ‘duplicate table’ has an option to duplicate triggers defined ON that table, but the way we named the new trigger could cause inconsistencies. Now the new trigger will be named ‘oldtriggername_newtablename’.
* Autocomplete was not functional with names of Triggers and Events.
* In MESSAGES tab font could change if non-ASCII characters were displayed.
* ALTER TABLE failed to rename a column when old and new column name only differed by letter-case. Actually the dialogue just shut down.
* A calculation error could cause export tools to create BULK INSERT statements larger than specified by user.
* Import External Data Tool will now always map any autoincrement type from ODBC sources to a MySQL autoincrement integer. Before this datatypes that could autoincrement on source but not in MySQL (example: a SQL Server ‘decimal autoincrement’) failed to import.
* Now Import External Data Tool will convert SQL Server ‘GETDATE()’ to MySQL ‘now()’. Before this an error occurred at import with GETDATE()’s.
* Fixed a Object Browser flickering issue when refreshing.

Packaging and licensing:
* The licensing scheme for SQLyog has changed: there is now the free Community version (unchanged) and 3 different commercial licensing models: Professional, Enterprise and Ultimate. Refer to comparison matrix for details . All existing Enterprise users were upgraded to Ultimate at no cost. Also note that this 8.2 version requires a new registration code as compared to 8.1x. Existing  Customers will get from our Customer Portal.  Please ensure that you have the new registration code available when installing. Also note that Professional, Enterprise and Ultimate installer files are now all named ‘SQLyog82.exe”. TRIAL is named ‘SQLyog82Trial.exe’ and Community name is ‘SQLyog82Community.exe’. The reason for this change is that it simplifies maintenance of the webshop records and download area files for us.
* TRIAL now has ULTIMATE features with the exception that there is a restriction on how many tables and other objects can be handled in a single SJA job (similar to what was previously the case with ENTERPRISE TRIAL).

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

Comments(13)

Changes (as compared to 3.6) include.

Bug Fix:
* If notifications were enabled, program threads were not always closed properly what ultimately could lead to a program ‘hang’. This bug was introduced in 3.6.

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

Comments(0)

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 also specify an option to kill such queries.

Better server management

Several of MONyog’s customers monitor hundreds of MySQL servers using a single instance of MONyog. Managing large number of servers has just gotten a whole lot easier. With tagging, you can categorize your servers into logical groups, and avoid clutter.

Many people had requested the option to add servers programatically. That was one of the primary motivations for documenting the entire MONyog schema. Some customers want to register hundreds of servers quickly without writing any code. For such situations, we introduced the ability to duplicate a connection with a single click. After duplicating a connection, most of the time you just need to change the MySQL IP or Port. You would probably want to retain all other settings.

Improved alerting system

Many users of MONyog have reported that they sometimes receive alerts for insignificant events. And, which is worse, because of this they tend to ignore important alerts! Some of the improvements in the alerting system are:

a) We have introduced the concept of “Delayed alert notifications”. It can now be defined that a problem must have existed for a number of sample intervals continuously (in a row) for an alert to be sent. A global setting for each server is available from GUI. For individual counters the global setting can be overridden by defining the RetryOverride (like ‘RetryOverride:3′) property of the (JavaScript) counter definition

b) You can also choose to be notified when MONyog detects that a problem, which existed previously, has been resolved.

I/O Monitoring for Linux servers

MONyog now provides several monitors on Linux I/O metrics.

Get notified on MySQL restart

We have also added an option to send alerts if server was restarted between two data retrievals. With managed hosting the MySQL server may be restarted automatically as part of routine maintenance or after a server crash. Knowing when this has occurred can be useful.

Lot of minor features and bug fixes

This release also contains many bug fixes, UI improvements and minor features. You can find the complete release notes in the ‘Version History’ section of MONyog’s Help, available online here.

MONyog customers can download the latest installers from Webyog’s Customer Portal.
To evaluate MONyog, please download the 30-day trials.

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

Regards,
Team MONyog

Comments(1)

Happy Holidays!

Black Friday is back. We are happy to offer a 50% flat discount on all Webyog products. Yes, you read it right, fifty percent flat discount. Hurry up, this offer is valid only till 1st Dec 09, 23:59 PST.

Still using SQLyog Community Edition? Held off buying SQLyog Enterprise Edition? This offer is literally too good to pass up. Its time to own your copy of SQLyog Enterprise with all the PowerTools. Check out what Enterprise Edition has to offer.

Worried about your MySQL server’s health? Monitor it like a PRO. Get MONyog – MySQL Monitor & Advisor. Your MySQL DBA in a box! Check what it has to offer.

Want to extend your maintenance period? Don’t think twice, head right away to Customer Area. On extension, you get free access to all future release of the respective products for one year.

Use coupon code blkfrdy09 to avail 50% discount on all your purchases. Please note that this offer is valid only till 1st Dec 09, 23:59 PST.

Regards,
Team Webyog

Comments(5)

Changes (as compared to first 3.6 beta) include:

Features:
* Grouping of servers: one or more ‘tags’ can now be specified for a server. In ‘register servers’ page the list of servers are grouped as per tags. As more tags may be specified for a server, it may appear in more groups. A group established this way can be selected in one operation.
* Added an option to send alert if server was restarted between two data retrievals. With managed hosting the MySQL server may be restarted automatically as part of routine maintenance or after a server crash. Knowing when this has occurred can be useful.
* Process-list based sniffer now has an option to notify about and kill long running queries.
* New and updated counters/advisors.
* Added automatic and manual update check.

Bug Fixes:
* With specific settings Dashboard graphs could hide other displayed dialogs.
* Notification mails now have information  about the value that triggered the alert.
* In log analysis a divisor ‘1024′ was used for calculation of ‘kilo rows’. Now the divisor ‘1000′ is used.
* Exporting charts as graphics did not use a consistent naming convention. Now files will be named ‘MONyog_chart_ConnectionName_Chart_Title.file_extension’.
* GUI improvements, improved error messages etc.
* For slave servers process-list options to “Kill”, “Copy”, “View Query” and “Explain” were not always accessible.

Miscellaneous:
* Added a warning in Disk Info page that the calculation may be expensive. In particular with databases with thousands of objects the calculations may cause unacceptable load.

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

Comments(0)

The primary reason for this release are the bug fixes (included with both 8.18 and 8.2 RC2):

* Schema Sync failed to set the auto-increment flag when syncing a table having this flag to a table not having. This bug was introduced in 8.13.
* SMTP authentication and notification could fail with passwords having special characters.
* Solved a crash with Query builder while creating VIEWs.
* INFO tab/HTML format was showing incorrect value for table’s data size having values in Gigabytes.

Additionally 8.18 includes  Bug Fixes already available in 8.2 beta and RC’s:
* The display of the optimized query from EXPLAIN EXTENDED is now truncated to 2 KB. With long BLOB/TEXT data there will need to be some limit.
* Schema Sync will now query Information_Schema for a VIEW definition. MySQL sometimes returns ‘databasename.viewname’ and not just ‘viewname’ when using SHOW CREATE .
* The fix in 8.15 for the issue that Windows Vista and higher could warn that SQLyog was not properly installed was not complete. It could still happen.

Additionally 8.2 RC2 includes:
* Schema optimizer will now throw a warning if table is empty. Also interface now has link to help/documentation.

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

Comments(0)

Changes (as compared to beta 1) include:

Bug Fixes:
* A calculation error could cause export tools to create BULK INSERT statements larger than specified by user.
* Import External Data Tool will now always map any autoincrement type from ODBC sources to a MySQL autoincrement integer. Before this datatypes that could autoincrement on source but not in MySQL (example: a SQL Server ‘decimal autoincrement’) failed to import.
* Now Import External Data Tool will convert SQL Server ‘GETDATE()’ to MySQL ‘now()’. Before this an error occurred at import with GETDATE()’s.
* Schema Sync will now query Information_Schema for a VIEW definition. MySQL sometimes returns ‘databasename.viewname’ and not just ‘viewname’ when using SHOW CREATE.
* Fixed a Object Browser flickering issue when refreshing.
* The fix in 8.15 for the issue that Windows Vista and higher could warn that SQLyog was not properly installed was not complete.  It could still happen.

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

Comments(0)