MySQL

From Seo Wiki - Search Engine Optimization and Programming Languages

Jump to: navigation, search
MySQL
File:MySQL.svg
File:Mysql-screenshot.PNG
Screenshot of the default MySQL command line.
Developer(s) Oracle Corporation
Initial release Template:Start-date
Written in C, C++
Operating system Cross-platform
Available in English
Type RDBMS
License GNU General Public License (version 2, with linking exception) or proprietary EULA
Website www.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 pronounced /maɪˌɛskjuːˈɛl/ (My S-Q-L), but often pronounced /maɪˌsiː'kwɛl/ (My SeQueL).[2]

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.[3]

In response to the acquisition by Oracle, members of the MySQL community have created several forks such as Drizzle and MariaDB in fear that Oracle would hurt the development of MySQL because MySQL competes with Oracle Corporation's other database products.

Free-software projects that require a full-featured database management system often use MySQL. Such projects include (for example) WordPress, phpBB 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, Drupal and Facebook.

Contents

Uses

Many web applications use MySQL as the database component of a LAMP software stack. Its popularity for use with web applications is closely tied to the popularity of PHP, which is often combined with MySQL. Several high-traffic web sites (including Flickr,[4] Facebook,[5][6] Wikipedia,[7] Google[8] (though not for searches), Nokia[9] and YouTube[10]) 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[11]

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.[12]

All major programming languages with language-specific APIs include Libraries for accessing MySQL databases. 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 MySQL server and official libraries are mostly implemented in ANSI C/ANSI C++.

Management and Graphical Frontends

File:Mysqlwb-homepage.png
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,[13] 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:

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 commercial Standard Edition which extends and improves the feature set of the Community Edition.

Third party

Several other third-party commercial and non-commercial 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:

  • phpMyAdmin - a free Web-based frontend widely installed by Web hosts worldwide, since it is developed in PHP and only requires the LAMP stack to run.
  • HeidiSQL - a full featured free frontend that runs on Windows, and can connect to local or remote MySQL servers to manage databases, tables, column structure, and individual data records. Also supports specialised GUI features for date/time fields and enumerated multiple-value fields[14].
  • Navicat - a series of commercial graphical database management applications, developed for Windows, Macintosh and Linux.

Available commercial MySQL frontends include:

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 or a pre-integrated TurnKey MySQL appliance that is ready-to-use[15] without manual configuration or setup.

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.[16] 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 number of distributed server clusters.[17]

Features

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

The developers release monthly versions of the MySQL Enterprise Server. The sources can be obtained either from MySQL's customer-only Enterprise site or from MySQL's Bazaar repository, both under the GPL license. The MySQL Community Server is published on an unspecified schedule under the GPL and contains all bug fixes that were shipped with the last MySQL Enterprise Server release. Binaries are no longer provided by MySQL for every release of the Community Server.[20][21]

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] MySQL is named after Monty Widenius's daughter My.[24]
  • 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",[25] 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.[3]
  • 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.[26]
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.[27]

Future releases

The MySQL 6 roadmap outlines support for:

  • Referential integrity and Foreign key support for all storage engines is targeted for release in MySQL 6.1 (although it has been present since version 3.23.44 for InnoDB).
  • Support for supplementary Unicode characters, beyond the 65,536 characters of the Basic Multilingual Plane (BMP); announced for MySQL 6.0.
  • A new storage engine called Falcon. A preview of Falcon is available on MySQL's website.

The 2006 roadmap for future versions plans support for parallelization.[28]

Support and licensing

Via MySQL Enterprise MySQL AB offers support itself, 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.

In addition to official product support from Sun, other companies offer support and services related to usage of MySQL. For example, Percona offers services related to optimization and Monty Program Ab offers non-recurring engineering.

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.[29]

Both the MySQL server software itself and the client libraries use dual-licensing distribution. Users may choose the GPL,[30] 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.[31]

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

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

Corporate backing history

In October 2005, Oracle Corporation acquired Innobase OY, the Finnish company that developed the InnoDB storage engine that allows MySQL to provide such functionality as transactions and foreign keys. After the acquisition, an Oracle press release[33] 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. 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.[34]

In February 2006, Oracle Corporation acquired Sleepycat Software,[35] makers of the Berkeley DB, a database engine providing the basis for another MySQL storage engine.

In April 2009, Oracle Corporation entered into an agreement to purchase Sun Microsystems,[36] current owners of the MySQL intellectual property. 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.[37] On December 14, 2009, Oracle pledged to continue to enhance MySQL.[38] In Europe the merge is under scrutiny by EU antitrust regulators, whose main concerns are on conflict of interests with existing database software by Oracle. Michael Widenius, one of the founders of MySQL, launched a petition to pledge EU Commission to stop the deal.[39] As the EC seems likely to approve the deal regardless, Widenius has since called on Russian and Chinese regulators to object to the deal.[40]

Forks in response to Oracle takeover

In response to Oracle's takeover of MySQL with the acquisition of Sun Microsystems, several forks have been made which hope to ensure the future success of MySQL despite being purchased by its biggest competitor.[citation needed] These include Drizzle and MariaDB. There are also moves in the community to retain the original MySQL offering, such as the Save MySQL petition.

See also

Frontend applications:

Other RDBMS:

References

  1. Robin Schumacher, Arjen Lentz. "Dispelling the Myths". MySQL AB. http://dev.mysql.com/tech-resources/articles/dispelling-the-myths.html. Retrieved 2007-02-10. 
  2. "What is MySQL?, MySQL 5.0 Reference Manual". MySQL AB. http://dev.mysql.com/doc/refman/5.0/en/what-is-mysql.html. Retrieved 2007-02-10. 
  3. 3.0 3.1 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
  4. "YouTube, Flickr, and Wikipedia to Share their Secrets of Success at the 2007 MySQL Conference & Expo". MySQL. 10 April 2007. http://dev.mysql.com/tech-resources/articles/mysqluc-2007.html. Retrieved 2009-12-09. 
  5. Sobel, Jason (21 December 2007). "Keeping Up". Facebook Blog. http://blog.facebook.com/blog.php?post=7899307130. 
  6. Malik, Om (25 April 2008). "Facebook’s Insatiable Hunger for Hardware". GigaOM. http://gigaom.com/2008/04/25/facebooks-insatiable-hunger-for-hardware/. Retrieved 2008-10-30. 
  7. "Wikimedia servers - Overall system architecture". http://meta.wikimedia.org/wiki/Wikimedia_servers#Overall_system_architecture. Retrieved 2009-09-11. 
  8. Claburn, Thomas (24 April 2007). "Google Releases Improved MySQL Code". Information Week. http://www.informationweek.com/news/internet/showArticle.jhtml?articleID=199201237. Retrieved 2008-11-30. 
  9. MySQL.com
  10. MySQL.com
  11. "MySQL Internals Manual". Dev.mysql.com. 2009-03-04. http://dev.mysql.com/doc/internals/en/index.html. Retrieved 2009-06-08. 
  12. Jean-François Piéronne. "PCSI Kits of Open Source Software for OpenVMS". Pi-net.dyndns.org. http://www.pi-net.dyndns.org/anonymous/kits/. Retrieved 2009-06-08. 
  13. MySQL Command line tools: mysql and mysqladmin
  14. HeidiSQL Grid editing features, using various editors for text, hex/binary, enum, set, date/time columns
  15. "MySQL Appliance". TurnKey Linux Virtual Appliance Library. http://www.turnkeylinux.org/mysql. Retrieved 2009-12-09. 
  16. "The future of replication in MySQL". Facebook. http://www.facebook.com/note.php?note_id=126049465932. Retrieved 2009-12-09. 
  17. "Database Sharding". Code Futures. http://www.codefutures.com/dbshards-cloud/. Retrieved 2009-12-09. 
  18. "Which Should I Use: MySQL Enterprise or MySQL Community Server?". MySQL AB. http://www.mysql.com/products/which-edition.html. Retrieved 2009-04-08. 
  19. "4.6.9. mysqlhotcopy - A Database Backup Program". MySQL 5.0 Reference Manual. Sun Microsystems. http://dev.mysql.com/doc/refman/5.0/en/mysqlhotcopy.html. 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." 
  20. "Peter Zaitsev's blog". Mysqlperformanceblog.com. http://www.mysqlperformanceblog.com/2006/12/29/where-to-get-recent-mysql-version/. Retrieved 2009-06-08. 
  21. "Kaj Arnö's reply". Planetmysql.org. http://www.planetmysql.org/kaj/?p=82. Retrieved 2009-06-08. 
  22. "The DB2 for i (IBMDB2I) Storage Engine for MySQL on IBM i". MySQL. http://solutions.mysql.com/engines/ibm_db2_storage_engine.html. Retrieved 2010-01-18. 
  23. "Five Questions With Michael Widenius - Founder And Original Developer of MySQL". Opensourcereleasefeed.com. http://www.opensourcereleasefeed.com/interview/show/five-questions-with-michael-widenius-founder-and-original-developer-of-mysql. Retrieved 2009-06-08. 
  24. "FAQ MariaDB, Why is the project called MariaDB?". Monty Widenius. http://askmonty.org/wiki/index.php/MariaDB#Why_is_the_project_called_MariaDB.3F. Retrieved 2009-01-18. 
  25. "capttofu: FederatedX Pluggable Storage Engine Released!". Capttofu.livejournal.com. http://capttofu.livejournal.com/5798.html. Retrieved 2009-04-03. 
  26. "Archives - Oops, we did it again (MySQL 5.1 released as GA wi". Planet MySQL. 2008-11-29. http://www.planetmysql.org/entry.php?id=16232. Retrieved 2009-04-03. 
  27. "TPC-H Run on MySQL 5.1 and 6.0 | MySQL Performance Blog". MySQL Performance Blog. http://www.mysqlperformanceblog.com/2008/04/10/tpc-h-run-on-mysql-51-and-60/. Retrieved 2009-06-08. 
  28. "Does MySQL support query parallelisation?". Forums.mysql.com. http://forums.mysql.com/read.php?106,78549,79006#msg-79006. Retrieved 2009-06-08. 
  29. "Must I purchase MySQL Enterprise under MySQL's Commercial License in order to receive support?". MySQL AB. http://www.mysql.com/about/legal/supportpolicies/policies-05.html#q01. 
  30. "MySQL AB :: MySQL Open Source License". Mysql.com. http://www.mysql.com/products/licensing/opensource-license.html. Retrieved 2009-06-08. 
  31. "MySQL AB :: FLOSS License Exception". Mysql.com. http://www.mysql.com/company/legal/licensing/foss-exception.html. Retrieved 2009-06-08. 
  32. "MySQL AB :: MySQL Commercial License". Mysql.com. http://www.mysql.com/company/legal/licensing/commercial-license.html. Retrieved 2009-06-08. 
  33. "Oracle Plans to Increase Support for Open Source Software". Oracle and InnoDB. http://www.oracle.com/innodb/index.html. 
  34. "MySQL to Promote New Open Source DB Engines from its Partners and Dev Community". MySQL AB. http://www.mysql.com/news-and-events/press-release/release_2006_21.html. 
  35. "Oracle Buys Sleepycat, Is JBoss Next?". Charles Babcock. http://www.informationweek.com/software/showArticle.jhtml?articleID=180200853. 
  36. "Oracle to Buy Sun". Sun Microsystems Press Release. http://www.sun.com/aboutsun/pr/2009-04/sunflash.20090420.1.xml. 
  37. "Oracle wins U.S. approval to buy Sun Microsystems". Reuters. August 20, 2009. http://www.reuters.com/article/rbssTechMediaTelecomNews/idUSN2053486920090820. Retrieved 2009-09-30. 
  38. Cnet.com
  39. "Save MySQL!". Monty Program Ab. http://www.helpmysql.org/. Retrieved 2010-01-04. 
  40. "MySQL campaigners lean on Russia and China". Computerworld UK. http://www.computerworlduk.com/management/government-law/legislation/news/index.cfm?newsid=18376. Retrieved 2010-01-19. 

External links

Personal tools

Served in 1.452 secs.