MySQL Introduction and Installation

I. MySQL INTRODUCTION 1, logo

The name of the MySQL dolphin logo is called "Sakila", and it is selected by the founder of MySQL AB from a list of many names suggested by the user in the "Dolphin Naming" contest. The winning name is provided by Ambrose Twebaze, an open source software developer from Swaziland , Africa. According to Ambrose, Sakila comes from a Swaziland dialect called SiSwati, and is also the name of a small town in Arusha, Tanzania , near Ambrose's hometown of Uganda.

Note: Sakila is also a database sample from MySQL (Sakila sample).

2.MySQL Development

MySQL's history can be traced back to 1979, a person called Monty Widenius, for a small company called TCX work, and basic design a reporting tool, can be run on the 4M clock and 16KB memory of the computer. After a while, the tool was rewritten in C and migrated to the UNIX platform, at which point it was a very low-level report-oriented storage engine. This tool is called Unireg.
In 1985, a few like-minded lads in Sweden (led by David Axmark) set up a company that was the predecessor of MySQL AB. The company was not originally designed to develop database products, but it needed a database in the process of implementing their ideas. They want to be able to use open source products. But at that time there is no suitable choice, no way, then develop it yourself.

at first, they just designed a way to access data by using an indexed sequence, that is, the predecessor of the core algorithm for the storage engine of the I-S A M (Indexed sequential Access method), using ISAM in conjunction with mSQL to achieve their application needs. In the early days, they were primarily providing data warehousing services to some of Sweden's largest retailers. In the process of system use, the combination of ISAM and mSQL becomes more and more heavy with the increasing of data volume and the higher complexity of system. After analyzing the performance bottlenecks, they found that the problem was msql. Had to, they abandoned the msql, and re-developed a similar function of the data storage engine, which is the ISAM storage engine. You may have noticed that their main customer at the time was the data warehouse, and it should be easy to understand why, until now, MySQL is best at querying performance, rather than transactional processing (with third-party storage engines).

in 1990, TCX's customer was asked to provide SQL support for its API, when someone thought of using a commercial database directly, but Monty that the speed of a commercial database was difficult to satisfy. As a result, he uses the mSQL code directly to integrate it into its own storage engine. But unfortunately, the effect is not very good. So, Monty ambitious, determined to rewrite a SQL support.

in 1996, MySQL 1.0 was released and used on a small scale. By October 96, MySQL 3.11.1 was released without a 2.x version. Initially, only binary versions under Solaris are available. One months later, theLinux version appeared. At this point, MySQL is also very primitive, in addition to doing some insert,update,delete and select operations on a table position, no more features.

for the next two years, MySQL migrated to each platform in turn. When it was released, the license policy adopted was somewhat different: it allowed for free commerce, but it was not possible to bundle MySQL with its own products. If you want to publish together, you have to use a special license, which means it costs money. Of course, business support also needs to spend money. Other, with the user how to use all can. This special license brings some revenue to MySQL, which lays a good foundation for its sustainable development.

in 1999-2000, a company was founded in Sweden, called MySQL AB. Hired several people, working with SLEEPYCAT, to develop the Berkeley DB engine, since BDB supports transactional processing, so MySQL has since started supporting transactions.

in 2000, MySQL released its source code and formally entered the open source world with the GPL (GNU general public License) license agreement.

In April 2000, MySQL sorted out the old storage engine, named MyISAM.

In 2001, Heikiki Tuuri proposed to MySQL to integrate their storage engine InnoDB, which also supports transactional processing and row-level locks. So in the 3.23 release of 2001, this version already supported most basic SQL operations, and also integrated the MyISAM and InnoDB storage engines. The official combination version of MySQL with InnoDB is 4.0.

In October 2004, the classic version of 4.1 was released. In October 2005, there was a release of a version of the milestone, MySQL 5.0. Added support for cursors, stored procedures, triggers, views, and transactions in 5.0. In the version after 5.0, MySQL clearly demonstrated the pace of progress towards a high-performance database.

January 2008 , 16th MySQL was acquired by Sun Company .

April 20, 2009 Oracle acquires Sun, MySQL is transferred to Oracle.

April 2010 22 released MySQL 5.5, Mysqlcluster 7.1.

Oracle has re-divided the MySQL version into the community and Enterprise Editions, and the Enterprise Edition is charged, and of course the fee will provide more functionality.

Ii. MySQL installation 1, Windows version

Windows platform: Win 7 64-bit

MySQL version: 5.5.27 (Mysql-5.5.27-win32.msi)

(1) Double-click the installation package, open the MySQL Installation Wizard, click Next:

(2) Tick the license agreement and click Next:

(3) Select installation method: Custom

Typical	Typical installation. Installing the most common program features is recommended for most users.
Custom	Custom installation. allows users to choose the installed program features and location of the installation, recommended for advanced users. (recommended)
Complete	Fully installed. All program features will be installed, requiring the most disk space.

(4) Select functional components:

MySQL Server			Installing the MySQL server main program
	Client Programs	Various helpful (commandline) tools including the MySQL command line client	A variety of useful (command line) tools include the MySQL command line client
	Debug binaries	Debug/trace versions of executables and libraries	Debug/Trace versions of executables and library files
Development components		Installs/C + + header files and libraries	Installing the C + + header files and libraries
Debug Symbols		Installs Debug Symbols	Installing debug Symbols
Server Data files		Server data files	Server data files

① Specify the installation path for MySQL Program files: select "MySQL Server", click "Browser" to select a folder

② Specify the installation path for the MySQL data file: Select the "Server data Files" item and click "Browser" to select a folder

(5) Click Next, enter the installation screen, click Install, wait for the installation to complete, and then tick "launch the MySQL Instance Configuration Wizard", click "Finish", To start the MySQL Instance Configuration Wizard:

(6) Select the Configuration type:

Detailed Configuration	Detailed configuration	Choose this configuration type to create the optimal server Setup	Select this configuration type to create the best server settings for this machine.
Standard Configuration	Standard configuration	The use of this is on machines, that does not already has a MySQL server installation. This would use a general purpose configuration for the server so can be tuned manually	This entry applies only to machines that do not have a MySQL server installed. This will use a common configuration of the server that can be manually adjusted.

(7) Select service type:Developer Machine

Developer Machine	Development Server	This was a development machine,and many other applications would be run on It.mysql server should only use a minimal amount of memory.	This is a development machine that runs many other applications on it. The MySQL server should use only a small amount of memory.
Server Machine	Server machine	Several server applications is running on the this machine. Choose this option for web/application Servers.mysql would have medium memory usage.	Some server applications will run on this computer and select the item for Web/app service. MySQL will use medium memory.
Dedicated MySQL Server machine	Dedicated MySQL server	This are dedicated to run, the MySQL datebase.no other Servers,such as a web or mail Server,will be run. MySQL would utilize up to all available memory.	This machine is dedicated to running the MySQL database. There are no other servers, such as Web or mail servers, that will run. MySQL will take advantage of all available memory.

(8) Select the database to use: Multifunctional

Multifunctional Database	Multi-function database	General purpose databases. This would optimize the server for the use of the fast transactional InnoDB storage engine and the high speed MyISAM Storag E engine.	A generic database that optimizes the server using the fast transaction storage engine InnoDB and the high-speed storage engine MyISAM.
Transactional Database only	Transaction processing Database	Optimized for application servers and transactional Web applications. This would make InnoDB the main storage engine. Note that the MyISAM engine can still is used.	Application servers and transactional Web applications are optimized. This will make the InnoDB storage engine a primary. It is important to note that the MyISAM engine is still available.
Non-transactional Database only	Non-transactional database	Suited for simple web applications,monitoring or logging applications as well as analysis programs. Only the non-transactional MyISAM storage engine would be activated.	Suitable for simple Web applications, monitoring or logging applications, and analysis programs. Only non-transactional storage engine MyISAM will be activated.

(9) Select the storage location of the InnoDB database file:

(10) Set approximate number of concurrent connections to the server:

Decision Support (DSS)/olap	Decision Support System (DSS) and OLAP	Select This option for database applications, that is, require a high number of concurrent connections. A number of connections would be assumed.	Select this option for database applications that do not require a large number of concurrent connections. The number of 20 connections will be assumed.
Online Transaction Processing (OLTP)	Online transaction processing (OLTP)	Choose This option for highly concurrent application The May has at any one time up to active connections such as he avily loaded Web servers.	Select this option for high concurrent applications, and the application may have up to 500 active connections at any time, such as overloaded Web servers.
Manual Setting	Manually set	Please enter the approximate number of concurrent	Please enter an approximate number of concurrent

(11) Set network options: 3306 ports

Enable TCP/IP Networking	Enable TCP/IP networking	Enable this to alllow TCP/IP connections. When Disabled,only local connections through named Pipes is allowed. ADD firewall exceptionfor this port.	Enable this entry to allow TCP/IP connections. When disabled, only local connections through named Pipes are allowed. Add a firewall exception to this port.
Enable Strict Mode	Enable Strict mode	This option forces the server to behave more like a traditional database server. It is recommended to enable the this option.	This option forces the server to be more like a traditional database server. It is recommended that you enable this option.

(12) Select the default character set: Utf-8

Standard Character Set	Standard Character Set	Makes Latin1 the default charset. This character set was suited for 中文版 and other West European languages.	Using Latin1 as the default character set, this character set is suitable for English and other European languages.
Best support for Multilingualism	Best support for multiple languages	Make UTF8 the default character set. The recommended character set for storing text in many different languages.	Using UTF8 as the default character set, this is the recommended character set for storing text in many different languages.
Manual Selected Default Character set/collation	Manually select the default character set/Sort	Specify the character set to use	Please specify the character set to use

(13) Set Windows options:

Install as Windows Service	Install as a Windows service	This is the recommended-to run of the MySQL server on Windows. Launch the MySQL Server automatically	This is the recommended way for a MySQL server to run on Windows. Automatically start the MySQL server
Include Bin Directory in Windows PATH	Add to Windows path path	Check This option to include the directory containing the server/client executables in the Windows PATH variable so they c An is called from the command line.	Select this option to include the directory Server/client executable file in the Windows path variable , so they can be called from the command line.

(14) Set security options: Set password (cannot be empty)

Modify Security Settings	Modify security Settings	Enable root access from remote machines	Allows access to the root from a remote machine
Create an anonymous account	Create an anonymous account	This option would create an anonymous account on the this server. Please note the This can leads to the insecure system.	This option creates an anonymous account on the server. Please note that this can lead to unsafe systems.

(15) Click "Execute" to start the configuration, (the period may occur 1-5 minutes not responding, normal behavior) until the installation is complete.

(16) Check whether the installation is successful: ①mysql comes with a command-line login tool: Start → All programs →mysql→mysql Server 5.5→mysql 5.5 Command lines Client, open, enter password, The ability to log on to MySQL instructions was successfully installed. ② Login with cmd command line: mysql-h localhost-u root-p Password

③windows Service will be known as "MySQL" service:

MySQL Introduction and Installation