February 9, 2021

• Mysql Workbench Server Not Running Mac
• Mysql Server Not Starting Mac
• Mysql Server Instance Is Not Running Mac

Support EOL for MySQL Connector/J 5.1

January 18, 2021. Support EOL for SUSE 15.0/1. Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for SUSE 15.0/1 as of January 18, 2021. I then install the exact same Ubuntu 16.04 OS on my same machine. This time, not as a VM but as the native OS. I run the exact same script, under the same Ubuntu OS with no modifications at all and I get the dreaded MySQL: 'SQLSTATEHY000 1130 Host '172.20.0.3' is not allowed to connect to this MySQL server' during migration. But starting from SQL Server 2019, it can also be run on Linux and from Docker container. However, migrating data between heterogeneous databases is not straightforward. It is not something to be taken lightly. Datatypes Require Conversion. Data types in MySQL and SQL Server are alike but not the same.

Per Oracle's Lifetime Support policy, as of Feb 9th, 2021, MySQL Connector/J 5.1 series is covered under Oracle Sustaining Support. Users are encouraged to upgrade to MySQL Connector/J 8.0 series.

February 1, 2021

MySQL 5.6 is covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, as of February 1, 2021, MySQL 5.6 is covered under Oracle Sustaining Support.

Users are encouraged to upgrade to MySQL 8.0.

January 18, 2021

Support EOL for SUSE 15.0/1

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for SUSE 15.0/1 as of January 18, 2021.

November 25, 2020

Support EOL for Fedora 31

Per the MySQL Support Lifecycle policy regarding ending support for OS versionsthat have reached end of life, we plan to discontinue building all MySQL binariesfor the Fedora 31 platform as of November 25, 2020.

October 19, 2020

Support EOL for macOS v10.14

Due to very low demand, MySQL has stopped development and support for macOS 10.14. MySQL 8.0 is the only supported version on macOS. Users of MySQL 5.7 are encouraged to upgrade to MySQL 8.0. Source and binaries for previously releasedversions will continue to be available from the archives.

September 18, 2020

MySQL Notifier is now covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, as of Sept 18, 2020, MySQL Notifier is covered under Oracle Sustaining Support.

September 18, 2020

MySQL for Excel is now covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, as of Sept 18, 2020, MySQL for Excel is covered under Oracle Sustaining Support.

Learn how to connect Excel to MySQL

July 10, 2020

Support EOL for Debian 8

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for Debian 8 as of June 30, 2020.

May 26, 2020

Support EOL for Fedora 30

Per the MySQL Support Lifecycle policy regarding ending support for OS versionsthat have reached end of life, we plan to discontinue building all MySQL binariesfor the Fedora 30 platform as of May 26, 2020.

May 20, 2020

Support EOL for MySQL Connector/ODBC 5.3

Per Oracle's Lifetime Support policy, as of May 20th, 2020, MySQL Connector/ODBC 5.3 series is covered under Oracle Sustaining Support. Users are encouraged to upgrade to MySQL Connector/ODBC 8.0 series.

May 20, 2020

Support EOL for MySQL Connector/C++ 1.1

Per Oracle's Lifetime Support policy, as of May 20th, 2020, MySQL Connector/C++ 1.1 series is covered under Oracle Sustaining Support. Users are encouraged to upgrade to MySQL Connector/C++ 8.0 series.

April 27, 2020

Support EOL for MySQL 5.7 on Fedora

Due to very low demand, MySQL has stopped development and support forMySQL 5.7 on Fedora. Users of Fedora are requested to upgrade to recentversions of MySQL. Source and binaries for previously released versionswill continue to be available from the archives.

January 13, 2020

Support EOL for macOS v10.13

Due to very low demand, MySQL has stopped development and support for macOS 10.13. Usersare requested to upgrade to recent versions of macOS. Source and binaries for previously releasedversions will continue to be available from the archives.

November 26, 2019

Support EOL for Fedora 29

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for the Fedora 29 platform as of November 26, 2019.

October 14, 2019

Support EOL for MySQL 5.7 on FreeBSD

Due to very low demand, MySQL has stopped development and support for MySQL 5.7 on FreeBSD. Users of FreeBSD are requested to upgrade to recent versions of MySQL. Source and binaries for previously released versions will continue to be available from the archives.

May 28, 2019

Support EOL for Fedora 28

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for the Fedora 28 platform as of May 28, 2019.

See Fedora 28 End of Life announcement »

April 25, 2019

Support EOL for FreeBSD v11

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, have reached end of life, or have little usage pattern, we plan todiscontinue building all MySQL binaries for FreeBSD v11 on April 25, 2019.

See https://www.freebsd.org/releases/ »

April 25, 2019

Support EOL for Ubuntu 14.04

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, have reached end of life, or have little usage pattern, we plan todiscontinue building all MySQL binaries for Ubuntu 14.04 on April 25, 2019.

See Extended Security Maintenance for Ubuntu 14.04 announcement »

March 31, 2019

Support EOL for SUSE Enterprise Linux v11

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, have reached end of life, or have little usage pattern, we plan todiscontinue building all MySQL binaries for SUSE Enterprise Linux v11 on March 31, 2019.

See https://www.suse.com/lifecycle/ »

January 31, 2019

MySQL Connector/NET 6.x is covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, as of January 31, 2019, MySQL Connector/NET 6.x is covered under Oracle Sustaining Support. Users are encouraged to upgrade to MySQL Connector/NET 8.0.

January 25, 2019

Support EOL for MySQL Enterprise Monitor 3.4

Per the MySQL Enterprise Monitor Lifecycle policy of supporting the two most recent major GA releases, MySQL Enterprise Monitor 3.4 has reached its end of life with the GA announcement of MySQL Enterprise Monitor 8.0.

January 20, 2019

MySQL 5.5 covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, as of December 31, 2018, MySQL 5.5 is covered under Oracle Sustaining Support.

Users are encouraged to upgrade to MySQL 8.0.

January 8, 2019

MySQL Connector/Python 2.x is covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, as of January 8, 2019, MySQLConnector/Python 2.x is covered under Oracle Sustaining Support. Users are encouraged to upgrade to Connector/Python 8.0.

November 30, 2018

Support EOL for Fedora 27

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reachedend of life, we plan to discontinue building all MySQL binaries for the Fedora 27 platform as ofNovember 30, 2018.

See Fedora 27 End of Life announcement »

November 26, 2018

MySQL Router 2.x covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, as of November 26th, 2018, MySQL Router 2.x is covered under Oracle Sustaining Support. Users are encouraged to upgrade to MySQL Router 8.0.

November 26, 2018

MySQL Shell 1.x covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, as of November 26th, 2018, MySQL Shell 1.x is covered under Oracle Sustaining Support. Users are encouraged to upgrade to MySQL Shell 8.0.

October 19, 2018

Support EOL for Mac OS X v10.12

Due to very low demand, MySQL has stopped development and support for Mac OS X 10.12. Usersare requested to upgrade to recent versions of OS X. Source and binaries for previously releasedversions will continue to be available from the archives.

October 19, 2018

Support EOL for MySQL 5.6 on macOS

Due to very low demand, MySQL has stopped development and support for MySQL 5.6 on macOS. Users of macOS are requested to upgrade to recent versions of MySQL. Source and binaries for previously released versions will continue to be available from the archives.

October 18, 2018

Support EOL for MySQL Enterprise Monitor 3.1, 3.2, 3.3

Per the MySQL Enterprise Monitor Lifecycle policy of supporting the three most recent GA releases, MySQL Enterprise Monitor 3.1, 3.2 and 3.3 have reached end of life with the GA announcement of MySQL Enterprise Monitor 4.0.

May 31, 2018

Support EOL for Debian 7

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for Debian 7 as of May 31, 2018.

See Debian 7 End of Life announcement »

May 30, 2018

MySQL Utilities is now covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, as of May 30, 2018, MySQL Utilities is covered under Oracle Sustaining Support.

Users are encouraged to migrate to MySQL Shell.

May 29, 2018

Support EOL for Fedora 26

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reachedend of life, we plan to discontinue building all MySQL binaries for the Fedora 26 platform as ofMay 29, 2018.

See Fedora 26 End of Life announcement »

April 11, 2018

Support EOL for Windows 8

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete or have reached end of life, we plan to discontinue building all MySQL binaries for Microsoft Windows 8 as of April 11, 2018.

See Windows lifecycle fact sheet »

December 12, 2017

Support EOL for Fedora 25

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reachedend of life, we plan to discontinue building all MySQL binaries for the Fedora 25 platform as ofDecember 12, 2017.

See Fedora 25 End of Life announcement »

October 30, 2017

Support EOL for Mac OS X v10.11

Due to very low demand, MySQL has stopped development and support for Mac OS X 10.11. Users are requested to upgrade to recent versions of OS X. Source and binaries for previously released versions will continue to be available from the archives.

August 8, 2017

Support EOL for Fedora 24

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reachedend of life, we plan to discontinue building all MySQL binaries for the Fedora 24 platform as ofAugust 8, 2017.

See Fedora 24 End of Life announcement »

July 6, 2017

MySQL Fabric is now covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, as of July 6, 2017, MySQL Fabric is covered under Oracle Sustaining Support.

Users are encouraged to migrate to MySQL InnoDB Cluster.

April 28, 2017

Support EOL for Ubuntu 12.04

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete or have reached end of life, we plan to discontinue building all MySQL binaries for Ubuntu 12.04 as of April 28, 2017.

See Ubuntu 12.04 End of Life announcement »

April 18, 2017

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete or have reached end of life, we plan to discontinue building all MySQL binaries for Red Hat Enterprise Linux v5, Oracle Linux 5 and CentOS v5 as of April 30, 2017.

April 10, 2017

Support EOL for FreeBSD v10

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, or have reached end of life, or have little usage pattern, we plan to discontinue building all MySQL binaries for FreeBSD v10 platform as of April 10, 2017.

See https://www.freebsd.org/releases/ »

December 20, 2016

Support EOL for Fedora 23

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for the Fedora 23 platform as of December 20, 2016.

See Fedora 23 End of Life announcement »

December 12, 2016

Support EOL for Mac OS X v10.9, 10.10

Due to very low demand, MySQL has stopped development and support for Mac OS X 10.9, 10.10. Users are requested to upgrade to recent versions of OS X. Source and binaries for previously released versions will continue to be available from the archives.

September 19, 2016

Support EOL for MySQL Enterprise Monitor 3.0

Per the MySQL Enterprise Monitor Lifecycle policy of supporting the three most recent GA releases, MySQL Enterprise Monitor 3.0 has reached end of life with the GA announcement of MySQL Enterprise Monitor 3.3.

July 19, 2016

Support EOL for Fedora 22

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for the Fedora 22 platform as of July 19, 2016.

See Fedora 22 End of Life announcement »

June 23, 2016

Support EOL for Windows 7

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete or have reached end of life, we plan to discontinue building all MySQL binaries for Microsoft Windows 7 as of June 23, 2016

See Windows lifecycle fact sheet »

June 23, 2016

Support EOL for Microsoft Windows Server 2008

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete or have reached end of life, we plan to discontinue building all MySQL binaries for Microsoft Windows Server 2008 as of June 23, 2016

See Windows lifecycle fact sheet »

April 15, 2016

Support EOL for Debian 6

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for Debian 6 as of April 15, 2016

See Debian 6 End of Life announcement »

February 10, 2016

Support EOL for Mac OS X v10.8

Due to very low demand, MySQL has stopped development and support for Mac OS X 10.8. Users are requested to upgrade to recent versions of OS X (10.9+). Source and binaries for previously released versions will continue to be available from the archives.

December 2, 2015

Support EOL for Fedora 21

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for the Fedora 21 platform as of December 1, 2015.

See Fedora 21 End of Life announcement »

October 28, 2015

Support EOL for MySQL Enterprise Monitor 2.3

Per the MySQL Enterprise Monitor Lifecycle policy of supporting the two most recent GA releases, MySQL Enterprise Monitor 2.3 has reached end of life with the GA announcement of MySQL Enterprise Monitor 3.1.

August 21, 2015

Support EOL for Microsoft Windows Vista

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete or have reached end of life, we plan to discontinue building all MySQL binaries for Microsoft Windows Vista as of August 21, 2015.

See http://windows.microsoft.com/en-us/windows/lifecycle »

August 19, 2015

Support EOL for FreeBSD v8, v9

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, or have reached end of life, or have little usage pattern, we plan to discontinue building all MySQL binaries for FreeBSD v8, v9 platform as of August 31, 2015.

See https://www.freebsd.org/releases/ »

July 15, 2015

Support EOL for Microsoft Windows 2003 Server

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete or have reached end of life, we plan to discontinue building all MySQL binaries for Microsoft Windows 2003 Server as of April 15, 2015. See Microsoft's Windows 2003 Server EOL announcement »

June 23, 2015

Support EOL for Fedora 20

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for the Fedora 20 platform as of June 23, 2015.

See Fedora 20 End of Life announcement »

January 7, 2015

Support EOL for Fedora 19

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for the Fedora 19 platform as of January 6, 2015.

See Fedora 19 End of Life announcement »

September 25, 2014

Support EOL for Mac OS X v10.6, 10.7

Due to very low demand, MySQL has stopped development and support for Mac OS X 10.6, and 10.7. Users are requested to upgrade to recent versions of OS X (10.8+). Source and binaries for previously released versions will continue to be available from the archives.

April 8, 2014

Support EOL for Microsoft Windows XP

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete or have reached end of life, we plan to discontinue building all MySQL binaries for Microsoft Windows XP as of April 8, 2014. See Microsoft's Windows XP EOL announcement »

January 14, 2014

Support EOL for Fedora 18

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached end of life, we plan to discontinue building all MySQL binaries for the Fedora 18 platform as of January 14, 2014.

See https://lists.fedoraproject.org/pipermail/announce/2014-January/003194.html »

December 4, 2013

MySQL 5.1 covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, as of December 31, 2013, MySQL 5.1 is covered under Oracle Sustaining Support.

Users are encouraged to upgrade to MySQL 5.6.

September 2, 2013

Support EOL for SUSE Enterprise Linux v10

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, have reached end of life, or have little usage pattern, we plan to discontinue building all MySQL binaries for SUSE Enterprise Linux v10 on September 30, 2013.

See https://www.suse.com/lifecycle/ »

February 5, 2013

Support EOL for the following Platforms

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, have reached end of life, or have little usage pattern, we plan to discontinue building all MySQL binaries for the following platforms.

As of February 5, 2013, the following platforms are EOL.

Vendor EOL'd and outdated platforms:

• Oracle Solaris v9
  Oracle announcement of EOL of Solaris v9

January 7, 2013

Support EOL for the following Platforms

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, have reached end of life, or have little usage pattern, we plan to discontinue building all MySQL binaries for the following platforms.

As of January 7, 2013, the following platforms are EOL.

Vendor EOL'd and outdated platforms:

• Oracle Linux v4
• RedHat Enterprise Linux v3, v4
  Red Hat announced version 3 has past 'End of Production 3 End of Regular Life Cycle' as of Oct 31, 2010 (https://access.redhat.com/support/policy/updates/errata/).
  Red Hat announced version 4 has past 'End of Production 3 End of Regular Life Cycle' as of Feb 29, 2012 (https://access.redhat.com/support/policy/updates/errata/).
• CentOS v4
  CentOS EOL announced February, 2012 (http://lists.centos.org/pipermail/centos-announce/2011-December/018285.html)
• SUSE Enterprise Linux v9
  SUSE EOL announced July, 2009 (see ftp://ftp.compaq.com/pub/products/servers/linux/NovellSLESLifeCycle.pdf)
• Debian v4, v5
  Debian EOL announced February, 2012 (http://www.debian.org/News/2012/20120209)
• FreeBSD v6, v7
  FreeBSD EOL announcements (http://www.freebsd.org/releases/)
• Apple Mac OS X v10.4, v10.5

Our platform support continues to evolve and we recently added following platforms:

• New - Windows 8, x86 and x86_64
• New - Windows Server 2012, x86 and x86_64
• Stay tuned for additional platforms and packages

Source and binaries for previously released versions will continue to be available from archives.

MySQL will continue to provide commercial support for existing customers in accordance with Oracle's Lifetime Support Policy.

As always, thanks for your continued support of MySQL!

Mysql Workbench Server Not Running Mac

June 14, 2012

Support EOL for MySQL Connector/MXJ

Due to very low demand, MySQL has stopped development and support for Connector/MXJ. Source and binaries for previously released versions will continue to be available from archives.

March 8, 2012

MySQL Connector/NET 6.3 Support EOL

MySQL Connector/NET 6.5 was released for General Availability on March 8, 2012. Support for MySQL Connector/NET 6.3 has now ended. Current Connector/NET 6.3 users are encouraged to upgrade to Connector/NET 6.5 for the most current feature set and bug fixes.

January 9, 2012

MySQL 5.0 covered under Oracle Lifetime Sustaining Support

Per Oracle's Lifetime Support policy, MySQL 5.0 is now covered under Oracle Sustaining Support.

Users are encouraged to upgrade to MySQL 5.5.

April 21, 2011

Support EOL for Intel Itanium (IA64)

Due to very low demand, MySQL will discontinue support for Intel Itanium (IA64) on April 30, 2011.

Support EOL for Intel Itanium (IA64) applies to:

• Microsoft Windows (Win XP, Win 2003, Win Vista, Win 7, etc.) on Intel Itanium
• Linux (RedHat, Oracle, SUSE, etc.) on Intel Itanium
• HP-UX on Intel Itanium

MySQL will continue to provide commercial support for existing customers on Itanium-based servers in accordance with Oracle's Lifetime Support Policy.

March 1, 2011

MySQL Enterprise Monitor Support EOL for the following platforms

Per the Oracle/MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, have reached end of life, or have little usage pattern, we plan to discontinue building MySQL Enterprise Monitor agent binaries for the following platforms.

Effective March 7, 2011 these platforms will no longer be supported for MySQL Enterprise Monitor versions 2.3.3 and higher:

Vendor EOL'd and outdated platforms

• Red Hat Enterprise Linux 3
• Microsoft Windows 2000
• SUSE Enterprise Linux v7
• Mac OS X for PowerPC
• Solaris 8
• OpenSolaris
• HP-UX 11.11
• FreeBSD 6
• Debian 3.1
• Fedora Core 4

Low demand platforms

• IBM AIX 5.3

Due to very low demand and according to IBM an April-2011 EOM (see http://www-01.ibm.com/software/support/lifecycleapp/PLCDetail.wss?synkey=E275996K38397L94-J526041L68492N04-Q513879J82296G35) this distribution has been dropped.

* IBM i 5.4 and 6.1

Due to very low demand and according to IBM a 5.4 Jan-07-2011 EOM (see http://www-947.ibm.com/systems/support/i/planning/upgrade/suptschedule.html) these distributions have been dropped.

January 10, 2011

Support Ending for Windows 2000

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete or have reached end of life, we plan to discontinue building all MySQL binaries for Microsoft Windows 2000 as of January 6, 2011. According to Microsoft, extended support for Windows 2000 ended July 13, 2010.

December 7, 2010

Support EOL for the following Platforms

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, have reached end of life, or have little usage pattern, we plan to discontinue building all MySQL binaries for the following platforms.

As of January 1, 2011, these platforms will no longer be supported for MySQL versions 5.0 and higher.

• Redhat Enterprise Linux v3
  According to Redhat version 3 is has past 'End of Production 3 End of Regular Life Cycle' as of Oct 31, 2010 (see https://access.redhat.com/support/policy/updates/errata/).
• SUSE Enterprise Linux v9
  According to SUSE, the SLES General Support End Date was July 2009 (see ftp://ftp.compaq.com/pub/products/servers/linux/NovellSLESLifeCycle.pdf) and for OpenSUSE (see http://lists.opensuse.org/opensuse-security-announce/2007-03/msg00001.html)
• OpenSUSE v 9
  According to opensuse,org, OpenSUSE, SUSE Linux 9.3 has been discontinued (see http://lists.opensuse.org/opensuse-security-announce/2007-03/msg00001.html)
• IBM AIX 5.3
  Due to very low demand and according to IBM an April-2011 EOM (see http://www-01.ibm.com/software/support/lifecycleapp/PLCDetail.wss?synkey=E275996K38397L94-J526041L68492N04-Q513879J82296G35) this distribution has been dropped.
• IBM i 5.4 and 6.1
  Due to very low demand and according to IBM a 5.4 Jan-07-2011 EOM (see http://www-947.ibm.com/systems/support/i/planning/upgrade/suptschedule.html) these distributions have been dropped.
• Linux Generic RPM built with icc (Intel compiler)
  Due to low demand the general Linux RPM distribution created with the icc Intel compiler has been dropped.
  Note: The gcc build is the preferred alternative.

Our platform support continues to evolve and we recently added following platforms to our officially supported list.

• New - Fedora 12, x86 and x86_64
• New - FreeBSD 8, x86 and x86_64
• Stay tuned for additional platforms and packages

Old releases for the EOLed platforms listed above remain available for download and we will continue to provide source code and limited support for customers who wish to build MySQL 5.1 and higher on these platforms. Please see the MySQL Support Policies for more information.

As always, thanks for your continued support of MySQL!

November 10, 2010

Support Ending for FreeBSD 6

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete or have reached end of life, we plan to discontinue building all MySQL binaries for FreeBSD 6 as of 2010-Nov-30. According to the FreeBSD Organization support for the FreeBSD 6.x stable branch will also cease on November 30, 2010.

May 25, 2010

Support EOL for Debian 3.1 ends on June 1, 2010

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete or have reached end of life, we plan to discontinue building all MySQL binaries for Debian 3.1 as of June 1, 2010. According to the Debian Project, Debian 3.1 is now 'obsolete' (see http://www.debian.org/releases/)

Our platform support continues to evolve and as such we are also adding Debian 5 to our officially supported platform list.

January 4, 2010

Support EOL for Low Usage Platforms

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have little usage pattern, we plan to discontinue building all MySQL binaries for the following platforms.

As of February 1, 2010, these platforms will no longer be supported for MySQL versions 5.0 and higher.

• Mac OS X for PowerPC
  Due to low demand and fading vendor support.Note: Apple has dropped support for PowerPC in Mac OS X Snow Leopard. Dropping PowerPC also falls in line with many other vendors such as Adobe.MySQL will focus on added support for latest Mac OS X releases
• Linux Generic RPM for PowerPC
  Due to very low demand this general Linux distribution has been dropped.
• Linux Generic RPM built with icc (Intel compiler) for Itanium
  Due to low demand and technical issues the general Linux RPM distribution created with the icc Intel compiler has been dropped.
  Note: The gcc build for Itanium is recommended as the preferred alternative.
• Generic Linux Build for S/390
  Due to low demand.

Our platform support continues to evolve and we recently added following platforms to our officially supported list.

• New - Windows 7, x86 and x86_64
• New - Mac OS X 10.6, x86 and x86_64
• New - HP-UX 11.31, Itanium build
• New - SLES 11, x86 and x64

Old releases for the EOLed platforms listed above remain available for download from the MySQL Customer Support Center and we will continue to provide source code and limited support for customers who wish to build MySQL 5.0 and higher on these platforms. Please see the MySQL Support Policies for more information.

As always, thanks for your continued support of MySQL!

December 31, 2009

MySQL 4.1 Extended Support ended on December 31, 2009

Per the MySQL Support Lifecycle policy, extended support for MySQL 4.1 ended on December 31, 2009. MySQL users are encouraged to upgrade to a current production release of MySQL. Customers needing upgrade assisitance should contact MySQL Support.

Please see the MySQL Support Lifecycle policy for more information.

December 31, 2009

MySQL 5.0 Active Support ended on December 31, 2009 - Now in Extended Support Phase

Per the MySQL Support Lifecycle policy, active support for MySQL 5.0 ended on December 31, 2009. MySQL 5.0 is now in the Extended support phase.

Please see the MySQL Support Lifecycle policy for more information.

December 18, 2009

EOL of MySQL Query Browser, MySQL Administrator, MySQL Migration Toolkit

With the beta releases of MySQL Workbench 5.2 well under way, we are announcing the EOL of the MySQL GUI Tools Bundle.

The MySQL Tools team has been working on MySQL Workbench 5.2 to give DBAs and developers an integrated tools environment for:

• Database Design & Modeling
• SQL Development (replacing MySQL Query Browser)
• Database Administration (replacing MySQL Administrator)

MySQL Workbench 5.2 also provides:

• Remote Administration (using SSH-Tunneling)
• Python scripting and plugins
• Native GUI for Windows, Mac, Linux

A future release of MySQL Workbench (post 5.2) will add a migration plugin, providing features comparable to the MySQL Migration Toolkit component of the MySQL GUI Tools Bundle. The MySQL Support team will continue to provide technical assistance for MySQL Migration Toolkit until such migration support functionality is released in MySQL Workbench, but no new development or bug fixes will be provided against the existing MySQL Migration Toolkit product.

MySQL Support will continue to answer questions and provide assistance related to MySQL GUI Tools Bundle, as well as assist our customers in upgrading from those tools to MySQL Workbench 5.2 until June 30, 2010.

Starting Dec 18, 2009, MySQL will no longer accept bug reports submitted against the MySQL GUI Tools Bundle, and existing bug reports against these tools will no longer be worked on. Users should instead download, use, and submit bug reports (where necessary) against MySQL Workbench. Downloads of the MySQL GUI Tools Bundle will remain available, but will be moved into the MySQL Archives location.

Users should begin planning to upgrade to MySQL Workbench 5.2 GA.

March 24, 2009

Support Ending for AIX 5.2

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached vendor end of life, we plan to discontinue building or supporting MySQL binaries for AIX 5.2 as of 2009-April-30. See IBM EOS (End of Support).

Please see the MySQL Support Lifecycle policy for more information.

December 1, 2008

MySQL 4.0 Extended Support ends on December 31, 2008

Per the MySQL Support Lifecycle policy, extended support for MySQL 4.0 ends on December 31, 2008. MySQL users are encouraged to upgrade to a current production release of MySQL. Customers needing upgrade assisitance should contact MySQL Support.

Please see the MySQL Support Lifecycle policy for more information.

October 15, 2008

Support EOL for Vendor/Low Usage Platforms

Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached vendor end of life or that have little to no usage pattern, we plan to discontinue building all MySQL binaries for version 4.1 effective 2008-Dec-31 and version 5.0 effective 2009-Dec-31 for the following OS versions.

These OS versions will not be supported for MySQL versions 5.1 and higher.

• HP-UX 11.00
• MAC OSX 10.3
• SCO OpenServer (all versions)
• QNX (all versions)

We will continue to provide source code and support for customers who wish to build MySQL 4.1 and higher on these and other specific OS versions. Please see the MySQL Support Policies for more information.

Please see the MySQL Support Lifecycle policy for more information.

As always, thanks for your continued support of MySQL!

Chapter 3. Installing and Launching MySQL Workbench

Table of Contents

3.1. Hardware Requirements

3.2. Software Requirements

3.3. Starting MySQL Workbench

3.3.1. Installing MySQL Workbench on Windows

3.3.2. Launching MySQL Workbench on Windows

3.3.3. Uninstalling MySQL Workbench on Windows

3.3.4. Installing MySQL Workbench on Linux

3.3.5. Launching MySQL Workbench on Linux

3.3.6. Uninstalling MySQL Workbench on Linux

3.3.7. Installing MySQL Workbench on Mac OS X

3.3.8. Launching MySQL Workbench on Mac OS X

3.3.9. Uninstalling MySQL Workbench on Mac OS X

3.4. Activation Procedure (Commercial Version)

MySQL Workbench is available for the following platforms:

Binary distributions of MySQL Workbench are avaliable for the above platforms. Source code distributions are also available as a tar.gz package, or an RPM package.

The following sections explain the installation process for each of these platforms.

MySQL Workbench requires a current system to run smoothly. The minimum hardware requirements are:

• CPU: Intel Core or Xeon 3GHz (or Dual Core 2GHz) or equal AMD CPU

• Cores: Single (Dual/Quad Core is recommended)

• RAM: 4 GB (6 GB recommended)

• Graphic Accelerators: nVidia or ATI with support of OpenGL 1.5 or higher

• Display Resolution: 1280×1024 is recommended, 1024×768 is minimum.

The following operating systems are officially supported:

• Windows 7 (64-bit, Professional level or higher)

• Mac OS X 10.6.1+

• Ubuntu 9.10 (64bit)

• Ubuntu 8.04 (32bit/64bit)

For convenience the following builds are also available:

• Windows XP SP3, Vista

• Mac OSX (10.5 and 10.6) Intel

• Ubuntu 8.04 (i386/x64)

• Ubuntu 9.04 (i386/x64)

• Fedora 11 (i386/x64)

MySQL Workbench also has the following general requirements:

1. The Microsoft .NET 3.5 Framework.

2. Cairo 1.6.0 or later

3. glib-2.10

4. libxml-2.6

5. libsigc++ 2.0

6. pcre

7. libzip

For convenience the Windows libraries are available as the download “Dependencies for Compiling in Windows”.

On start up, the application checks the OpenGL version and selects between software and hardware rendering. To determine the rendering method that is being used, open the Help menu and choose the System Info submenu.

The procedure for launching MySQL Workbench depends on the platform. Generally, there are two ways to launch MySQL Workbench from the command line and from the graphical user interface of the host operating system. Using the command-line launching facility is useful when you want to customize some aspects of the way MySQL Workbench operates. Launching MySQL Workbench for each of the supported platforms is described in the following sections.

In addition to platform-specific command line options, MySQL Workbench has the following command line options:

• --admin instance - Launch MySQL Workbench and load the server instance specified.

• --query connection - Launch MySQL Workbench and load the connection specified.

• --model modelfile - Launch MySQL Workbench and load the model specified.

• --script script - Launch MySQL Workbench and run the script specified.

• --run code - Launch MySQL Workbench and run the code snippet specified.

• --quit-when-done - quits MySQL Workbench after --script or --run finishes.

MySQL Workbench may be installed using the Windows installer file or it may be installed manually from a ZIP file.

Installing MySQL Workbench Using the Installer

MySQL Workbench can be installed using the Windows Installer (.msi) installation package. The MSI package bears the name mysql-workbench-version-win32.msi, where version indicates the MySQL Workbench version number.

Installing MySQL Workbench using the installer requires either Administrator or Power User privileges. If you are using the ZIP file without an installer, you do not need Administrator or Power User privileges.

Improving the MySQL Installation Wizard depends on the support and feedback of users. If you find that the MySQL Installation Wizard is lacking some feature important to you, or if you discover a bug, please report it in our bugs database. To do this use the Report a Bug option under the Help menu.

1. To install MySQL Workbench, right-click the MSI file and select the Install option from the pop-up menu, or simply double-click the file.

2. In the Setup Type window you may choose a Complete or Custom installation. To use all features of MySQL Workbench choose the Complete option.

3. Unless you choose otherwise, MySQL Workbench is installed in C:%PROGRAMFILES%MySQLMySQL Workbench 5.1 edition_type, where %PROGRAMFILES% is the default directory for programs for your locale. The %PROGRAMFILES% directory may be C:Program Files or C:programme.

Installing from the ZIP File

Mysql Server Not Starting Mac

If you are having problems running the installer, as an alternative, you can download a ZIP file without an installer. That file is called mysql-workbench-version-win32.zip. Using a ZIP utility, unpack it to the directory of your choice. You may also want to create a shortcut on your desktop or the quick launch bar.

To install using the ZIP file, download the ZIP file to a convenient location and decompress the file. You can place the resulting directory anywhere on you system. You do not need to install or configure the application before using it.

To start MySQL Workbench on Windows select Start, Programs, MySQL and then select MySQL Workbench.

You may also start MySQL Workbench from the command line. To view the available command-line options, issue the command MySQLWorkbench -help | more from the MySQL Workbench installation directory. You will see the following output:

The MySQL Workbench version number is displayed followed by a usage message and then the options. Use the -swrendering option if your video card does not support OpenGL 1.5. The -version option can be used to display the MySQL Workbench version number. The -grtversion can be used to display the GRT shell version number. The other options are self-explanatory.

When using command-line options that display output to a console window, namely -help and -version, be sure that you pipe the output through the more command otherwise nothing will be displayed.

The method for uninstalling MySQL Workbench will depend on how you install MySQL Workbench in the first place.

Rmoving MySQL Workbench when installed Using the Installer

1. To uninstall MySQL Workbench, open the Control Panel and Choose Add or Remove Programs. Find the MySQL Workbench entry and choose the button. Doing this will remove MySQL Workbench.

2. Any modules added to the C:Program FilesMySQLMySQL Workbench versionmodules directory will not be deleted.

It is not possible to remove MySQL Workbench from the command line if you have installed MySQL Workbench using the installer. Although you can manually remove some of the compoentns There is no command-line option for removing MySQL Workbench.

Removing the MySQL Workbench directory manually will not remove all the files belonging to MySQL Workbench.

When installed from a ZIP file

If you installed MySQL Workbench using a ZIP file, to remove MySQL Workbench you can just delete the MySQL Workbench directory.

If you installed any additional modules within the modules directory and you want to keep them, make sure you copy those modules to a different directory before deleting the MySQL Workbench directory.

There are several binary distributions of MySQL Workbench available for Linux. These include:

• Fedora 10 amd64 (RPM)

• Ubuntu 8.04 i386 (DEB)

• Ubuntu 8.10 amd64 (DEB)

In addition to the binary distributions, it is also possible to download the MySQL Workbench source code as a tar.gz or RPM package.

Check the MySQL Workbench download page for the latest packages.

The procedure for installing on Linux depends on which Linux distribution you are using.

Installing DEB packages

On Ubuntu, and other systems that use the Debian package scheme, you can install MySQL Workbench using a command such as:

Note that package.deb will be the MySQL Workbench package, for example, mysql-workbench-oss-version_i386.deb, where version is the MySQL Workbench version number.

You may be warned that certain libraries are not available, depending on what you already have installed. Install the required libraries and then install the MySQL Workbench package again.

Installing RPM packages

Mysql Server Instance Is Not Running Mac

On RedHat-based systems, and other systems using the RPM package format, MySQL Workbench can be installed by a command such as:

Again, note that package.rpm will be the MySQL Workbench package, for example, mysql-workbench-oss-version-1fc10.x86_64.rpm, and version is the MySQL Workbench version number.

Once MySQL Workbench has been installed it can be launched by selecting Applications, Programming, MySQL Workbench from the main menu.

MySQL Workbench can also be launched from the command line on Linux. Type the command:

This will display the available command-line options:

The procedure for uninstalling MySQL Workbench on Linux depends on the packe you are using.

Uninstalling DEB packages

For Debian packages the command is:

This does not remove the configuration files. If you wish to also remove the configuration files use:

Uninstalling RPM packages

To uninstall RPM packages use:

This does not remove the configuration files.

MySQL Workbench is available for Mac OS X and is distributed as a DMG file. The file is named mysql-workbench-oss-version-osx10.5-i686.dmg, where version is the MySQL Workbench version.

To install MySQL Workbench on Mac OS X, simply download the file. Double-click the downloaded file. You will be presented with the installation screen:

Figure 3.1. MySQL Workbench Mac OS X Installation Screen

Drag the MySQL Workbench icon onto the Application icon as instructed. MySQL Workbench is now installed.

You can now launch MySQL Workbench from the Applications folder.

To launch MySQL Workbench on Mac OS X, simply open the Applications folder in the Finder, then double-click MySQL Workbench.

It is also possible to start MySQL Workbench from the command line:

A model file must be specified.

To uninstall MySQL Workbench for Mac OS X, simply locate MySQL Workbench in the Applications folder, right-click, and select Move to Trash. The application is uninstalled.