Upgrading MySQL with the MySQL APT Repository Upgrading the Shared Client Libraries 2.11.8 Upgrading MySQL with the MySQL APT Repository 2.11.9 Upgrading MySQL with the MySQL SLES Repository 2.11.10 Upgrading MySQL on Windows Note Note 293 MySQL Installer does not support upgrades between  Community  releases and Commercial  releases. If you require this type of upgrade, perform it using the ZIP archive approach. Upgrades between non-GA releases (or from a non-GA release to a GA release) are not supported. Significant development changes take place in non-GA releases and you may encounter compatibility issues or problems starting the server. Whichever approach you choose, always back up your current MySQL installation before performing an upgrade. See Section 7.2, “Database Backup Methods” . The approach you select depends on how the existing installation was performed. Before proceeding, review Section 2.11, “Upgrading MySQL”  for additional information on upgrading MySQL that is not specific to Windows. There are two approaches for upgrading MySQL on Windows: On the SUSE Linux Enterprise Server (SLES) platform, to perform an in-place upgrade of MySQL and its components, use the MySQL SLES repository. See Upgrading MySQL with the MySQL SLES Repository in A Quick Guide to Using the MySQL SLES Repository. On Debian and Ubuntu platforms, to perform an in-place upgrade of MySQL and its components, use the MySQL APT repository. See Upgrading MySQL with the MySQL APT Repository in A Quick Guide to Using the MySQL APT Repository. If you recompile applications and dynamically link them with the updated libraries:   As typical with new versions of shared libraries where there are differences or additions in symbol versioning between the newer and older libraries (for example, between the newer, standard 8.0 shared client libraries and some older—prior or variant—versions of the shared libraries shipped natively by the Linux distributions’ software repositories, or from some other sources), any applications compiled using the updated, newer shared libraries require those updated libraries on systems where the applications are deployed. As expected, if those libraries are not in place, the applications requiring the shared libraries fail. For this reason, be sure to deploy the packages for the shared libraries from MySQL on those systems. To do this, add the MySQL Yum repository to the systems (see Adding the MySQL Yum Repository) and install the latest shared libraries using the instructions given in Installing Additional MySQL Products and Components with Yum. After updating MySQL using the Yum repository, applications compiled with older versions of the shared client libraries should continue to work. •Using MySQL Installer •Using the Windows ZIP archive distribution