View source for Software:MySQL

{{short description|SQL database engine software}}
{{Infobox software
| title                  =
| name                   = MySQL
| logo                   = MySQL logo.svg
| logo size              = 100px
| logo alt               =
| logo caption           =
| screenshot             = Mysql-screenshot.PNG
| screenshot size        =
| screenshot alt         =
| caption                = [[Screenshot]] of the default MySQL command-line banner and prompt
| collapsible            =
| author                 = [[Company:MySQL AB|MySQL AB]]
| developer              = [[Company:Oracle Corporation|Oracle Corporation]]
| released               = {{Start date and age|1995|05|23|df=yes}}
| latest release version = <!-- If you update Template:MySQL version, it will automatically update this page and [[Software:List of content management systems|List of content management systems]]--> {{MySQL version}}
| latest release date    = {{MySQL version|releasedate}}
| programming language   = [[C (programming language)|C]], [[C++]]<ref>{{cite web |url=http://www.ohloh.net/p/mysql/analyses/latest |title=MySQL: Project Summary |work=Ohloh |publisher=Black Duck Software |access-date=17 September 2012}}</ref>
| operating system       = [[Software:Linux|Linux]], [[Software:Solaris (operating system)|Solaris]], [[Software:MacOS|macOS]], [[Software:Microsoft Windows|Windows]], [[Software:FreeBSD|FreeBSD]]<ref>{{cite web|url=http://www.mysql.com/support/supportedplatforms/database.html |title=Supported Platforms: MySQL Database |publisher=Oracle |access-date=24 March 2014}}</ref>
| platform               =
| size                   =
| language               = [[Social:English language|English]]
| genre                  = [[Software:Relational database management system|RDBMS]]
| license                = [[Software:GNU General Public License|GPLv2]] or [[Proprietary software|proprietary]]<ref>{{cite web|url=http://www.mysql.com/downloads/ |title=Downloads |publisher=MySQL |access-date=2014-08-03}}</ref>
| standard               =
}}

'''MySQL''' ({{IPAc-en|ˌ|m|aɪ|ˌ|ɛ|s|ˌ|k|juː|ˈ|ɛ|l}})<ref name="whatismysql">{{cite web|url=https://dev.mysql.com/doc/refman/8.0/en/what-is-mysql.html|title=What is MySQL?|work=MySQL 8.0 Reference Manual|publisher=Oracle Corporation|access-date=2020-04-03|quote=The official way to pronounce "MySQL" is "My Ess Que Ell" (not "my sequel"), but we do not mind if you pronounce it as "my sequel" or in some other localized way.}}</ref> is an [[Open-source software|open-source]] [[Software:Relational database management system|relational database management system]] (RDBMS).<ref name="whatismysql" /><ref>{{cite web|url=http://db-engines.com/en/ranking/relational+dbms|title=DB-Engines Ranking of Relational DBMS|website=DB-Engines|publisher=solidIT consulting & software development GmbH|access-date=2020-04-03}}</ref> Its name is a combination of "My", the name of co-founder Michael Widenius's daughter My,<ref>{{cite web|url=https://dev.mysql.com/doc/refman/8.0/en/history.html|title=History of MySQL|work=MySQL 8.0 Reference Manual|publisher=Oracle Corporation|access-date=2020-04-03|quote=MySQL is named after co-founder Monty Widenius's daughter, My.}}</ref> and "SQL", the acronym for Structured Query Language. A [[Relational database|relational database]] organizes data into one or more data tables in which data may be related to each other; these relations help structure the data. SQL is a language that programmers use to create, modify and extract data from the relational database, as well as control user access to the database. In addition to relational databases and SQL, an RDBMS like MySQL works with an [[Operating system|operating system]] to implement a relational database in a computer's storage system, manages users, allows for network access and facilitates testing database integrity and creation of backups.

MySQL is [[Free and open-source software|free and open-source software]] under the terms of the [[Software:GNU General Public License|GNU General Public License]], and is also available under a variety of [[Proprietary software|proprietary]] licenses. MySQL was owned and sponsored by the Swedish company [[Company:MySQL AB|MySQL AB]], which was bought by [[Company:Sun Microsystems|Sun Microsystems]] (now [[Company:Oracle Corporation|Oracle Corporation]]).<ref name="sunacquire">{{cite press release |title=Sun Microsystems Announces Completion of MySQL Acquisition; Paves Way for Secure, Open Source Platform to Power the Network Economy |publisher=Sun Microsystems |date=26 February 2008 |url=http://www.sun.com/aboutsun/pr/2008-02/sunflash.20080226.1.xml |access-date=17 September 2012 |archive-url=https://web.archive.org/web/20080228025123/http://www.sun.com/aboutsun/pr/2008-02/sunflash.20080226.1.xml |archive-date=28 February 2008}}</ref> In 2010, when Oracle acquired Sun, Widenius [[Software:Fork (software development)|forked]] the open-source MySQL project to create [[Software:MariaDB|MariaDB]].<ref>{{Cite web|last=Pearce|first=Rohan|date=2013-03-28|title=Dead database walking: MySQL's creator on why the future belongs to MariaDB|url=https://www.computerworld.com/article/3463901/dead-database-walking-mysql-s-creator-on-why-the-future-belongs-to-mariadb.html|url-status=dead|archive-url=https://web.archive.org/web/20200703115804/https://www.computerworld.com/article/3463901/dead-database-walking-mysql-s-creator-on-why-the-future-belongs-to-mariadb.html|archive-date=2020-07-03|access-date=2020-04-03|website=Computerworld|language=en|quote=The day the Sun purchase was announced, Widenius responded […] — he forked MySQL, launching MariaDB […]}}</ref>

MySQL has stand-alone clients that allow users to interact directly with a MySQL database using SQL, but more often, MySQL is used with other programs to implement applications that need relational database capability. MySQL is a component of the [[Software:LAMP (software bundle)|LAMP]] [[Web application|web application]] software stack (and others), which is an acronym for ''[[Software:Linux|Linux]], [[Software:Apache HTTP Server|Apache]], MySQL, [[Perl]]/[[Organization:PHP|PHP]]/[[Python (programming language)|Python]]''. MySQL is used by many database-driven web applications, including [[Software:Drupal|Drupal]], [[Software:Joomla|Joomla]], [[Software:PhpBB|phpBB]], and [[Software:WordPress|WordPress]].<ref>{{cite web|url=https://archive.nytimes.com/www.nytimes.com/external/idg/2010/03/08/08idg-wordpress-guns-for-web-content-management-duties-87311.html|title=WordPress Guns for Web Content Management Duties|quote=WordPress, created in 2003, uses a variety of open-source programs and open standards, such as PHP, MySQL, JavaScript, HTML and CSS.|first=Joab|last=Jackson|website={{wipe|The New York Times}}|date=March 8, 2010|access-date=August 24, 2023|language=en-US}}</ref> MySQL is also used by many popular websites, including [[Company:Facebook|Facebook]],<ref>{{cite web|url=http://blog.facebook.com/blog.php?post=7899307130|title=Keeping Up|last=Sobel|first=Jason|date=2007-12-21|work=The Facebook Blog|publisher=Facebook|url-status=dead|archive-url=https://web.archive.org/web/20090618191723/http://blog.facebook.com/blog.php?post=7899307130|archive-date=2009-06-18|access-date=2009-06-18|quote=[…] Facebook's data is stored in MySQL database servers […]}}</ref><ref>{{Cite web|url=https://engineering.fb.com/core-data/myrocks-a-space-and-write-optimized-mysql-database/|title=MyRocks: A space- and write-optimized MySQL database|last=Matsunobu|first=Yoshinori|date=2016-08-31|website=Facebook Engineering|language=en-US|url-status=live|archive-url=https://web.archive.org/web/20200307113840/https://engineering.fb.com/core-data/myrocks-a-space-and-write-optimized-mysql-database/|archive-date=2020-03-07|access-date=2020-03-07|quote=At Facebook we use MySQL to manage many petabytes of data, along with the InnoDB storage engine […]}}</ref> [[Social:Flickr|Flickr]],<ref>{{Cite web|url=http://code.flickr.net/2010/02/08/using-abusing-and-scaling-mysql-at-flickr/|title=Using, Abusing and Scaling MySQL at Flickr|last=Elliott-McCrea|first=Kellan|date=2010-02-08|website=code.flickr.com|access-date=2020-04-03|quote=[…] at Flickr, MySQL is our hammer, and we use it for nearly everything. It's our federated data store, our key-value store, and our document store.}}</ref> [[Software:MediaWiki|MediaWiki]],<ref>{{Cite web|url=https://www.mediawiki.org/wiki/Manual:MySQL|title=Manual:MySQL|website=www.mediawiki.org|publisher=MediaWiki, The Free Wiki Engine|access-date=2020-04-03|quote=The MySQL and MariaDB database engines are the most commonly-used database backends for MediaWiki.}}</ref> [[Company:Twitter|Twitter]],<ref>{{Cite web|url=https://blog.twitter.com/engineering/en_us/topics/infrastructure/2017/the-infrastructure-behind-twitter-scale.html|title=The Infrastructure Behind Twitter: Scale|last=Hashemi|first=Mazdak|date=2017-01-19|website=blog.twitter.com|language=en-us|access-date=2020-04-03|quote=SQL: This includes MySQL, PostgreSQL and Vertica. MySQL/PosgreSQL are used where we need strong consistency […]}}</ref> and [[Company:YouTube|YouTube]].<ref>{{cite book|author1=Mehta, Chintan|author2=K Bhavsar, Ankit|author3=Oza, Hetal|author4=Shah, Subhash |date= February 15, 2018 |title=MySQL 8 Administrator's Guide: Effective Guide to Administering High-performance MySQL 8 Solutions|url=https://books.google.com/books?id=EJdMDwAAQBAJ&dq=%22YouTube%22+%2B+%22MySQL%22&pg=PA32|publisher=Packt Publishing|page=32|isbn=9781788393843}}</ref>

==Overview==
MySQL is written in [[C (programming language)|C]] and [[C++]]. Its SQL parser is written in [[Software:Yacc|yacc]], but it uses a home-brewed [[Lexical analysis|lexical analyzer]].<ref>{{cite web |date=4 March 2009 |title=MySQL Internals Manual |url=http://dev.mysql.com/doc/internals/en/index.html |access-date=8 June 2009 |website=dev.mysql.com }}</ref> MySQL works on many system platforms, including AIX, BSDi, [[Software:FreeBSD|FreeBSD]], [[Software:HP-UX|HP-UX]], [[Software:ArcaOS|ArcaOS]], [[Software:EComStation|eComStation]], [[Software:IBM i|IBM i]], [[Software:IRIX|IRIX]], [[Software:Linux|Linux]], [[Software:MacOS|macOS]], [[Software:Microsoft Windows|Microsoft Windows]], [[Software:NetBSD|NetBSD]], Novell NetWare, [[Organization:OpenBSD|OpenBSD]], [[Software:OpenSolaris|OpenSolaris]], OS/2 Warp, [[QNX]], [[Software:Solaris (operating system)|Oracle Solaris]], [[Software:Symbian|Symbian]], [[Software:SunOS|SunOS]], SCO OpenServer, SCO UnixWare, Sanos and [[Software:Tru64 UNIX|Tru64]]. A port of MySQL to [[Software:OpenVMS|OpenVMS]] also exists.<ref>{{cite web |date=2011-03-30 |title=MySQL for OpenVMS |url=http://www.vmsmysql.org/ |url-status=dead |access-date=2014-01-16 |publisher=vmsmysql.org |archive-date=12 May 2014 |archive-url=https://web.archive.org/web/20140512060500/http://www.vmsmysql.org/ }}</ref>

The MySQL server software itself and the client libraries use dual-licensing distribution. They are offered under [[Software:GNU General Public License|GPL]] version 2, or a proprietary license.<ref>{{Cite web |date=July 2010 |title=Commercial License for OEMs, ISVs and VARs |url=https://www.mysql.com/about/legal/licensing/oem/ |access-date=2020-04-03 |website=www.mysql.com |quote=Oracle provides its MySQL database server […] under a dual license model […] Oracle makes its MySQL database server […] available under the GPLv2 […]}}</ref>

Support can be obtained from the official manual.<ref>[http://dev.mysql.com/doc/refman/5.5/en/index.html MySQL Support Manual], MySQL Developers</ref> Free support additionally is available in different IRC channels and forums. Oracle offers paid support via its MySQL Enterprise products. They differ in the scope of services and in price. Additionally, a number of third party organisations exist to provide support and services.

MySQL has received positive reviews, and reviewers noticed it "performs extremely well in the average case" and that the "developer interfaces are there, and the documentation (not to mention feedback in the real world via Web sites and the like) is very, very good".<ref>[http://review.techworld.com/applications/346/mysql-50-open-source-database/ Review of MySQL Server 5.0], Techworld.com, November 2005</ref> It has also been tested to be a "fast, stable and true multi-user, multi-threaded SQL database server".<ref>[http://community.linuxmint.com/software/view/mysql-server MySQL Server Review], LinuxMint.com</ref>

==History==
[[File:Monty-Widenius-David-Axmark-MySQL-2003-05-09.jpg|thumb|right|David Axmark (left) and Michael "Monty" Widenius, founders of MySQL AB, in 2003]]

MySQL was created by a Swedish company, [[Company:MySQL AB|MySQL AB]], founded by Swedes David Axmark, Allan Larsson and Finnish Michael "Monty" Widenius.
Original development of MySQL by Widenius and Axmark began in 1994.<ref>{{cite web|url=http://www.opensourcereleasefeed.com/interview/show/five-questions-with-michael-widenius-founder-and-original-developer-of-mysql |archive-url=https://web.archive.org/web/20090313160628/http://www.opensourcereleasefeed.com/interview/show/five-questions-with-michael-widenius-founder-and-original-developer-of-mysql |archive-date=2009-03-13 |title=Five Questions With Michael Widenius – Founder And Original Developer of MySQL |publisher=opensourcereleasefeed.com |access-date=13 October 2012}}</ref> The first version of MySQL appeared on 23 May 1995. It was initially created for personal usage from [[Software:MSQL|mSQL]] based on the low-level language [[ISAM]], which the creators considered too slow and inflexible. They created a new [[SQL]] interface, while keeping the same [[API]] as mSQL. By keeping the API consistent with the mSQL system, many developers were able to use MySQL instead of the (proprietarily licensed) mSQL antecedent.<ref>{{cite web |last=Pachev |first=Sasha |title=MySQL History and Architecture |url=https://www.oreilly.com/library/view/understanding-mysql-internals/0596009577/ch01.html |access-date=5 December 2020 |website=www.oreilly.com |language=en-US}}</ref>

===Milestones===
Additional milestones in MySQL development included:
* First internal release on 23 May 1995
* Version 3.19: End of 1996, from www.tcx.se
* Version 3.20: January 1997
* Windows version was released on 8 January 1998 for Windows 95 and NT
* Version 3.21: production release 1998, from www.mysql.com
* Version 3.22: alpha, beta from 1998
* Version 3.23: beta from June 2000, production release 22 January 2001<ref>{{cite web|url=http://www.mysql.com/news/article-54.html |archive-url=https://web.archive.org/web/20010815175526/http://www.mysql.com/news/article-54.html |archive-date=15 August 2001 |title=MySQL 3.23 Declared Stable}}</ref>
* Version 4.0: beta from August 2002, production release March 2003 (unions).
* Version 4.1: beta from June 2004, production release October 2004 (R-trees and [[B-tree]]s, subqueries, prepared statements).
* Version 5.0: beta from March 2005, production release October 2005 (cursors, stored procedures, triggers, views, [[Database transaction|XA transactions]]).
** The developer of the Federated Storage Engine states that "The Federated Storage Engine is a [[Proof of concept|proof-of-concept]] storage engine",<ref>{{cite web|url=http://capttofu.livejournal.com/5798.html |title=Capttofu: FederatedX Pluggable Storage Engine Released! |publisher=Capttofu.livejournal.com |access-date=3 April 2009 |url-status=dead |archive-url=https://web.archive.org/web/20110813040439/http://capttofu.livejournal.com/5798.html |archive-date=13 August 2011}}</ref> but the main distributions of MySQL version 5.0 included it and turned it on by default. Documentation of some of the short-comings appears in "MySQL Federated Tables: The Missing Manual".<ref>{{cite web |date=8 October 2006 |title=MySQL Federated Tables: The Missing Manual |url=http://www.oreillynet.com/pub/a/databases/2006/08/10/mysql-federated-tables.html |url-status=dead |access-date=1 February 2012 |publisher=O'Reilly Media |archive-date=13 August 2006 |archive-url=https://web.archive.org/web/20060813161552/http://www.oreillynet.com/pub/a/databases/2006/08/10/mysql-federated-tables.html }}</ref>
* [[Company:Sun Microsystems|Sun Microsystems]] acquired MySQL AB in 2008.<ref>{{cite web |last=Arrington |first=Michael |date=2008-01-16 |title=Sun Picks Up MySQL For $1 Billion; Open Source Is A Legitimate Business Model |url=https://techcrunch.com/2008/01/16/sun-picks-up-mysql-for-1-billion-open-source-is-a-legitimate-business-model/ |access-date=13 October 2012 |website=www.techcrunch.com}}</ref>
* Version 5.1: production release 27 November 2008 (event scheduler, [[Software:Partition (database)|partitioning]], plugin API, row-based replication, [[Server log|server log]] tables)
** Version 5.1 contained 20 known crashing and wrong result bugs in addition to the 35 present in version 5.0 ''(almost all fixed as of release 5.1.51)''.<ref>{{cite web |url=http://www.planetmysql.org/entry.php?id=16232 |title=Archives – Oops, we did it again (MySQL 5.1 released as GA with crashing bugs) |publisher=Planet MySQL |date=29 November 2008 |access-date=5 February 2013 |url-status=dead |archive-url=https://web.archive.org/web/20081230032718/http://www.planetmysql.org/entry.php?id=16232 |archive-date=30 December 2008}}</ref>
** MySQL 5.1 and 6.0-alpha showed poor performance when used for data warehousing{{snd}} partly due to its inability to utilize multiple CPU cores for processing a single query.<ref>{{cite web |author=Zaitsev |first=Peter |date=2008-04-10 |title=TPC-H Run on MySQL 5.1 and 6.0 |url=http://www.mysqlperformanceblog.com/2008/04/10/tpc-h-run-on-mysql-51-and-60/ |access-date=8 June 2009 |website=MySQL Performance Blog}}</ref>
* Oracle acquired Sun Microsystems on 27 January 2010.<ref>{{cite press release|url=http://www.oracle.com/us/corporate/press/044428 |title=Oracle Completes Acquisition of Sun|publisher=Oracle |date=27 January 2010 |access-date=1 February 2012}}</ref><ref>{{cite web |title=Overview and Frequently Asked Questions |url=https://www.oracle.com/us/assets/038563.pdf |url-status=dead |access-date=8 February 2016 |archive-date=11 February 2016 |archive-url=https://web.archive.org/web/20160211190401/https://www.oracle.com/us/assets/038563.pdf }}</ref><ref>{{cite news |last=Krill |first=Paul |date=27 January 2010 |title=Oracle's ambitious plans for integrating Sun's technology |work=InfoWorld |url=http://www.infoworld.com/article/2627785/m-a/oracle-s-ambitious-plans-for-integrating-sun-s-technology.html |access-date=2018-05-08}}</ref>
* The day Oracle announced the purchase of Sun, Michael "Monty" Widenius forked MySQL, launching [[Software:MariaDB|MariaDB]], and took a swath of MySQL developers with him.<ref name="dead">{{cite news |last=Pearce |first=Rohan |date=28 March 2013 |title=Dead database walking: MySQL's creator on why the future belongs to MariaDB |work=Computerworld |url=https://www2.computerworld.com.au/article/457551/dead_database_walking_mysql_creator_why_future_belongs_mariadb/ |access-date=2020-10-02}}</ref>
[[File:Geir Høydalsvik at Percona Live Europe 2018 3.jpg|thumb|right|Geir Høydalsvik, current Senior Software Development Director for MySQL at Oracle in 2018]]
* MySQL Server 5.5 was generally available ({{as of|2010|12|lc=on}}). Enhancements and features include:
** The default storage engine is [[Software:InnoDB|InnoDB]], which supports transactions and referential integrity constraints.
** Improved InnoDB I/O subsystem<ref>{{cite web|url=http://dev.mysql.com/doc/refman/5.5/en/innodb-io-changes.html|title=InnoDB I/O Subsystem Changes|publisher=dev.mysql.com|access-date=1 February 2012|url-status=dead|archive-url=https://web.archive.org/web/20120210005904/http://dev.mysql.com/doc/refman/5.5/en/innodb-io-changes.html|archive-date=10 February 2012}}</ref>
** Improved [[Symmetric multiprocessing|SMP]] support<ref>{{cite web |url=http://dev.mysql.com/doc/refman/5.5/en/smp-improvements.html |title=Scalability Improvements |publisher=dev.mysql.com |access-date=1 February 2012 |url-status=dead |archive-url=https://web.archive.org/web/20120210005914/http://dev.mysql.com/doc/refman/5.5/en/smp-improvements.html |archive-date=10 February 2012}}</ref>
** Semisynchronous replication.
** SIGNAL and RESIGNAL statement in compliance with the SQL standard.
** Support for supplementary Unicode character sets utf16, utf32, and utf8mb4.{{efn|name=utf8mb4}}
** New options for user-defined partitioning.
* MySQL Server 6.0.11-alpha was announced<ref>{{cite web |title=MySQL Lists: packagers: MySQL 6.0.11 Alpha has been released! |url=http://lists.mysql.com/packagers/418 |url-status=dead |access-date=1 February 2012 |website= |publisher=Lists.mysql.com |archive-date=23 March 2012 |archive-url=https://web.archive.org/web/20120323235154/http://lists.mysql.com/packagers/418 }}</ref> on 22 May 2009 as the last release of the 6.0 line. Future MySQL Server development uses a New Release Model. Features developed for 6.0 are being incorporated into future releases.
* The general availability of MySQL&nbsp;5.6 was announced in February 2013.<ref>{{Cite web |url=http://www.oracle.com/us/corporate/press/1904335 |title=Oracle Announces General Availability of MySQL 5.6 |access-date=13 June 2018 |archive-date=13 June 2018 |archive-url=https://web.archive.org/web/20180613191021/http://www.oracle.com/us/corporate/press/1904335 |url-status=dead }}</ref> New features included performance improvements to the query optimizer, higher transactional throughput in InnoDB, new [[NoSQL]]-style memcached APIs, improvements to partitioning for querying and managing very large tables, {{mono|TIMESTAMP}} column type that correctly stores milliseconds, improvements to replication, and better performance monitoring by expanding the data available through the {{mono|PERFORMANCE_SCHEMA}}.<ref>{{cite web|url=http://dev.mysql.com/tech-resources/articles/whats-new-in-mysql-5.6.html|title=What's New in MySQL 5.6|publisher=MySQL Developer Zone|access-date=21 April 2011|url-status=dead|archive-url=https://web.archive.org/web/20110423052507/http://dev.mysql.com/tech-resources/articles/whats-new-in-mysql-5.6.html|archive-date=23 April 2011}}</ref> The InnoDB storage engine also included support for full-text search and improved group commit performance.
* The general availability of MySQL&nbsp;5.7 was announced in October 2015.<ref>{{cite web |title=Oracle Announces General Availability of MySQL 5.7 |url=https://www.oracle.com/corporate/pressrelease/mysql-5-7-ga-101915.html |url-status=dead |access-date=1 November 2015 |publisher=Oracle |archive-date=23 January 2016 |archive-url=https://web.archive.org/web/20160123022325/https://www.oracle.com/corporate/pressrelease/mysql-5-7-ga-101915.html }}</ref> As of MySQL 5.7.8, August 2015,<ref>{{Cite web |title=MySQL :: MySQL 5.7 Release Notes :: Changes in MySQL 5.7.8 (2015-08-03, Release Candidate) |url=https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-8.html#mysqld-5-7-8-json |access-date=10 October 2019 |website=dev.mysql.com}}</ref> MySQL supports a native [[JSON]] data type defined by RFC 7159.<ref>{{Cite journal|url=https://dev.mysql.com/doc/refman/5.7/en/json.html|title=MySQL :: MySQL 5.7 Reference Manual :: 11.6 The JSON Data Type|website=dev.mysql.com|year=2014 |doi=10.17487/RFC7159 |access-date=10 October 2019|rfc=7159|editor-last1=Bray |editor-first1=T |last1=Bray |first1=T. |doi-access=free }}</ref>
* MySQL Server 8.0 was announced in April 2018,<ref>{{Cite web|url=https://blogs.oracle.com/mysql/announcing-general-availability-of-mysql-80|title=Announcing General Availability of MySQL 8.0|first=Mike|last=Frank|website=blogs.oracle.com|access-date=10 October 2019}}</ref> including NoSQL Document Store, atomic and crash safe DDL sentences and [[JSON]] Extended syntax, new functions, such as JSON table functions, improved sorting, and partial updates. Previous MySQL Server 8.0.0-dmr (Milestone Release) was announced 12 September 2016.<ref>{{cite web|url=http://lists.mysql.com/announce/1106 |title=8.0.0-dmr (Milestone Release) |access-date=12 September 2016}}</ref>
* MySQL was declared DBMS of the year 2019 from the [[Software:DB-Engines ranking|DB-Engines ranking]]<ref>{{cite web |last=Gelbmann |first=Matthias |date=2020-01-03 |title=MySQL is the DBMS of the Year 2019 |url=https://db-engines.com/en/blog_post/83 |access-date=7 January 2020 |website=db-engines.com |publisher=DB-Engines}}</ref>

=== Release history ===
{| class="wikitable"
|-
! Release
! General availability
! Latest minor version
! Latest release
! End of support<ref>{{Cite web|url=http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf|title=Oracle Lifetime Support Policy|access-date=10 October 2019}}</ref><ref>{{Cite web|url=https://dev.mysql.com/blog-archive/introducing-mysql-innovation-and-long-term-support-lts-versions/|title= Introducing MySQL Innovation and Long-Term Support (LTS) versions |access-date=16 October 2023}}</ref>
|-
| {{Version |o |5.1 LTS}}
| {{Release date and age|df=yes|2008|11|14}}<ref>{{cite web|url=https://docs.oracle.com/cd/E17952_01/mysql-5.1-en/faqs-general.html|title=A.1 MySQL 5.1 FAQ: General|website=docs.oracle.com|access-date=2 August 2017}}</ref>
| style="text-align:center" | 5.1.73<ref>{{cite web|url=https://docs.oracle.com/cd/E17952_01/mysql-5.1-relnotes-en/news-5-1-73.html|title=2 Changes in MySQL 5.1.73 (2013-12-03)|website=docs.oracle.com|access-date=2020-04-28}}</ref>
| 2013-12-03
| Dec 2013
|-
| {{Version |o |5.5 LTS}}
| {{Release date and age|df=yes|2010|12|03}}<ref>{{cite web|url=https://dev.mysql.com/doc/relnotes/mysql/5.5/en/|title=MySQL: MySQL 5.5 Release Notes|website=dev.mysql.com|access-date=15 January 2018}}</ref>
| style="text-align:center" | 5.5.62<ref>{{cite web|url=https://docs.oracle.com/cd/E17952_01/mysql-5.5-relnotes-en/news-5-5-62.html|title=2 Changes in MySQL 5.5.62 (2018-10-22, General availability)|website=docs.oracle.com|access-date=2020-04-28}}</ref>
| 2018-10-22
| Dec 2018
|-
| {{Version |o |5.6 LTS}}
| {{Release date and age|df=yes|2013|02|05}}<ref>{{cite web|url=https://dev.mysql.com/doc/relnotes/mysql/5.6/en/|title=MySQL: MySQL 5.6 Release Notes|website=dev.mysql.com|access-date=15 January 2018}}</ref>
| style="text-align:center" | 5.6.51<ref>{{Cite web|url=https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-51.html|title=MySQL :: MySQL 5.6 Release Notes :: Changes in MySQL 5.6.51 (2021-01-20, General Availability)|website=dev.mysql.com|access-date=2021-03-04}}</ref>
| 2021-01-20
| Feb 2021
|-
| {{Version |o |5.7 LTS}}
| {{Release date and age|df=yes|2015|10|21}} <ref>{{cite web|url=https://dev.mysql.com/doc/relnotes/mysql/5.7/en/|title=MySQL: MySQL 5.7 Release Notes|website=dev.mysql.com|access-date=15 January 2018}}</ref>
| style="text-align:center" | 5.7.44<ref>{{Cite web |title=Changes in MySQL 5.7.44 (2023-10-25, General Availability) |url=https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html |access-date=2023-10-25 |website=dev.mysql.com}}</ref>
| 2023-10-25
| Oct 2023
|-
| {{Version |co |8.0 LTS}}
| {{Release date and age|df=yes|2018|04|19}} <ref>{{Cite web|url=https://mysqlserverteam.com/whats-new-in-mysql-8-0-generally-available/|title=What's New in MySQL 8.0? (Generally Available)|first=Geir|last=Hoydalsvik|date=19 April 2018|access-date=10 October 2019}}</ref>
| style="text-align:center; white-space:nowrap" | 8.0.36<ref>{{Cite web |title=MySQL :: MySQL 8.0 Release Notes :: Changes in MySQL 8.0.36 (2024-01-16, General Availability) |url=https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-36.html |access-date=2024-01-16 |website=dev.mysql.com}}</ref>
| 2024-01-16
| Apr 2026
|-
| {{Version |o |8.1}}
| {{Release date and age|df=yes|2023|07|18}}<ref>{{Cite web|url=https://dev.mysql.com/doc/refman/8.1/en/mysql-nutshell.html|title=What Is New in MySQL 8.1| date=18 July 2023|access-date=16 October 2023}}</ref>
| style="text-align:center" | 8.1.26<ref>{{Cite web|url=https://dev.mysql.com/doc/relnotes/mysql/8.1/en/news-8-1-0.html|title= Changes in MySQL 8.1.0 (2023-07-18, Innovation Release)| date=18 July 2023|access-date=16 October 2023}}</ref>
| 2023-07-18
| Oct 2023
|-
| {{Version |o |8.2}}
| {{Release date and age|df=yes|2023|10|25}}<ref>{{Cite web|url=https://dev.mysql.com/doc/refman/8.2/en/mysql-nutshell.html|title=What Is New in MySQL 8.2| date=25 October 2023|access-date=26 October 2023}}</ref>
| style="text-align:center" | 8.2.0<ref>{{Cite web|url=https://dev.mysql.com/doc/relnotes/mysql/8.2/en/news-8-2-0.html|title= Changes in MySQL 8.2.0 (2023-08-25, Innovation Release)| date=25 October 2023|access-date=26 October 2023}}</ref>
| 2023-10-25
| Jan 2024
|-
| {{Version |c |8.3}}
| {{Release date and age|df=yes|2024|01|16}}<ref>{{Cite web|url=https://dev.mysql.com/doc/refman/8.3/en/mysql-nutshell.html|title=What Is New in MySQL 8.3| date=16 January 2024|access-date=16 January 2024}}</ref>
| style="text-align:center" | 8.3.0<ref>{{Cite web|url=https://dev.mysql.com/doc/relnotes/mysql/8.3/en/news-8-3-0.html|title= Changes in MySQL 8.3.0 (2024-01-16, Innovation Release)| date=16 January 2024|access-date=16 January 2024}}</ref>
| 2024-01-16
| Apr 2024
|-
| colspan="5" | <small>{{Version |l |show=111100}}</small>
|}

Work on version 6 stopped after the Sun Microsystems acquisition. The MySQL Cluster product uses version 7. The decision was made to jump to version 8 as the next major version number.<ref>{{cite web|url=https://opensource.com/article/17/2/mysql-8-coming|title=MySQL 8 is coming|website=opensource.com|access-date=27 April 2018}}</ref>

===Legal disputes and acquisitions===
On 15 June 2001, NuSphere sued MySQL AB, TcX DataKonsult AB and its original authors Michael ("Monty") Widenius and David Axmark in U.S District Court in Boston for "breach of contract, tortious interference with third party contracts and relationships and unfair competition".<ref>{{cite mailing list |url=http://no.spam.ee/~tonu/mysql/tombasil.txt |title=Eyewitness account: "Monty Widenius, International Fugitive" |date=4 September 2001 |access-date=16 September 2012 |mailing-list=MySQL Life |last=Basil |first=Tom |url-status=dead |archive-url=https://web.archive.org/web/20131004214013/http://no.spam.ee/~tonu/mysql/tombasil.txt |archive-date=4 October 2013}}</ref><ref>{{cite web |url=http://mysql.com/news/article-75.html |title=FAQ on MySQL vs. NuSphere Dispute |date=13 July 2001 |publisher=MySQL AB |access-date=16 September 2012 |archive-url=https://web.archive.org/web/20010717185237/http://mysql.com/news/article-75.html |archive-date=17 July 2001}}</ref>

In 2002, MySQL AB sued Progress NuSphere for [[Copyright infringement|copyright]] and trademark infringement in United States district court. NuSphere had allegedly violated MySQL AB's copyright by linking MySQL's GPL'ed code with NuSphere Gemini table without being in compliance with the license.<ref>{{cite web |url=http://www.fsf.org/press/mysql-affidavit.html|archive-url=https://web.archive.org/web/20050207084821/http://www.fsf.org/press/mysql-affidavit.html|archive-date=2005-02-07|title=Affidavit of Eben Moglen on Progress Software vs. MySQL AB Preliminary Injunction Hearing}}</ref> After a preliminary hearing before Judge Patti Saris on 27 February 2002, the parties entered settlement talks and eventually settled.<ref>{{cite court |litigants=Progress Software Corporation v. MySQL AB |vol=195 |reporter=F. Supp. 2d |opinion=328 |court=D. Mass. |year=2002 |url=https://scholar.google.com/scholar_case?case=13584730711160488510 |access-date=16 September 2012}}</ref> After the hearing, [[Organization:Free Software Foundation|FSF]] commented that "Judge Saris made clear that she sees the GNU GPL to be an enforceable and binding license."<ref>{{cite press release |title=Judge Saris defers GNU GPL Questions for Trial in MySQL vs. Progress Software |publisher=Free Software Foundation |date=1 March 2002 |url=https://www.gnu.org/press/2002-03-01-pi-MySQL.html |access-date=16 September 2012}}</ref>

In October 2005, Oracle Corporation acquired Innobase OY, the {{wipe|Finland}} company that developed the third-party InnoDB storage engine that allows MySQL to provide such functionality as transactions and [[Foreign key|foreign key]]s. After the acquisition, an Oracle press release mentioned that the contracts that make the company's software available to [[Company:MySQL AB|MySQL AB]] would be due for renewal (and presumably renegotiation) some time in 2006.<ref>{{cite press release |title=Oracle Announces the Acquisition of Open Source Software Company, Innobase |publisher=Oracle |date=7 October 2005 |url=http://www.oracle.com/us/corporate/press/016679_EN |access-date=16 September 2012 |archive-url=https://web.archive.org/web/20110720225615/http://www.oracle.com/us/corporate/press/016679_EN |archive-date=20 July 2011 |url-status=live}}</ref> During the MySQL Users Conference in April 2006, MySQL AB issued a press release that confirmed that MySQL AB and Innobase OY agreed to a "multi-year" extension of their licensing agreement.<ref>{{cite press release |title=MySQL to Promote New Open Source DB Engines from its Partners and Dev Community |publisher=MySQL AB |date=26 April 2006 |url=http://www.businesswire.com/news/home/20060426005579/en/MySQL-AB-Promote-Open-Source-Database-Engines |access-date=16 September 2012 |archive-url=https://web.archive.org/web/20110623190958/http://www.mysql.com/news-and-events/generate-article.php?id=2006_21 |archive-date=23 June 2011|url-status=live}}</ref>

In February 2006, Oracle Corporation acquired [[Company:Sleepycat Software|Sleepycat Software]],<ref>{{cite web |url=http://www.informationweek.com/software/showArticle.jhtml?articleID=180200853 |title=Oracle Buys Sleepycat, Is JBoss Next? |last=Babcock |first=Charles |date=14 February 2006 |work=InformationWeek |publisher=CPM Media |access-date=16 September 2012 |archive-date=15 May 2011 |archive-url=https://web.archive.org/web/20110515023408/http://www.informationweek.com/software/showArticle.jhtml?articleID=180200853 |url-status=dead }}</ref> makers of the [[Software:Berkeley DB|Berkeley DB]], a database engine providing the basis for another MySQL storage engine. This had little effect, as Berkeley DB was not widely used, and was dropped (due to lack of use) in MySQL 5.1.12, a pre-GA release of MySQL 5.1 released in October 2006.<ref>{{cite web |url=http://dev.mysql.com/doc/refman/5.1/en/news-5-1-12.html |title=Changes in MySQL 5.1.12 |date=24 October 2006 |work=MySQL 5.1 Reference Manual |publisher=MySQL AB |access-date=16 September 2012 |url-status=dead |archive-url=https://web.archive.org/web/20121020222957/http://dev.mysql.com/doc/refman/5.1/en/news-5-1-12.html |archive-date=20 October 2012}}</ref>

In January 2008, Sun Microsystems bought MySQL AB for $1 billion.<ref>{{cite press release|title=Sun Microsystems Announces Agreement to Acquire MySQL, Developer of the World's Most Popular Open Source Database |publisher=Sun Microsystems |date=16 January 2008 |url=http://www.businesswire.com/news/home/20080116005349/en/Sun-Microsystems-Announces-Agreement-Acquire-MySQL-Developer |archive-url=https://web.archive.org/web/20110718044718/http://mysql.com/news-and-events/sun-to-acquire-mysql.html |archive-date=18 July 2011 |access-date=16 September 2012 |url-status=dead}}</ref>

In April 2009, Oracle Corporation entered into an agreement to purchase Sun Microsystems,<ref>{{cite press release |title=Oracle to Buy Sun |publisher=Sun Microsystems |date=20 April 2009 |url=http://www.businesswire.com/news/home/20090420005760/en/Oracle-Buy-Sun |access-date=16 September 2012 |archive-url=https://web.archive.org/web/20090422033454/http://www.sun.com/aboutsun/pr/2009-04/sunflash.20090420.1.xml |archive-date=22 April 2009|url-status=live}}</ref> then owners of MySQL copyright and trademark. Sun's board of directors unanimously approved the deal. It was also approved by Sun's shareholders, and by the U.S. government on 20 August 2009.<ref>{{cite news |title=Oracle wins U.S. approval to buy Sun Microsystems |last1=Thomasch |first1=Paul |last2=Finkle |first2=Jim |date=20 August 2009 |url=https://www.reuters.com/article/sun-oracle/update-1-oracle-wins-u-s-approval-to-buy-sun-microsystems-idUSN2053486920090820 |work=Reuters |access-date=2 March 2020 }}</ref> On 14 December 2009, Oracle pledged to continue to enhance MySQL<ref>{{cite web |url=http://news.cnet.com/8301-1001_3-10414686-92.html |title=Oracle pledges to play well with MySQL |last=Whitney |first=Lance |date=14 December 2009 |website=CNET |archive-url=https://web.archive.org/web/20160312052010/http://www.cnet.com/news/oracle-pledges-to-play-well-with-mysql/|archive-date=12 March 2016|access-date=16 September 2012}}</ref> as it had done for the previous four years.

A movement against Oracle's acquisition of MySQL AB, to "Save MySQL"<ref>{{cite web |title=Help saving MySQL |url=http://monty-says.blogspot.com/2009/12/help-saving-mysql.html |last=Michael |first=Widenius |date=12 December 2009 |work=Monty Says |publisher=Google |access-date=16 September 2012}}</ref> from Oracle was started by one of the MySQL AB founders, Monty Widenius. The petition of 50,000+ developers and users called upon the European Commission to block approval of the acquisition. At the same time, some Free Software [[Social:Opinion leadership|opinion leaders]] (including Pamela Jones of [[Software:Groklaw|Groklaw]], Jan Wildeboer and Carlo Piana, who also acted as co-counsel in the merger regulation procedure) advocated for the unconditional approval of the merger.<ref>{{cite web |url=https://www.softwarefreedom.org/news/2009/dec/04/software-freedom-law-center-submits-opinion-oracle/ |title=The Software Freedom Law Center Submits an Opinion on the Oracle/Sun Merger to the EC |date=2009-12-04 |website=www.softwarefreedom.org |publisher=Software Freedom Law Center |access-date=2018-02-01 }}</ref><ref>{{cite web |url=https://www.infoworld.com/article/2630216/database/many-open-sourcers-back-an-oracle-takeover-of-mysql.html |title=Many open-sourcers back an Oracle takeover of MySQL |last=Lai |first=Eric |date=2009-10-28 |website=www.infoworld.com |publisher=InfoWorld |access-date=2018-02-01 }}</ref><ref>{{cite web |url=http://jan.wildeboer.net/2010/01/why-i-will-not-sign-the-mysql-petition/ |title=Why I will not sign the MySQL petition |last=Wildeboer |first=Jan |date=2010-01-05 |website=jan.wildeboer.net |access-date=2018-02-01 }}</ref> As part of the negotiations with the European Commission, Oracle committed that MySQL server will continue until at least 2015 to use the dual-licensing strategy long used by MySQL AB, with proprietary and GPL versions available. The antitrust of the EU had been "pressuring it to divest MySQL as a condition for approval of the merger". But the US Department of Justice, at the request of Oracle, pressured the EU to approve the merger unconditionally.<ref>{{cite web |url=http://www.pcworld.com/article/239132/wikileaks_cable_offers_new_insights_into_oraclesun_deal.html |title=Wikileaks Cable Offers New Insights into Oracle-Sun Deal |last=Kanaracus |first=Chris |date=30 August 2011 |work=PC World |access-date=16 September 2012}}</ref> The European Commission eventually unconditionally approved Oracle's acquisition of MySQL AB on 21 January 2010.<ref>{{cite press release |title=Mergers: Commission clears Oracle's proposed acquisition of Sun Microsystems |publisher=European Union |date=21 January 2010 |url=http://europa.eu/rapid/pressReleasesAction.do?reference=IP/10/40 |access-date=16 September 2012}}</ref>

In January 2010, before Oracle's acquisition of MySQL AB, Monty Widenius started a GPL-only [[Software:Fork (software development)|fork]], [[Software:MariaDB|MariaDB]]. MariaDB is based on the same code base as MySQL server 5.5 and aims to maintain compatibility with Oracle-provided versions.<ref>{{Cite web|url=https://mariadb.com/kb/en/mariadb-vs-mysql-compatibility/|title=MariaDB versus MySQL - Compatibility|website=MariaDB KnowledgeBase|access-date=2020-04-03|quote=MariaDB versions function as a "drop-in replacement" for the equivalent MySQL version, with some limitations.}}</ref>

==Features==
MySQL is offered under two different editions: the [[Open-source software|open source]] MySQL Community Server<ref>{{Cite web|url=https://www.mysql.com/products/community/|title=MySQL Community Edition|website=www.mysql.com|access-date=2020-04-03|quote=MySQL Community Edition is the freely downloadable version […]. It is available under the GPL license […]}}</ref> and the proprietary [[Software:MySQL Enterprise|Enterprise Server]].<ref>{{cite web | url=http://www.mysql.com/products/which-edition.html | title=Which Should I Use: MySQL Enterprise or MySQL Community Server? | publisher=MySQL AB | access-date=8 April 2009 | url-status=dead | archive-url=https://web.archive.org/web/20090409055908/http://www.mysql.com/products/which-edition.html | archive-date=9 April 2009}}</ref> MySQL Enterprise Server is differentiated by a series of proprietary extensions which install as server plugins, but otherwise shares the version numbering system and is built from the same code base.

Major features as available in MySQL 5.6:

* A broad subset of [[SQL:1999|ANSI SQL 99]], as well as extensions
* Cross-platform support
* [[Stored procedure]]s, using a procedural language that closely adheres to SQL/PSM<ref name="HarrisonFeuerstein2008">{{cite book|author1=Guy Harrison|author2=Steven Feuerstein|title=MySQL Stored Procedure Programming|url=https://books.google.com/books?id=YpeP0ok0cO4C&pg=PT75|year=2008|publisher=O'Reilly Media|isbn=978-0-596-10089-6|page=49}}</ref>
* [[Database trigger|Triggers]]
* [[Cursor (databases)|Cursors]]
* Updatable [[View (SQL)|views]]
* Online Data Definition Language (DDL) when using the InnoDB Storage Engine.
* [[Information schema]]
* Performance Schema that collects and aggregates statistics about server execution and query performance for monitoring purposes.<ref>{{cite web | url=https://www.datadoghq.com/blog/monitoring-rds-mysql-performance-metrics/ | title=Monitoring RDS MySQL performance metrics | publisher=[[Company:Datadog|Datadog]] | date=2015-10-20 | access-date=14 December 2015}}</ref>
* A set of SQL Mode options to control [[Run time (program lifecycle phase)|runtime]] behavior, including a strict mode to better adhere to SQL standards.
* X/Open XA distributed transaction processing (DTP) support; [[Two-phase commit protocol|two phase commit]] as part of this, using the default [[Software:InnoDB|InnoDB]] storage engine
* Transactions with [[Savepoint|savepoint]]s when using the default InnoDB Storage Engine. The NDB Cluster Storage Engine also supports transactions.
* [[ACID]] compliance when using InnoDB and NDB Cluster Storage Engines<ref>{{cite web |url=http://dev.mysql.com/doc/innodb/1.1/en/glossary.html#glos_acid | archive-url=https://web.archive.org/web/20101225160519/http://dev.mysql.com/doc/innodb/1.1/en/glossary.html#glos_acid | url-status=dead | archive-date=25 December 2010 | title=MySQL :: InnoDB 1.1 for MySQL 5.5 User's Guide :: C InnoDB Glossary :: ACID | access-date=5 January 2011 }}</ref>
* SSL support
* Query [[Cache (computing)|caching]]
* Sub-SELECTs (i.e. nested SELECTs)
* Built-in [[Software:Database replication|replication]] support
** Asynchronous replication: master-slave from one master to many slaves<ref>{{cite web|url=http://dev.mysql.com/doc/refman/5.6/en/replication.html|title=Replication|publisher=MySQL}}</ref><ref>{{Cite web|url=https://mariadb.com/kb/en/library/high-availability-performance-tuning-mariadb-replication/|title=MariaDB Replication|website=MariaDB KnowledgeBase|access-date=2019-03-09}}</ref> or many masters to one slave<ref>{{Cite web|url=https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source.html|title=MySQL :: MySQL 5.7 Reference Manual :: 16.1.4 MySQL Multi-Source Replication|website=dev.mysql.com|access-date=2019-03-09}}</ref>
** Semi synchronous replication: Master to slave replication where the master waits on replication<ref>{{Cite web|url=https://dev.mysql.com/doc/refman/5.7/en/replication-semisync.html|title=MySQL :: MySQL 5.7 Reference Manual :: 16.3.9 Semisynchronous Replication|website=dev.mysql.com|access-date=2019-03-09}}</ref><ref>{{Cite web|url=https://mariadb.com/kb/en/library/semisynchronous-replication/|title=Semisynchronous Replication|website=MariaDB KnowledgeBase|access-date=2019-03-09}}</ref>
** Synchronous replication: [[Multi-master replication]] is provided in [[Software:MySQL Cluster|MySQL Cluster]].<ref>{{cite web|url=http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-replication-multi-master.html|title=MySQL Cluster Replication: Multi-Master and Circular Replication|publisher=MySQL}}</ref>
** [[Virtual synchrony|Virtual Synchronous]]: Self managed groups of MySQL servers with multi master support can be done using: Galera Cluster<ref>{{cite web|url=https://blogs.oracle.com/mysqlf/entry/mysql_university_mysql_galera_multi|title=MySQL University: MySQL Galera Multi-Master Replication|date=2010-02-09|publisher=[[Company:Oracle Corporation|Oracle Corporation]]|access-date=3 May 2013|archive-date=12 December 2013|archive-url=https://web.archive.org/web/20131212022901/https://blogs.oracle.com/mysqlf/entry/mysql_university_mysql_galera_multi|url-status=dead}}</ref> or the built in Group Replication plugin<ref>{{Cite web|url=https://dev.mysql.com/doc/refman/8.0/en/group-replication.html|title=MySQL :: MySQL 8.0 Reference Manual :: 18 Group Replication|website=dev.mysql.com|access-date=2019-03-09}}</ref>
* Full-text indexing and searching{{efn|Initially, it was a MyISAM-only feature; supported by InnoDB since the release of MySQL 5.6.}}
* Embedded database library
* [[Unicode]] support{{efn|name=utf8mb4|Prior to MySQL 5.5.3, [[UTF-8]] and UCS-2 encoded strings are limited to the BMP; MySQL 5.5.3 and later use utf8mb4 for full Unicode support.}}
* Partitioned tables with pruning of partitions in optimizer
* Shared-nothing clustering through [[Software:MySQL Cluster|MySQL Cluster]]
* Multiple storage engines, allowing one to choose the one that is most effective for each table in the application.{{efn|In MySQL 5.0, storage engines must be compiled in; since MySQL 5.1, storage engines can be dynamically loaded at [[Run time (program lifecycle phase)|run time]].}}
* Native storage engines [[Software:InnoDB|InnoDB]], [[Software:MyISAM|MyISAM]], Merge, Memory (heap), [[Software:MySQL Federated|Federated]], Archive, [[Comma-separated values|CSV]], Blackhole, NDB Cluster.
* Commit grouping, gathering multiple transactions from multiple connections together to increase the number of commits per second.

The developers release minor updates of the MySQL Server approximately every two months. The sources can be obtained from MySQL's website or from MySQL's [[GitHub]] repository, both under the GPL license.

===Limitations===
When using some storage engines other than the default of InnoDB, MySQL does not comply with the full [[SQL]] standard for some of the implemented functionality, including foreign key references.<ref>{{cite web
|url=https://dev.mysql.com/doc/refman/8.0/en/create-table-foreign-keys.html
|title=13.1.20.5 FOREIGN KEY Constraints
|publisher=MySQL
|access-date=10 March 2021}}</ref> Check constraints are parsed but ignored by all storage engines before MySQL version 8.0.15.<ref>{{cite web
|url=http://bugs.mysql.com/bug.php?id=3464
|title=Bug #3464 Constraints: support CHECK
|publisher=MySQL
|date=14 April 2004
|access-date=11 April 2015}}</ref><ref>{{Cite web|url=https://dev.mysql.com/doc/refman/8.0/en/create-table.html|title=MySQL 8.0 Reference Manual: CREATE TABLE Syntax |website=MySQL Reference Manual|publisher=Oracle|access-date=2018-05-07}}</ref>

Up until MySQL 5.7, triggers are limited to one per action / timing, meaning that at most one trigger can be defined to be executed after an {{mono|INSERT}} operation, and one before {{mono|INSERT}} on the same table.<ref name="dev.mysql.com">{{cite web
|url=http://dev.mysql.com/doc/refman/5.6/en/create-trigger.html
|title=CREATE TRIGGER Syntax
|publisher=MySQL
|access-date=11 April 2015}}</ref>
No triggers can be defined on views.<ref name="dev.mysql.com"/>

Before MySQL 8.0.28, inbuilt functions like {{mono|UNIX_TIMESTAMP()}} would return {{mono|0}} after 03:14:07 [[UTC]] on [[Year 2038 problem|19 January 2038]].<ref>{{cite web
|url=https://bugs.mysql.com/bug.php?id=12654
|title=MySQL Bugs: #12654: 64-bit unix timestamp is not supported in MySQL functions
|publisher=MySQL
|date=2005-08-18
|access-date=2017-10-06
}}</ref> In 2017, an attempt to solve the problem was submitted, but was not used for the final solution that was shipped in 2022.<ref>{{cite web
|url=https://github.com/mysql/mysql-server/pull/130
|title=Allow dates beyond 2038 by dveeden · Pull Request #130 · mysql/mysql-server
|publisher=GitHub, Inc.
|date=2017-03-22
|access-date=2017-10-06
}}</ref><ref>{{Cite web |title=MySQL Bugs: #12654: 64-bit unix timestamp is not supported in MySQL functions |url=https://bugs.mysql.com/bug.php?id=12654 |access-date=2023-08-29 |website=bugs.mysql.com}}</ref><ref>{{Cite web |title=MySQL :: MySQL 8.0 Release Notes :: Changes in MySQL 8.0.28 (2022-01-18, General Availability) |url=https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-28.html |access-date=2023-08-29 |website=dev.mysql.com}}</ref>

===Deployment===
MySQL can be built and installed manually from source code, but it is more commonly installed from a binary package unless special customizations are required. On most [[Software:Linux distribution|Linux distribution]]s, the package management system can download and install MySQL with minimal effort, though further configuration is often required to adjust security and optimization settings.

[[File:LAMP software bundle.svg|thumb|400px|LAMP software bundle, displayed here together with Squid.]]

Though MySQL began as a low-end alternative to more powerful proprietary databases, it has gradually evolved to support higher-scale needs as well. It is still most commonly used in small to medium scale single-server deployments, either as a component in a [[Software:LAMP (software bundle)|LAMP]]-based web application or as a standalone database server. Much of MySQL's appeal originates in its relative simplicity and ease of use, which is enabled by an ecosystem of open source tools such as [[Software:PhpMyAdmin|phpMyAdmin]].
In the medium range, MySQL can be scaled by deploying it on more powerful hardware, such as a multi-processor server with gigabytes of memory.

There are, however, limits to how far performance can scale on a single server ('scaling up'), so on larger scales, multi-server MySQL ('scaling out') deployments are required to provide improved performance and reliability. A typical high-end configuration can include a powerful master database which handles data write operations and is [[Software:Database replication|replicated]] to multiple slaves that handle all read operations.<ref>{{cite web |title = The future of replication in MySQL |publisher = Facebook |url= https://www.facebook.com/note.php?note_id=126049465932 |access-date =2009-12-09 }}</ref> The master server continually pushes binlog events to connected slaves so in the event of failure a slave can be promoted to become the new master, minimizing downtime. Further improvements in performance can be achieved by caching the results from database queries in memory using [[Software:Memcached|memcached]], or breaking down a database into smaller chunks called [[Shard (database architecture)|shards]] which can be spread across a number of distributed server clusters.<ref>{{cite web |title=Database Sharding |publisher=Code Futures |url = http://www.codefutures.com/dbshards-cloud/|access-date = 2009-12-09 |url-status=dead |archive-url = https://web.archive.org/web/20100116031912/http://codefutures.com/dbshards-cloud/|archive-date=16 January 2010}}</ref>

==={{anchor|HA}}High availability software===
Oracle MySQL offers a high availability solution with a mix of tools including the MySQL router and the MySQL shell. They are based on Group Replication, open source tools.<ref>{{Cite web|url=https://www.mysql.com/products/enterprise/high_availability.html|title=MySQL :: MySQL Enterprise High Availability|website=www.mysql.com|access-date=2019-03-09}}</ref>

MariaDB offers a similar offer in terms of products.<ref>{{Cite web|url=https://mariadb.com/kb/en/library/replication-cluster-multi-master/|title=High Availability & Performance Tuning|website=MariaDB KnowledgeBase|access-date=2019-03-09}}</ref>

===Cloud deployment===
{{Main article|Cloud database}}

MySQL can also be run on [[Cloud computing|cloud computing]] platforms such as [[Software:Microsoft Azure|Microsoft Azure]], [[Software:Amazon Elastic Compute Cloud|Amazon Elastic Compute Cloud]], [https://cloud.oracle.com/en_US/infrastructure/compute Oracle Cloud Infrastructure]. Some common deployment models for MySQL on the cloud are:

; Virtual machine image
: In this implementation, cloud users can upload a machine image of their own with MySQL installed, or use a ready-made machine image with an optimized installation of MySQL on it, such as the one provided by Amazon EC2.<ref>{{cite web |url = http://aws.amazon.com/articles/1663 |title = Running MySQL on Amazon EC2 with EBS (Elastic Block Store) |website =[[Company:Amazon Web Services|Amazon Web Services]] |access-date=5 February 2013 }}</ref>

; MySQL as a service
: Some cloud platforms offer MySQL "as a service". In this configuration, application owners do not have to install and maintain the MySQL database on their own. Instead, the database service provider takes responsibility for installing and maintaining the database, and application owners pay according to their usage.<ref name="readwriteweb">{{cite web | first=Klint |last=Finley |url=http://www.readwriteweb.com/cloud/2011/01/7-cloud-based-database-service.php | title = 7 Cloud-Based Database Services |website = ReadWriteWeb | access-date =2011-11-09 | url-status=dead | archive-url = https://web.archive.org/web/20111109084453/http://www.readwriteweb.com/cloud/2011/01/7-cloud-based-database-service.php |archive-date=2011-11-09}}</ref> Notable cloud-based MySQL services are the [[Software:Amazon Relational Database Service|Amazon Relational Database Service]]; [http://oracle.com/mysql Oracle MySQL HeatWave Database Service], [https://azure.microsoft.com/en-us/services/mysql/ Azure Database for MySQL], [[Company:Rackspace|Rackspace]]; HP Converged Cloud; [[Company:Heroku|Heroku]] and [[Company:Jelastic|Jelastic]]. In this model the database service provider takes responsibility for maintaining the host and database.

==User interfaces==
===Graphical user interfaces===
A [[Graphical user interface|graphical user interface]] (GUI) is a type of interface that allows users to interact with electronic devices or programs through graphical icons and visual indicators such as secondary notation, as opposed to text-based interfaces, typed command labels or text navigation.

Third-party proprietary and free graphical administration applications (or "front ends") are available that integrate with MySQL and enable users to work with database structure and data visually.

[[File:The MySQL Workbench startup screen.png|thumb|right|MySQL Workbench running on macOS]]

====MySQL Workbench====
{{main|Software:MySQL Workbench}}
[[Software:MySQL Workbench|MySQL Workbench]] is the integrated environment for MySQL. It was developed by MySQL AB, and enables users to graphically administer MySQL databases and visually design database structures.

MySQL Workbench is available in three editions, the regular free and open source ''Community Edition'' which may be downloaded from the MySQL website, and the proprietary ''Standard Edition'' which extends and improves the feature set of the Community Edition, and the MySQL Cluster CGE.<ref>{{Cite web|url=https://www.mysql.com/products/|title = MySQL :: MySQL Products}}</ref> <ref>{{Cite web|url=https://www.mysql.com/products/community/|title = MySQL :: MySQL Community Edition}}</ref>

====Other GUI tools====
* [[Software:Adminer|Adminer]]
* [[Software:Database Workbench|Database Workbench]]
* [[Software:DBeaver|DBeaver]]
* [[Software:DBEdit|DBEdit]]
* [[Software:HeidiSQL|HeidiSQL]]
* [[Software:LibreOffice Base|LibreOffice Base]]
* [[Software:Navicat|Navicat]]
* [[Software:OpenOffice.org|OpenOffice.org]] Base
* [[Software:PhpMyAdmin|phpMyAdmin]]
* [[Software:SQLBuddy|SQLBuddy]]
* [[Software:SQLyog|SQLyog]]
* [[Software:Toad|Toad for MySQL]]
* [[Software:Webmin|Webmin]]

===Command-line interfaces===
A [[Command-line interface|command-line interface]] is a means of interacting with a computer program where the user issues commands to the program by typing in successive lines of text (command lines). MySQL ships with many command line tools, from which the main interface is the {{Mono|mysql}} client.<ref name="mysql – The MySQL Command-Line Tool">[http://dev.mysql.com/doc/refman/5.6/en/mysql.html mysql — The MySQL Command-Line Tool], MySQL Reference Manual</ref><ref name="mysqladmin - the MySQL command-line tool">[http://dev.mysql.com/doc/refman/5.5/en/mysqladmin.html mysqladmin – the MySQL command-line tool], MySQL Reference Manual</ref>

MySQL Utilities is a set of utilities designed to perform common maintenance and administrative tasks. Originally included as part of the MySQL Workbench, the utilities are a stand-alone download available from Oracle.

Percona Toolkit is a cross-platform toolkit for MySQL, developed in [[Perl]].<ref>{{cite web|url=http://www.percona.com/software/percona-toolkit |title=Percona Toolkit|publisher=Percona |access-date=26 March 2014}}</ref> Percona Toolkit can be used to prove replication is working correctly, fix corrupted data, automate repetitive tasks, and speed up servers. Percona Toolkit is included with several [[Software:Linux|Linux]] distributions such as [[Software:CentOS|CentOS]] and [[Software:Debian|Debian]], and packages are available for [[Software:Fedora Linux|Fedora]] and [[Software:Ubuntu|Ubuntu]] as well. Percona Toolkit was originally developed as Maatkit, but as of late 2011, Maatkit is no longer developed.

MySQL shell is a tool for interactive use and administration of the MySQL database. It supports JavaScript, Python or SQL modes and it can be used for administration and access purposes.<ref>{{Cite web|url=https://dev.mysql.com/downloads/shell/|title=MySQL :: Download MySQL Shell|website=dev.mysql.com|access-date=2019-03-09}}</ref>

==Application programming interfaces==
Many [[Programming language|programming language]]s with language-specific [[Application programming interface|APIs]] include [[Library (computing)|libraries]] for accessing MySQL databases. These include MySQL Connector/Net for [[List of CLI languages|.NET/CLI Languages]],<ref>{{cite web|url=https://dev.mysql.com/doc/connector-net/en/ |title=MySQL Connector/NET Developer Guide |date=2020-09-09|access-date=2020-09-20|website=mysql.com}}</ref> and the JDBC driver for Java.<ref>{{cite web|url=https://dev.mysql.com/doc/connector-j/8.0/en/ |title=MySQL Connector/J Developer Guide |date=2020-09-18 |access-date=2020-09-20|website=mysql.com}}</ref>

In addition, an ODBC interface called MySQL Connector/ODBC allows additional programming languages that support the ODBC interface to communicate with a MySQL database, such as [[Software:Active Server Pages|ASP]] or [[Software:Adobe ColdFusion|ColdFusion]]. The [[HTSQL]]{{snd}} [[URL]]-based query method also ships with a MySQL adapter, allowing direct interaction between a MySQL database and any web client via structured URLs. Other drivers exists for languages like [[Python (programming language)|Python]]<ref>{{Cite web|url=https://dev.mysql.com/downloads/connector/python/|title=MySQL :: Download Connector/Python|website=dev.mysql.com|access-date=2019-03-09}}</ref> or [[Software:Node.js|Node.js]].<ref>{{Cite web|url=https://dev.mysql.com/downloads/connector/nodejs/|title=MySQL :: Download Connector/Node.js|website=dev.mysql.com|access-date=2019-03-09}}</ref>

==Project forks==
A variety of MySQL [[Software:Fork (software development)|forks]] exist, including the following.

=== Current ===
; MariaDB
: [[Software:MariaDB|MariaDB]] is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. The fork has been led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle.<ref name="dead" />
; Percona Server for MySQL
: [[Software:Percona Server for MySQL|Percona Server for MySQL]], forked by [[Company:Percona|Percona]], aims to retain close compatibility to the official MySQL releases.<ref>{{cite web|url=http://www.percona.com/software/percona-server/faq|publisher=Percona|work=Frequently Asked Questions|title=How is it related to other MySQL forks?|access-date=6 June 2015|archive-url=https://web.archive.org/web/20150415051416/http://www.percona.com/software/percona-server/faq|archive-date=15 April 2015|url-status=dead}}</ref> Also included in Percona Server for MySQL is [[Software:XtraDB|XtraDB]], Percona's fork of the [[Software:InnoDB|InnoDB Storage Engine]].<ref name="pcw1">{{cite web | url=http://www.pcworld.com/article/2054060/percona-challenges-oracle-with-alternate-mysql-release.html | title=Percona challenges Oracle with alternate MySQL release | work=PC World | access-date=12 February 2015}}</ref>

=== Abandoned ===
; Drizzle
: [[Software:Drizzle (database server)|Drizzle]] was a free software/open source relational database management system (DBMS) that was forked from the now-defunct 6.0 development branch of the MySQL DBMS.<ref name="Clark 2011">{{cite web | last=Clark | first=Jack | title=MySQL fork Drizzle gets general release | website=ZDNet | date=2011-03-17 | url=http://www.zdnet.com/article/mysql-fork-drizzle-gets-general-release/ | access-date=2016-01-03}}</ref> Like MySQL, Drizzle had a client/server architecture and uses [[SQL]] as its primary [[Command language|command language]]. Drizzle was distributed under version 2 and 3 of the [[Software:GNU General Public License|GNU General Public License]] (GPL) with portions, including the protocol drivers and [[Software:Database replication|replication]] messaging under the [[Software:BSD licenses|BSD]] license.
; WebScaleSQL
: [[Software:WebScaleSQL|WebScaleSQL]] was a software branch of MySQL 5.6, and was announced on 27 March 2014 by Facebook, Google, LinkedIn and Twitter as a joint effort to provide a centralized development structure for extending MySQL with new features specific to its large-scale deployments, such as building large replicated databases running on server farms. Thus, WebScaleSQL opened a path toward deduplicating the efforts each company had been putting into maintaining its own branch of MySQL, and toward bringing together more developers. By combining the efforts of these companies and incorporating various changes and new features into MySQL, WebScaleSQL aimed at supporting the deployment of MySQL in large-scale environments.<ref>{{cite news
 | url = http://www.zdnet.com/webscalesql-mysql-for-facebook-sized-databases-7000027814/
 | title = WebScaleSQL: MySQL for Facebook-sized databases
 | date = 28 March 2013 | access-date = 1 April 2014
 | author = Steven J. Vaughan-Nichols | work = [[ZDNet]]
}}</ref><ref>{{cite magazine
 | url = https://www.wired.com/2014/03/webscalesql/
 | title = Google and Facebook Team Up to Modernize Old-School Databases
 | date = 27 March 2013 | access-date = 1 April 2014
 | author = Klint Finley | magazine = Wired
}}</ref> The project's source code is licensed under version 2 of the GNU General Public License, and is hosted on [[GitHub]].<ref name="theregister-20140327">{{cite web
 | url = https://www.theregister.co.uk/2014/03/27/webscalesql_launch/
 | title = Forkin' 'L! Facebook, Google and friends create WebScaleSQL from MySQL 5.6
 | date = 27 March 2013 | access-date = 1 April 2014
 | author = Jack Clark | website = The Register
}}</ref><ref name="webscalesql-faq">{{Cite web
 | url = http://webscalesql.org/faq.html
 | title = Frequently Asked Questions
 | date = 27 March 2014 | access-date = 1 April 2014
 | website = webscalesql.org
}}</ref>
; OurDelta
: The OurDelta distribution, created by the Australian company Open Query (later acquired by Catalyst IT Australia), had two versions: 5.0, which was based on MySQL, and 5.1, which was based on MariaDB. It included patches developed by Open Query and by other notable members of the MySQL community including Jeremy Cole and Google. Once the patches were incorporated into the MariaDB mainline, OurDelta's objectives were achieved and OurDelta passed on its build and packaging toolchain to Monty Program (now MariaDB Plc).<ref>{{cite web |url=https://openquery.com.au/products/ourdelta |title=OurDelta |website=openquery.com.au |date=22 August 2017 |access-date=20 August 2021 }}</ref>

==See also==
* [[Software:Comparison of database administration tools|Comparison of database administration tools]]
* [[Software:Comparison of MySQL database engines|Comparison of MySQL database engines]]
* [[Software:Comparison of relational database management systems|Comparison of relational database management systems]]

== Notes ==
{{Notelist}}

== References ==
{{Reflist}}

==External links==
* [http://www.oracle.com/us/products/mysql/index.html MySQL] at [[Company:Oracle Corporation|Oracle]]
* {{curlie|/Computers/Software/Databases/MySQL/|MySQL}}

{{MySQL}}
{{Sun Microsystems}}
{{Oracle}}


[[Category:MySQL| ]]
[[Category:Client-server database management systems]]
[[Category:Cross-platform software]]
[[Category:Free database management systems]]
[[Category:Oracle software]]
[[Category:Relational database management systems]]

{{Sourceattribution|MySQL}}