The world's most popular open source database
Rob Young is a Senior Product Manager with the Sun Database Technology Group. He has over 20 years of database and application development experience with MySQL, Oracle, SQL Server, Sybase, and DB2. His primary responsibility is to work with the MySQL Enterprise Tools Engineering team on solutions that help DBAs and Developers scale their time, talent, and resources across the ever increasing number of MySQL servers he or she is destined to manage.
In an earlier article I described how MySQL Enterprise takes the guesswork out of deciding which version of the MySQL server customers should be running by providing alerts around regularly scheduled Monthly Rapid Update and Quarterly Service Pack releases of the Enterprise Server. Being of an old school "if it ain't broke don't fix it" mindset, I understand the conservative approach most DBAs take when deciding if a new release of any software is relevant to their environment. In fact, given the monthly frequency of Enterprise maintenance releases and the work involved with upgrading, I completely understand how recipients can begin to ignore Update Alerts (unless of course a known fix is on the way). Based on feedback from customers, MySQL colleagues, and my own field experience, I recognize that while notifications around the regular Enterprise Server drops is a good thing, upgrading an existing MySQL implementation is no small task and that a major part of removing guesswork around new releases involves helping those receiving notifications better understand how they are affected.
While many customers pour over the regular Update Alerts we shoot out, our challenge as a collective Engineering team has been to help all customers standardize their applications on the most up to date, bug-free version of MySQL, meaning we need to provide an additional safety net for those who are too busy to review the Update Alerts they receive. Also, what about older, version specific bugs that lay in wait ready to create a security breach or crash condition based on certain combinations of user, database, SQL or data activity? Even smooth running systems can be impacted by bugs that have been previously reported and fixed in newer releases of MySQL. How can we help ensure such bugs are proactively identified and squashed before they surface?
In an effort to provide DBAs with a belt-and-suspenders support and alert system and to further help take the guesswork out of deciding which version of the MySQL server they should be running, MySQL Enterprise now provides the new Upgrade Advisor. The premise is simple; the Upgrade Advisor provides monitoring for specific security and crash inducing bugs that affect current versions of the MySQL Community or Enterprise Server running in an Enterprise Monitor protected environment. It also provides the recommended upgrade path to a version of MySQL that fixes any identified problems.

