Skip navigation links

Kontakt

Deutschland: +49 (0)89/420 95 98 95

USA Subscription Renewals: +1-866-830-4410
EMEA: +353 1 6919191

Kontaktformular »
Verlängern von Abonnements »

MySQL Newsletter - Jetzt abonnieren!

Section 4. About MySQL Enterprise Releases



Return to table of contents

 

 

4.1 What builds of the MySQL Server are available?

There are numerous builds of the MySQL Server available, depending on which product and/or licenses have been purchased. There are three standard builds of the MySQL Server: MySQL Classic Server, MySQL Pro Server, and MySQL Advanced Server. Additionally, there are builds and source packages of MySQL Cluster made available to customers who have purchased that product.

Back to top
 

4.2 What is the difference between MySQL Classic, MySQL Pro and MySQL Advanced Server builds?

MySQL Advanced Server builds are built with partitioning enabled. MySQL Pro Server binaries do not have partitioning enabled, but do include MyISAM, InnoDB, and all other features. MySQL Classic Server excludes InnoDB but contains all other features of MySQL Pro Server.

Back to top
 

4.3 What MySQL Server build am I entitled to use?

MySQL Advanced Server builds are available to MySQL Enterprise Gold and Enterprise Platinum level customers. MySQL Pro Server builds are available at all MySQL Enterprise subscription levels. MySQL Embedded Server (OEM) customers purchase licenses for MySQL Classic Server, MySQL Pro Server, or MySQL Advanced Server as required. MySQL Classic Server is only available to MySQL Embedded Server licensees.

Back to top
 

4.4 How are bugs addressed in the MySQL Server?

Bug fixes are vetted in Monthly Release Updates (MRUs) and are later included in Quarterly Service Packs (QSPs).

Back to top
 

4.5 What is a MySQL Server Monthly Rapid Update (MRU)?

MySQL Server Monthly Rapid Update (MRU) releases serve customers who desire to stay as up to date as possible with releases of the MySQL Server or who have run into a problem that has not yet been fixed in a Quarterly Service Pack. Monthly Rapid Updates are scheduled to be issued once per month for versions of the MySQL Server in the Active Lifecycle stage.

Back to top
 

4.6 What is a MySQL Server Quarterly Service Pack (QSP)?

MySQL Quarterly Service Pack (QSP) releases serve customers who wish to stay current with fixes to the MySQL Server, but do not want to update their servers every month. This program provides cumulative, tested service packs that contain fixes to the MySQL Server. Each QSP is based on a prior MRU, and MySQL QSPs are scheduled to be released every three months, several months after the MRU on which the QSP is based, with the addition of any critical fixes released in intervening MRUs.

Back to top
 

4.7 Are Monthly Rapid Updates and Quarterly Service Packs cumulative?

Yes. Monthly Rapid Updates and Quarterly Service packs are cumulative. This means that each one contains all the fixes that were included with previous release, plus any new fixes. A customer does not have to install earlier service packs before they install the latest one.

Back to top
 

4.8 What happens if I skip installing Monthly Rapid Updates or Quarterly Service Packs?

Quarterly Service Packs are cumulative. If a customer wishes to update, for example, only twice per year, that customer could simply take two service packs and apply them instead of four. If a customer who is not up-to-date with QSPs runs into a problem that is known or reasonably expected to be fixed in a more recent QSP or MRU, that customer will be expected to upgrade to a more recent release.

Back to top
 

4.9 What form do MySQL Server Monthly Rapid Updates, Quarterly Service Packs, and HotFixes take?

All MySQL Server builds are completely new packages in the standard format provided for the platform being used. No MySQL Server releases take the form of patches that can be applied to an existing MySQL installation.

Back to top
 

4.10 What is a MySQL Server HotFix?

MySQL offers HotFix support at the Gold and Platinum level to customers who encounter a known or undiscovered MySQL Server bug in a binary built by MySQL/Sun which causes a major business interruption. If no fix is currently available in an official binary release, MySQL will endeavor to create a HotFix patch for the customer's use.

Back to top
 

4.11 What issues are eligible for a MySQL Server HotFix?

HotFixes are emergency database server patches. The issue must be validated by MySQL Support as a Severity 1 issue. The bug must not be addressed in a current MySQL Server release.

Back to top
 

4.12 How is a HotFix handled for a bug that has already been fixed?

If a bug fix currently exists in a yet-to-be published MySQL service pack, MySQL Support will create a new binary that contains the needed patch as part of the yet-unpublished service pack. The new binary may therefore include other bug fixes unrelated to the reported problem.

Back to top
 

4.13 How is a HotFix handled for a bug that has not yet been fixed?

If the fix does not currently exist in any published or unpublished official MySQL binary release, MySQL Support will validate the bug and assign it to a MySQL developer for investigation. When a HotFix bug fix is returned by MySQL Development, MySQL Support will deliver to the customer a new MySQL server binary containing that HotFix.

Back to top
 

4.14 How does Emergency Bug Fix Escalation work?

MySQL Support will escalate the priority of reproducible, verified bugs which affect customers upon request. Because bugs vary so widely in scope and complexity, MySQL cannot promise to fix any escalated bug within a specific resolution time but only to prioritize it relative to other development work. Escalation requires that you maintain an open support issue regarding the relevant bug until a fix has been delivered.

Back to top
 

PreviousNext