Windows下MySQL的綠化與精簡

　　MySQL本身就支援安裝使用，本文只是對自己使用免安裝版MySQL的經歷記錄下來，以便以後檢視。

　　首先是獲取Windows下的MySQL免安裝版本，這個需要去到MySQL官網進行下載。我一般喜歡把首頁頁面拖動到最下方，點選MySQL Server進入下載。

　　

　　我下載了MySQL5.5.33版本(zip包)。

　　得到的檔案就是mysql-5.5.33-win32.zip，解壓出來後我把名字改成了mysql。

　　

　　我們保留資料夾bin、data和share，其餘的資料夾可以刪除。

　　還需要一個my.ini作為配置檔案，zip包中的幾個ini是根據你物理機硬體水平進行選擇的，從<=64M到4G的記憶體。

　　我一般都直接刪除，然後沿用以前的ini檔案，你也可以選擇適合自己的my-*.ini進行配置然後改名為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="./mysql"

#Path to the database root
datadir="./mysql/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=35M


# 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=69M

# 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=107M

# 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=54M

# 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=10

　　上文中basedir和datadir比較重要，從名稱來看是指mysql的安裝路徑和資料檔案存放路徑，我已經修改了。

　　bin資料夾中的.pdb檔案是沒有存在感的，*test*.exe和*debug*.exe我也刪除了。

　　最後的檔案結構大概是這個樣子：

　　

　　COPYING是我特意留下的，你可以去除。

　　這個樣子就算OK了，我們可以使用批處理指令啟動MySQL了：

"./mysql/bin/mysqld.exe" --defaults-file=./mysql/my.ini

　　不過這個命令必須cd到mysql資料夾所在目錄進行，或者是將上面的語句儲存為*.bat(也要放到mysql同級目錄下)：

　　

　　啟動mysql.bat，mysql資料庫就開始工作了。

　　

　　這個視窗會卡住，但其實它是可以關閉的，關閉後mysql沒有被結束：

　　

　　我們登入進mysql：

　　

　　mysql的初始密碼是空，所以我們只需要在Enter password:後面敲擊回車(不要做任何輸入)即可進入系統。

　　我們先對root的密碼進行設定：

　　

　　然後刪除匿名使用者(匿名使用者就是登入名為空的使用者，它不需要密碼即可登入，對安全性有影響)。當然，先刪除匿名使用者再改root密碼也可以：　　

　　

　　現在，mysql資料庫就配置好了。

　　通過一個批處理命令和windows shell的結合，我們可以實現mysql只啟動一次且不卡住視窗：

tasklist | find /i "mysqld.exe"
if %errorlevel%==0 (exit) else goto stm
:stm
start /min "" "./mysql/bin/mysqld.exe" --defaults-file=./mysql/my.ini

　　(值得一提的是我們並沒有考慮將mysql作為系統服務，因為上文的路徑是相對路徑，理論上我們可以隨意移動。而服務要求路徑明確，不過服務的優勢在於比較方便地跟隨系統啟動和關閉，容易掛起等)

　　最後介紹一個我的思路，我通常會為一個專案維護一個資料庫，而且使用一個專門的使用者來進行管理。

　　比如我會使用如下語句來建立使用者：

grant all privileges on testdb.* to testuser identified by 'testuser';

　　上述語句可以在testdb還未建立時執行，而且testdb被刪除重建後testeuser仍然具有許可權。

　　不過上述語句沒有賦予testuser建立檢視的權利，所以我建議大家使用root完成檢視的建立。

 

 歡迎您移步我們的交流群，無聊的時候大家一起打發時間：

 或者通過QQ與我聯絡：

 （最後編輯時間2013-09-17 21:57:02）