Physical machine Version: Win 7 Ultimate Edition (64-bit)
MySQL version: Version 5.5.40MSI (64-bit)
First, the database type:
(1) Relational database
(2) Object-oriented database
(3) XML database
The current mainstream is the relational database.
Second, database products:
- Large databases are: Oracle, Sybase, DB2, SQL Server
- Small databases are: MySQL, access, etc.
The databases listed above are relational databases, but only a small part of Oracle is object-oriented. MySQL is open source, free and other features, suitable for small and medium-sized enterprise development.
Three, the basic concept of relational database:
A relational database is a collection of data that consists of multiple tables (table) and associations between tables, a two-dimensional relational structure that consists of several rows and several columns.
, the table's columns are called fields (field), and the rows of the table become Records (record). A field is the structure of a table, and a record is the data of a table.
Iv. mysql Download:
Official website: http://www.mysql.com/:
, you can see that there are three versions of MySQL: Enterprise Edition, Cluster Edition, Community Edition. The Community Edition is the version we need , and the GPL is an open source protocol. Click the link in the Red box to enter another interface:
, we select the community version of the Red box section to download and pop up the following screen:
, you can see that MySQL supports many platforms:
my operating system is 64-bit, I choose the corresponding version (MSI version) to download , click the link in the Red box section, enter the following interface:
, click on the Red box section to download, pop up the following screen:
, we do not need to register, click on the Red box section, directly download.
V. Installation of MySQL:
This error occurs when you double-click the installation package:
Well, I didn't expect the software to be downloaded on the website. Forget it, I'm still in the old version.
Click on the Red box section to pop up the following screen:
, click on the Red Box section to bring up the following screen:
Do not register, download it directly ...
V. Installation of MySQL:
Once the software download is complete, start the installation.
, it is recommended that you select custom for the second item, and then customize the installation. The following screen appears:
, select the appropriate installation path and click "Continue":
Then jumping out of another dialog is to let us install a visual tool:
, we tick the Red box section and click "Finish" to configure it.
Vi. configuration of MySQL:
Explanation: In Java development in the future, to access this server, it is related to the communication protocol, where the use of TCP/IP protocol, this time involves the port, MySQL default port number is 3306, using the default. Continue to the next step:
, the encoding of the database is selected. The first is Latin, only English is supported, Chinese is not supported, and the second seems to be related to Japanese. Here we choose the third type: Custom. Then set the encoding mode to: Utf-8. Next:
, we tick "add path to environment variable" and continue:
, the password is set for the root user. Here, I set the password to SMYH. In addition, check "Allow user remote (network) Access", otherwise only local access, continue:
The above tick will be automatically played:
, we can see that our configuration is written in the My.ini file.
Click Finish to complete the installation. Let's go to the corresponding directory and look at the contents of the My.ini file:
# MySQL Server Instance Configuration File
# Generated by the MySQL Server Instance Configuration Wizard
# Installation Instructions
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@[email protected] for this installation) or to
# ~/.my.cnf to set user-specific options.
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
# make sure the server reads the config file use the startup option
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
# And then execute this in a command line shell to start the server, e.g.
# net start MySQLXY
# Guildlines for editing this file
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
# More detailed information about the individual options can also be
# found in the manual.
# CLIENT SECTION
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
# SERVER SECTION
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# The TCP/IP Port the MySQL Server will listen on
#Path to installation directory. All paths are usually resolved relative to this.
basedir="D:/MySQL/MySQL Server 5.5/"
#Path to the database root
datadir="C:/ProgramData/MySQL/MySQL Server 5.5/Data/"
# The default character set that will be used when a new schema or table is
# created and no character set is defined
# The default storage engine that will be used when create new tables when
# Set the SQL mode to strict
# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client‘s threads are put in the cache if there aren‘t
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn‘t give a notable performance
# improvement if you have a good thread implementation.)
#*** MyISAM Specific options
# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you‘re not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
#*** INNODB Specific options ***
# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
At the same time, we can see the installed programs in the Start menu program as well:
Click on it to start running:
Open Computer Management to see that the MySQL service is started:
You can also see in the process:
V. MySQL Uninstall:
1, to the control panel inside the first to remove the MySQL software;
2, delete the MySQL installation directory (if the other disk also has a set directory to be deleted, empty directory also to delete);
3. Delete the following files in the registry: (Press "Win+r" key, enter Regedit, enter the registry):
Some words all delete (tip: Use F3 loop to find "MySQL");
4, if it is a Windows 7 system, also need to find C:\ProgramData\MYSQL to delete it; if it is an XP system, remove C:\Documents and Settings\All Users\Application Data\ Mysql
Once you are done, you can install again without rebooting the system.
MySQL Database Learning Note (i)----installation and configuration of MySQL-5.6.21 (Setup edition)