MySQL數據庫學習筆記（一）----MySQL 5.6.21的安裝和配置（setup版）

【聲明】 

歡迎轉載，但請保留文章原始出處→_→ 

生命壹號：http://www.cnblogs.com/smyhvae/

文章來源：http://www.cnblogs.com/smyhvae/p/4026782.html

 

【正文】

【開發環境】

物理機版本：Win 7旗艦版（64位）

MySQL版本：5.5.40MSI版（64位）

1、數據庫類型：

（1）關係數據庫

（2）面向對象數據庫

（3）XML數據庫

如今的主流是關係型數據庫。

 

2、數據庫產品：

• 大型數據庫有：Oracle、Sybase、DB二、SQL server
• 小型數據庫有：MySQL、Access等

上面列舉的數據庫都是關係型數據庫，只是Oracle中有一小部分是面向對象的。MySQL具備開源、免費等特性，適合中小型企業的開發。

 

3、關係型數據庫的基本概念：

關係型數據庫是由多個表（table）和表之間的關聯關係組成的數據的集合，表是一個由若干行、若干列組成的二維的關係結構。

上圖中，表的列稱爲字段（field），表的行成爲記錄（record）。字段是表的結構，記錄是表的數據。

4、MySQL的下載：

官網下載地址：http://www.mysql.com/：

上圖中，能夠看到MySQL有三個版本：企業版、集羣版、社區版。社區版就是咱們所須要的版本，GPL是一種開源的協議。點擊上圖中紅框中的連接，進入另一個界面：

上圖中，咱們選擇紅框部分的社區版本進行下載，彈出以下界面：

下圖中，能夠看到MySQL支持許多平臺：

個人操做系統是64位的，我選擇對應版本（MSI版）進行下載，點擊上圖中紅框部分的連接，進入以下界面：

上圖中，點擊紅框部分進行下載，彈出以下界面：

上圖中，咱們不須要註冊，點擊紅框部分，直接下載便可。

 

5、MySQL的安裝：

雙擊安裝包時，出現了這個錯誤：

好吧，沒想到官網下載的軟件都能出問題。算了，我仍是下老版本的吧。

點擊上圖中紅框部分，彈出以下界面：

上圖中，點擊紅框部分，彈出以下界面：

不用註冊，直接下載吧。。。

 

5、MySQL的安裝：

軟件下載完成後，就開始安裝吧。

上圖中，建議選擇第二項的Custom，自定義安裝。彈出以下界面：

上圖中，選擇合適的安裝路徑，點擊「繼續」：

以後跳出另外一個對話框，是讓咱們安裝一個可視化的工具：

上圖中，咱們勾選紅框部分，而後點擊「finish」，進行配置。

 

6、MySQL的配置：

 

 

 

上圖的解釋：從此在Java開發中，要對這個服務器進行訪問，就要涉及到通訊的協議，這裏使用TCP/IP協議，此時就涉及到了端口，MySQL默認的端口號爲3306，使用默認的便可。繼續下一步：

 

上圖中，是選擇數據庫的編碼。第一種是拉丁文，只支持英文，不支持中文；第二種貌似是和日語有關的。這裏咱們選擇第三種：自定義。而後將編碼方式設置爲：utf-8。下一步：

上圖中，咱們勾選「路徑添加到環境變量」，而後繼續：

上圖中，是給root用戶設置密碼。這裏，我將密碼設置爲smyh。另外，勾選「容許用戶遠程（網路）訪問」，不然只能在本地訪問，繼續：

上面的勾會自動打的：

上圖中，能夠看到，咱們的配置被寫在了my.ini這個文件中了。

點擊finish，完成安裝。咱們再到對應目錄下看一下my.ini文件的內容：

# 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
# (@localstatedir@ 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 
# "--defaults-file". 
#
# 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.
#
[client]
port=3306
[mysql]
default-character-set=utf8
# 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 
# file.
#
[mysqld]
# The TCP/IP Port the MySQL Server will listen on
port=3306
#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
character-set-server=utf8
# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB
# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
# 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.
max_connections=100
# 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.
query_cache_size=0
# 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]
table_cache=256
# 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.
tmp_table_size=34M
# 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.)
thread_cache_size=8
#*** 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).
myisam_max_sort_file_size=100G
# 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.
myisam_sort_buffer_size=68M
# 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.
key_buffer_size=55M
# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K
# 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.
sort_buffer_size=256K
#*** 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.
#skip-innodb
# 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.
innodb_additional_mem_pool_size=3M
# 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.
innodb_flush_log_at_trx_commit=1
# 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_log_buffer_size=2M
# 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.
innodb_buffer_pool_size=106M
# 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.
innodb_log_file_size=53M
# 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.
innodb_thread_concurrency=8

View Code

 

同時，咱們在開始菜單的程序中也能看到已經安裝好的程序了：

點擊它，開始運行：

打開」計算機管理「能夠看到MySQL的服務已啓動：

同時在進程中也能夠看到：

 

5、MySQL的卸載：

一、到控制面板裏面先把mysql軟件刪除；

二、刪除mysql的安裝目錄（若是在其餘盤還有設置目錄也要刪除，空目錄也要刪除）；

三、刪除註冊表中的如下文件：（按"Win+R"鍵，輸入regedit，進入註冊表）：

• HKEY_LOCAL_MACHINE/SYSTEM/ControlSet001/Services/Eventlog/Applications/MySQL
• HKEY_LOCAL_MACHINE/SYSTEM/ControlSet002/Services/Eventlog/Applications/MySQL
• HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Eventlog/Applications/MySQL

有的話所有刪除（技巧：用F3循環查找「mysql」）;

四、若是是windows 7 系統，還須要找到C:\ProgramData\MYSQL將其刪除；若是是XP系統，刪除找到C:\Documents and Settings\All Users\Application Data\MYSQL

完成後便可再次安裝，不須要重啓系統。