MySQL: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Line 105: Line 105:
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.
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, so on larger scales, multi-server MySQL 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 [[Replication (computer science)#Database_replication|replicated]] to multiple slaves that handle all read operations.<ref>{{cite web |title=The future of replication in MySQL |publisher=Facebook |url=http://www.facebook.com/note.php?note_id=126049465932 |accessdate=2009-12-09 }}</ref> The master server synchronizes continually with its 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 [[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/|accessdate=2009-12-09 }}</ref>
There are however limits to how far performance can scale on a single server, so on larger scales, multi-server MySQL 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 [[Replication (computer science)#Database_replication|replicated]] to multiple slaves that handle all read operations.<ref>{{cite web |title=The future of replication in MySQL |publisher=Facebook |url=http://www.facebook.com/note.php?note_id=126049465932 |accessdate=2009-12-09 }}</ref> The master server synchronizes continually with its 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 [[memcached]], or breaking down a database into smaller chunks called [[Shard (database architecture)|shards]] which can be spread across a ASASASAXSWASXA number of distributed server clusters.<ref>{{cite web |title=Database Sharding|publisher=Code Futures |url= http://www.codefutures.com/dbshards-cloud/|accessdate=2009-12-09 }}</ref>


==Features==
==Features==

Revision as of 12:25, 31 August 2010

MySQL
Developer(s)MySQL AB (A subsidiary of Sun microsystems)
Initial releaseMay 23, 1995 (1995-05-23)
Repository
Written inC, C++
Operating systemCross-platform
Available inEnglish
TypeRDBMS
LicenseGNU General Public License (version 2, with linking exception) or proprietary EULA
Websitewww.mysql.com
dev.mysql.com

MySQL is a relational database management system (RDBMS)[1] that runs as a server providing multi-user access to a number of databases. MySQL is officially Template:Pron-en ("My S-Q-L"),[2] but is often pronounced /maɪˈsiːkwəl/ ("My Sequel"). It is named for original developer Michael Widenius's daughter My.[3]

The MySQL development project has made its source code available under the terms of the GNU General Public License, as well as under a variety of proprietary agreements. MySQL is owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned by Sun Microsystems, a subsidiary of Oracle Corporation.[4]

Members of the MySQL community have created several forks such as Drizzle, OurDelta, Percona Server, and MariaDB. All of these forks were in progress before the Oracle acquisition (Drizzle was announced 8 months before the Sun acquisition).

Free-software projects that require a full-featured database management system often use MySQL. Such projects include (for example) WordPress, phpBB, Drupal and other software built on the LAMP software stack. MySQL is also used in many high-profile, large-scale World Wide Web products including Wikipedia, Google[5] and Facebook[6].

Uses

The "M" in the acronym of the popular LAMP software stack refers to MySQL. Its popularity for use with web applications is closely tied to the popularity of PHP (the "P" in LAMP). Several of the highest-traffic web sites (including Flickr,[7] Facebook,[8][9] Wikipedia,[10] Google[11] (though not for searches), Nokia[12] and YouTube[13]) use MySQL for data storage and logging of user data.

Platforms and interfaces

MySQL code uses C and C++. The SQL parser uses yacc and a home-brewed lexer, sql_lex.cc[14]

MySQL works on many different system platforms, including AIX, BSDi, FreeBSD, HP-UX, i5/OS, Linux, Mac OS X, NetBSD, Novell NetWare, OpenBSD, OpenSolaris, eComStation, OS/2 Warp, QNX, IRIX, Solaris, Symbian, SunOS, SCO OpenServer, SCO UnixWare, Sanos, Tru64 and Microsoft Windows. A port of MySQL to OpenVMS also exists.[15]

Many programming languages with language-specific APIs include libraries for accessing MySQL databases[example needed]. In addition, an ODBC interface called MyODBC allows additional programming languages that support the ODBC interface to communicate with a MySQL database, such as ASP or ColdFusion. The HTSQL - URL based query method also ships with MySQL adapter allowing direct interaction with MySQL database from any web client via structured URLs. The MySQL server and official libraries are mostly implemented in ANSI C/ANSI C++.

Management and Graphical Frontends

MySQL Workbench in Windows, displaying the Home Screen which streamlines use of its full capabilities

MySQL is primarily an RDBMS and therefore ships with no GUI tools to administer MySQL databases or manage data contained within. Users may use the included command-line tools,[16] or download MySQL frontends from various parties that have developed desktop software and web applications to manage MySQL databases, build database structure, and work with data records.

Official

The official MySQL Workbench is a free integrated environment developed by MySQL AB, that enables users to graphically administer MySQL databases and visually design database structure. MySQL Workbench replaces the previous package of software, MySQL GUI Tools. Similar to other third-party packages but still considered the authoritative MySQL frontend, MySQL Workbench lets users manage the following:

  • Database design & modeling
  • SQL development — replacing MySQL Query Browser
  • Database administration — replacing MySQL Administrator

MySQL Workbench is available in two 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.

Third party

Several other third-party proprietary and free graphical administration applications (or "Frontends") are available that integrate with MySQL and enable users to work with database structure and data visually. Some well-known frontends are:

Command-Line

MySQL ships with a suite of command-line tools for tasks such as querying the database, backing up data, inspecting status, performing common tasks such as creating a database, and many more. A variety of third-party command-line tools is also available, including:

  • Maatkit, a set of power-user tools written in Perl
  • MySQL Sandbox, a set of scripts for quickly starting server instances for testing and development

Deployment

MySQL can be built and installed manually from source code, but this can be tedious so it is more commonly installed from a binary package unless special customizations are required. On most Linux distributions the package management system can download and install MySQL with minimal effort, though further configuration is often required to adjust security and optimization settings.

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 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 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, so on larger scales, multi-server MySQL 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 replicated to multiple slaves that handle all read operations.[18] The master server synchronizes continually with its 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 memcached, or breaking down a database into smaller chunks called shards which can be spread across a ASASASAXSWASXA number of distributed server clusters.[19]

Features

As of April 2009, MySQL offers MySQL 5.1 in two different variants: the open source MySQL Community Server and the commercial Enterprise Server.[20] They have a common code base and include the following features:

The developers release monthly versions of the MySQL Server. The sources can be obtained from MySQL's web site or from MySQL's Bazaar repository, both under the GPL license.

Distinguishing features

MySQL implements the following features, which some other RDBMS systems may not:

  • Multiple storage engines, allowing one to choose the one that is most effective for each table in the application (in MySQL 5.0, storage engines must be compiled in; in MySQL 5.1, storage engines can be dynamically loaded at run time):
  • Commit grouping, gathering multiple transactions from multiple connections together to increase the number of commits per second.

Product history

Milestones in MySQL development include:

  • Original development of MySQL by Michael Widenius and David Axmark beginning in 1994[23]
  • First internal release on 23 May 1995
  • Windows version was released on 8 January 1998 for Windows 95 and NT
  • Version 3.23: beta from June 2000, production release January 2001
  • Version 4.0: beta from August 2002, production release March 2003 (unions)
  • Version 4.01: beta from August 2003, Jyoti adopts MySQL for database tracking
  • Version 4.1: beta from June 2004, production release October 2004 (R-trees and B-trees, subqueries, prepared statements)
  • Version 5.0: beta from March 2005, production release October 2005 (cursors, stored procedures, triggers, views, XA transactions)
The developer of the Federated Storage Engine states that "The Federated Storage Engine is a proof-of-concept storage engine",[24] 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".
  • Sun Microsystems acquired MySQL AB on 26 February 2008.[4]
  • Version 5.1: production release 27 November 2008 (event scheduler, partitioning, plugin API, row-based replication, server log tables)
Version 5.1 contained 20 known crashing and wrong result bugs in addition to the 35 present in version 5.0.[25]
MySQL 5.1 and 6.0 showed poor performance when used for data warehousing — partly due to its inability to utilize multiple CPU cores for processing a single query.[26]

Future releases

MySQL Server 5.5 is currently available in pre-release (as of June 2010). Enhancements and features include:

  • The default storage engine is InnoDB, which supports transactions and referential integrity constraints.
  • Semisynchronous replication.
  • SIGNAL and RESIGNAL statement in compliance with the SQL standard.
  • Support for supplementary Unicode character sets utf16, utf32, and utf8mb4.
  • New options for user-defined partitioning.

MySQL Server 6.0.11-alpha was announced May 22, 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.

Support and licensing

MySQL offers support via their MySQL Enterprise product, including a 24/7 service with 30-minute response time. The support team has direct access to the developers as necessary to handle problems. In addition, it hosts forums and mailing lists, employees and other users are often available in several IRC channels providing assistance.

Buyers of MySQL Enterprise have access to binaries and software certified for their particular operating system, and access to monthly binary updates with the latest bug-fixes. Several levels of Enterprise membership are available, with varying response times and features ranging from how to and emergency support through server performance tuning and system architecture advice. The MySQL Network Monitoring and Advisory Service monitoring tool for database servers is available only to MySQL Enterprise customers.

Potential users can install MySQL Server as free software under the GNU General Public License (GPL), and the MySQL Enterprise subscriptions include a GPL version of the server, with a traditional proprietary version available on request at no additional cost for cases where the intended use is incompatible with the GPL.[27]

Both the MySQL server software itself and the client libraries use dual-licensing distribution. Users may choose the GPL,[28] which MySQL has extended with a FLOSS License Exception. It allows Software licensed under other OSI-compliant open source licenses, which are not compatible to the GPL, to link against the MySQL client libraries.[29]

Customers that do not wish to follow the terms of the GPL may purchase a proprietary license.[30]

Like many open-source programs, MySQL has trademarked its name, which others may use only with the trademark holder's permission.[31]

Corporate backing history

In October 2005, Oracle Corporation acquired Innobase OY, the Finnish company that developed the third-party InnoDB storage engine that allows MySQL to provide such functionality as transactions and foreign keys. After the acquisition, an Oracle press release mentioned that the contracts that make the company's software available to MySQL AB would be due for renewal (and presumably renegotiation) some time in 2006.[32] During the MySQL Users Conference in April 2006, MySQL issued a press release that confirmed that MySQL and Innobase OY agreed to a "multi-year" extension of their licensing agreement.[33]

In February 2006, Oracle Corporation acquired Sleepycat Software,[34] makers of the 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 deprecated (due to lack of use) in MySQL 5.1.12, a pre-GA release of MySQL 5.1 released in October 2006.[35]

In January 2008, Sun Microsystems bought MySQL for USD $1 billion.[36]

In April 2009, Oracle Corporation entered into an agreement to purchase Sun Microsystems,[37] 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 August 20, 2009.[38] On December 14, 2009, Oracle pledged to continue to enhance MySQL[39] as it had done for the previous four years. A movement against Oracle's acquisition of MySQL, to "Save MySQL" [40] from Oracle was started by one of the MySQL founders, Monty Widenius. The petition of 50,000+ developers and users called upon the European Commission to block approval of the acquisition. As part of the negotiations with the European Commission, Oracle committed that MySQL server will continue to use the dual-licensing strategy long used by MySQL AB with commercial and GPL versions available until at least 2015. The Oracle acquisition was eventually approved by the European Commission on January 21, 2010.[41] Meanwhile, Monty Widenius has released a GPL only fork, MariaDB. MariaDB is based on the same code base as MySQL server and strives to maintain compatibility with Oracle provided versions.[42]

Forks of MySQL

  • Drizzle — a fork targeted at the web-infrastructure and cloud computing markets. The developers of the product describe it as a "smaller, slimmer and (hopefully) faster version of MySQL". As such is planned to have many common MySQL features stripped out, including stored procedures, query cache, prepared statements, views, and triggers. This is a complete rewrite of the server that does not maintain compatibility with MySQL.
  • Percona Server — a community-developed branch of the MySQL database, the impetus being the community maintenance of its free status under GPL as opposed to any uncertainty of MySQL license status under its current ownership by Oracle. The intent also being to maintain high fidelity with MySQL, ensuring a "drop-in" replacement capability with library binary equivalency and exacting matching with MySQL APIs and commands. It includes the XtraDB storage engine as a replacement for InnoDB.
  • MariaDB — a fork that includes the XtraDB storage engine. It is an enhanced version of MySQL that is fully compatible, and deviates as little as possible from it, while still providing beneficial new features, better performance, and improved instrumentation for analysis of performance and usage.
  • OurDelta — is best characterized as a source of binaries compiled with various patches, including patches from MariaDB, Percona, and Google.

MySQL versions

[43] [44] [45] [46] [47] [48]

See also

Frontend applications:

Other RDBMS:

References

  1. ^ Robin Schumacher, Arjen Lentz. "Dispelling the Myths". MySQL AB. Retrieved 2007-02-10.
  2. ^ "What is MySQL?, MySQL 5.1 Reference Manual". MySQL AB. Retrieved 2010-03-19. 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.
  3. ^ "History of MySQL, MySQL 5.1 Reference Manual". MySQL AB. Retrieved 2010-03-19. MySQL is named after co-founder Monty Widenius's daughter, My.
  4. ^ a b Sun Microsystems Announces Completion of MySQL Acquisition; Paves Way for Secure, Open Source Platform to Power the Network Economy, Sun Microsystems Press release, February 26, 2008
  5. ^ "Google Runs MySQL". TheOpenForce. Retrieved 2010-08-03. AdWords was built using the MySQL database
  6. ^ "MySQL at Facebook". O'Reilly, Mark callaghan. Retrieved 2010-08-03. x,000 servers, ... Master-slave replication, InnoDB
  7. ^ "YouTube, Flickr, and Wikipedia to Share their Secrets of Success at the 2007 MySQL Conference & Expo". MySQL. 10 April 2007. Retrieved 2009-12-09.
  8. ^ Sobel, Jason (21 December 2007). "Keeping Up". Facebook Blog. {{cite web}}: Unknown parameter |ac cessdate= ignored (help)
  9. ^ Malik, Om (25 April 2008). "Facebook's Insatiable Hunger for Hardware". GigaOM. Retrieved 2008-10-30.
  10. ^ "Wikimedia servers - Overall system architecture". Retrieved 2009-09-11.
  11. ^ Claburn, Thomas (24 April 2007). "Google Releases Improved MySQL Code". Information Week. Retrieved 2008-11-30.
  12. ^ MySQL.com
  13. ^ MySQL.com
  14. ^ "MySQL Internals Manual". Dev.mysql.com. 2009-03-04. Retrieved 2009-06-08.
  15. ^ Jean-François Piéronne. "PCSI Kits of Open Source Software for OpenVMS". Pi-net.dyndns.org. Retrieved 2009-06-08.
  16. ^ MySQL Command line tools: mysql and mysqladmin
  17. ^ HeidiSQL Grid editing features, using various editors for text, hex/binary, enum, set, date/time columns
  18. ^ "The future of replication in MySQL". Facebook. Retrieved 2009-12-09.
  19. ^ "Database Sharding". Code Futures. Retrieved 2009-12-09.
  20. ^ "Which Should I Use: MySQL Enterprise or MySQL Community Server?". MySQL AB. Retrieved 2009-04-08.
  21. ^ "4.6.9. mysqlhotcopy - A Database Backup Program". MySQL 5.0 Reference Manual. Sun Microsystems. Retrieved 2009-09-23. mysqlhotcopy is a Perl script [...]. It uses Lock Tables, Flush Tables, and cp or scp to make a database backup quickly [...] but it can be run only on the same machine where the database directories are located. mysqlhotcopy works only for backing up MyISAM and Archive tables. It runs on Unix and NetWare. {{cite web}}: Cite has empty unknown parameters: |month= and |coauthors= (help)
  22. ^ "The DB2 for i (IBMDB2I) Storage Engine for MySQL on IBM i". MySQL. Retrieved 2010-01-18.
  23. ^ "Five Questions With Michael Widenius - Founder And Original Developer of MySQL". Opensourcereleasefeed.com. Retrieved 2009-06-08.
  24. ^ "capttofu: FederatedX Pluggable Storage Engine Released!". Capttofu.livejournal.com. Retrieved 2009-04-03.
  25. ^ "Archives - Oops, we did it again (MySQL 5.1 released as GA wi". Planet MySQL. 2008-11-29. Retrieved 2009-04-03.
  26. ^ "TPC-H Run on MySQL 5.1 and 6.0 | MySQL Performance Blog". MySQL Performance Blog. Retrieved 2009-06-08.
  27. ^ "Must I purchase MySQL Enterprise under MySQL's Commercial License in order to receive support?". MySQL AB.
  28. ^ "MySQL AB :: MySQL Open Source License". Mysql.com. Retrieved 2009-06-08.
  29. ^ "MySQL AB :: FLOSS License Exception". Mysql.com. Retrieved 2009-06-08.
  30. ^ "MySQL AB :: MySQL Commercial License". Mysql.com. Retrieved 2009-06-08.
  31. ^ "MySQL AB Trademark Policy". MySQL AB. September 2005. Retrieved 28 February 2010.
  32. ^ "Oracle Plans to Increase Support for Open Source Software". Oracle and InnoDB.
  33. ^ "MySQL to Promote New Open Source DB Engines from its Partners and Dev Community". MySQL AB.
  34. ^ "Oracle Buys Sleepycat, Is JBoss Next?". Charles Babcock.
  35. ^ "MySQL 5.1.12 change list".
  36. ^ "Sun to Acquire MySQL".
  37. ^ "Oracle to Buy Sun". Sun Microsystems Press Release.
  38. ^ "Oracle wins U.S. approval to buy Sun Microsystems". Reuters. August 20, 2009. Retrieved 2009-09-30.
  39. ^ Cnet.com
  40. ^ "Save MySQL!".
  41. ^ "Mergers: Commission clears Oracle's proposed acquisition of Sun Microsystems".
  42. ^ "MariaDB vs MySQL".
  43. ^ "B.3. Changes in Release 3.23.x (Lifecycle Support Ended)". Oracle. Retrieved 2010-08-24.
  44. ^ "B.2. Changes in Release 4.0.x (Lifecycle Support Ended)". Oracle. Retrieved 2010-08-24.
  45. ^ "B.1. Changes in Release 4.1.x (Lifecycle Support Ended)". Oracle. Retrieved 2010-08-24.
  46. ^ "C.1. Changes in Release 5.0.x (Production)". Oracle. Retrieved 2010-08-24.
  47. ^ "C.1. Changes in Release 5.1.x (Production)". Oracle. Retrieved 2010-08-24.
  48. ^ "C.1. Changes in Release 5.5.x (Development)". Oracle. Retrieved 2010-08-24.

External links

Wikibooks has more on the topic of: MySQL
Wikimedia Commons has media related to MySQL.
Retrieved from "https://en.wikipedia.org/w/index.php?title=MySQL&oldid=382057852"