mysql配置文件（Windows）

1.位置

在Windows上，默认情况下，MySQL的配置文件位于C:\ProgramData\MySQL\MySQL Server X.X\my.ini，其中的X.X表示你所安装的具体版本号。

C:\ProgramData\MySQL\MySQL Server 8.0

配置文件一般为 my.ini（MySQL 8.0 之前版本）或 my.cnf（MySQL 8.0 及以后版本）

2.my.ini

# Other default tuning values
# MySQL Server Instance Configuration File
[client]

# pipe=

# socket=MYSQL

port=3306

[mysql]
no-beep

# default-character-set=

# 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.
#
# server_type=3
[mysqld]

# The next three options are mutually exclusive to SERVER_PORT below.
# skip-networking
# enable-named-pipe
# shared-memory

# shared-memory-base-name=MYSQL

# The Pipe the MySQL Server will use.
# socket=MYSQL

# The access control granted to clients on the named pipe created by the MySQL Server.
# named-pipe-full-access-group=

# 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="C:/Program Files/MySQL/MySQL Server 8.0/"

# Path to the database root
datadir=C:/ProgramData/MySQL/MySQL Server 8.0\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=


# Administers multifactor authentication (MFA) capabilities. It applies to the authentication
# factor-related clauses of CREATE USER and ALTER USER statements used to manage MySQL account
# definitions, where "factor" corresponds to an authentication method or plugin associated
# with an account.
authentication_policy=mysql_native_password,,

# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB

# The current server SQL mode, which can be set dynamically.
# Modes affect the SQL syntax MySQL supports and the data validation checks it performs. This 
# makes it easier to use MySQL in different environments and to use MySQL together with other 
# database servers.
sql-mode="ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION"

# General and Slow logging.
log-output=FILE

general-log=1

# general_log_file="LAPTOP-BN9EG6N3.log"
general_log_file="D:/java/mysql/general.log"

slow-query-log=1

# slow_query_log_file="LAPTOP-BN9EG6N3-slow.log"
slow_query_log_file="D:/java/mysql/slow_query.log"

long_query_time=10

# Error Logging.
#log-error="LAPTOP-BN9EG6N3.err"
log-error="D:/java/mysql/error.log"
# ***** Group Replication Related *****
# Specifies the base name to use for binary log files. With binary logging
# enabled, the server logs all statements that change data to the binary
# log, which is used for backup and replication.
log-bin="LAPTOP-BN9EG6N3-bin"

# ***** Group Replication Related *****
# Specifies the server ID. For servers that are used in a replication topology,
# you must specify a unique server ID for each replication server, in the
# range from 1 to 2^32 − 1. "Unique" means that each ID must be different
# from every other ID in use by any other source or replica.
server-id=1

# Indicates how table and database names are stored on disk and used in MySQL.
# Value 0 = Table and database names are stored on disk using the lettercase specified in the CREATE 
#           TABLE or CREATE DATABASE statement. Name comparisons are case-sensitive. You should not 
#           set this variable to 0 if you are running MySQL on a system that has case-insensitive file 
#           names (such as Windows or macOS). If you force this variable to 0 with 
#           --lower-case-table-names=0 on a case-insensitive file system and access MyISAM tablenames 
#           using different lettercases, index corruption may result.
# Value 1 = Table names are stored in lowercase on disk and name comparisons are not case-sensitive. 
#           MySQL converts all table names to lowercase on storage and lookup. This behavior also applies 
#           to database names and table aliases.
# Value 2 = Table and database names are stored on disk using the lettercase specified in the CREATE TABLE 
#           or CREATE DATABASE statement, but MySQL converts them to lowercase on lookup. Name comparisons 
#           are not case-sensitive. This works only on file systems that are not case-sensitive! InnoDB 
#           table names and view names are stored in lowercase, as for lower_case_table_names=1.
lower_case_table_names=1

# This variable is used to limit the effect of data import and export operations, such as 
# those performed by the LOAD DATA and SELECT ... INTO OUTFILE statements and the 
# LOAD_FILE() function. These operations are permitted only to users who have the FILE privilege.
secure-file-priv="C:/ProgramData/MySQL/MySQL Server 8.0/Uploads"

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

# The number of open tables for all threads. Increasing this value increases the number 
# of file descriptors that mysqld requires.
table_open_cache=4000

# Defines the maximum amount of memory that can be occupied by the TempTable 
# storage engine before it starts storing data on disk.
temptable_max_ram=1G

# Defines the maximum size of internal in-memory temporary tables created 
# by the MEMORY storage engine and, as of MySQL 8.0.28, the TempTable storage 
# engine. If an internal in-memory temporary table exceeds this size, it is 
# automatically converted to an on-disk internal temporary table.
tmp_table_size=62M

# The storage engine for in-memory internal temporary tables (see Section 8.4.4, "Internal 
# Temporary Table Use in MySQL"). Permitted values are TempTable (the default) and MEMORY.
internal_tmp_mem_storage_engine=TempTable

#*** MyISAM Specific options
# The maximum size of the temporary file that MySQL is permitted to use while re-creating a 
# MyISAM index (during REPAIR TABLE, ALTER TABLE, or LOAD DATA). If the file size would be 
# larger than this value, the index is created using the key cache instead, which is slower. 
# The value is given in bytes.
myisam_max_sort_file_size=2146435072

# The size of the buffer that is allocated when sorting MyISAM indexes during a REPAIR TABLE 
# or when creating indexes with CREATE INDEX or ALTER TABLE.
myisam_sort_buffer_size=115M

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

# Each thread that does a sequential scan for a MyISAM table allocates a buffer 
# of this size (in bytes) for each table it scans. If you do many sequential 
# scans, you might want to increase this value, which defaults to 131072. The 
# value of this variable should be a multiple of 4KB. If it is set to a value 
# that is not a multiple of 4KB, its value is rounded down to the nearest multiple 
# of 4KB.
read_buffer_size=128K

# This variable is used for reads from MyISAM tables, and, for any storage engine, 
# for Multi-Range Read optimization.
read_rnd_buffer_size=256K

#*** INNODB Specific options ***
# innodb_data_home_dir=

# 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

# 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 in bytes of the buffer that InnoDB uses to write to the log files on 
# disk. The default value changed from 8MB to 16MB with the introduction of 32KB 
# and 64KB innodb_page_size values. A large log buffer enables large transactions 
# to run without the need to write the log to disk before the transactions commit. 
# Thus, if you have transactions that update, insert, or delete many rows, making 
# the log buffer larger saves disk I/O.
innodb_log_buffer_size=16M

# The size in bytes of the buffer pool, the memory area where InnoDB caches table 
# and index data. The default value is 134217728 bytes (128MB). The maximum value 
# depends on the CPU architecture; the maximum is 4294967295 (232-1) on 32-bit systems 
# and 18446744073709551615 (264-1) on 64-bit systems. On 32-bit systems, the CPU 
# architecture and operating system may impose a lower practical maximum size than the 
# stated maximum. When the size of the buffer pool is greater than 1GB, setting 
# innodb_buffer_pool_instances to a value greater than 1 can improve the scalability on 
# a busy server.
innodb_buffer_pool_size=128M


# Defines the maximum number of threads permitted inside of InnoDB. A value 
# of 0 (the default) is interpreted as infinite concurrency (no limit). This 
# variable is intended for performance tuning on high concurrency systems.
# InnoDB tries to keep the number of threads inside InnoDB less than or equal to 
# the innodb_thread_concurrency limit. Once the limit is reached, additional threads 
# are placed into a "First In, First Out" (FIFO) queue for waiting threads. Threads 
# waiting for locks are not counted in the number of concurrently executing threads.
innodb_thread_concurrency=17

# The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.
innodb_autoextend_increment=64

# The number of regions that the InnoDB buffer pool is divided into.
# For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
# by reducing contention as different threads read and write to cached pages.
innodb_buffer_pool_instances=8

# Determines the number of threads that can enter InnoDB concurrently.
innodb_concurrency_tickets=5000

# Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
# it can be moved to the new sublist.
innodb_old_blocks_time=1000

# When this variable is enabled, InnoDB updates statistics during metadata statements.
innodb_stats_on_metadata=0

# When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table
# in a separate .ibd file, rather than in the system tablespace.
innodb_file_per_table=1

# Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none.
innodb_checksum_algorithm=0

# If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
# synchronize unflushed data to disk.
# This option is best used only on systems with minimal resources.
flush_time=0

# The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
# indexes and thus perform full table scans.
join_buffer_size=256K

# The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
# mysql_stmt_send_long_data() C API function.
max_allowed_packet=64M

# If more than this many successive connection requests from a host are interrupted without a successful connection,
# the server blocks that host from performing further connections.
max_connect_errors=100

# The number of file descriptors available to mysqld from the operating system
# Try increasing the value of this option if mysqld gives the error "Too many open files".
open_files_limit=8161

# If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
# sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
# or improved indexing.
sort_buffer_size=256K

# Specify the maximum size of a row-based binary log event, in bytes.
# Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.
binlog_row_event_max_size=8K


# If the value of this variable is greater than 0, a replica synchronizes its master.info file to disk.
# (using fdatasync()) after every sync_source_info events.
sync_source_info=10000

# If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.
# (using fdatasync()) after every sync_relay_log writes to the relay log.
sync_relay_log=10000

# If the value of this variable is greater than 0, a replica synchronizes its relay-log.info file to disk.
# (using fdatasync()) after every sync_relay_log_info transactions.
sync_relay_log_info=10000

# Load mysql plugins at start."plugin_x ; plugin_y".
# plugin_load

# The TCP/IP Port the MySQL Server X Protocol will listen on.

3.参数介绍

[mysqld] 部分

• basedir: MySQL安装目录的路径。

• datadir: MySQL数据目录的路径，即数据库文件存储的地方。

• port: MySQL服务器监听的端口号，默认为3306。

• server-id: 服务器唯一ID，用于复制和集群配置。

• socket: MySQL服务器使用的套接字文件的路径，用于本地连接。

• pid-file: MySQL服务器进程ID文件的路径。

• tmpdir: 用于存储临时文件的目录。

• character-set-server: 服务器默认字符集，例如utf8mb4。

• collation-server: 服务器默认排序规则。

• init-connect: 当客户端连接时执行的SQL语句。

• max_connections: 允许的最大并发连接数。

• table_open_cache: 打开表的缓存数。

• thread_cache_size: 线程缓存的大小。

• innodb_buffer_pool_size: InnoDB存储引擎的缓冲池大小。

• innodb_log_file_size: InnoDB重做日志文件的大小。

• innodb_log_buffer_size: InnoDB重做日志缓冲区的大小。

• innodb_file_per_table: 是否为每个InnoDB表使用单独的表空间文件。

• innodb_flush_log_at_trx_commit: 控制InnoDB日志刷新的频率。

• innodb_flush_method: 控制InnoDB文件刷新到磁盘的方法。

• query_cache_type: 查询缓存的开启状态。

• query_cache_size: 查询缓存的大小。

• max_allowed_packet: 客户端和服务器之间传输的最大数据包大小。

• log_error: 错误日志文件的路径。

• slow_query_log: 是否启用慢查询日志。

• slow_query_log_file: 慢查询日志文件的路径。

• long_query_time: 慢查询的阈值，以秒为单位。

• log_queries_not_using_indexes: 记录未使用索引的查询。

• expire_logs_days: 二进制日志的过期天数。

• sync_binlog: 控制二进制日志同步的频率。

• binlog_format: 二进制日志的格式（例如ROW, STATEMENT, MIXED）。

• secure_file_priv: 限制LOAD DATA, SELECT ... INTO OUTFILE, LOAD_FILE()函数能访问的目录。

[client] 部分

• port: 客户端连接的MySQL服务器端口。

• socket: 用于本地连接的套接字文件的路径。

• default-character-set: 客户端默认字符集。

[mysql] 部分

• 这个部分通常用于MySQL客户端工具的配置。

4.日志

在Windows上查看MySQL的日志，通常指的是查看错误日志、查询日志或慢查询日志。以下是如何查看这些日志的方法：

错误日志：默认情况下，错误日志文件名为hostname.err，位于MySQL数据目录中（通常是C:\ProgramData\MySQL\MySQL Server X.Y\Data）。

查询日志：可以通过设置general_log和general_log_file变量来启用查询日志，记录所有MySQL服务器处理的通用查询。

慢查询日志：通过设置slow_query_log和slow_query_log_file变量启用慢查询日志，记录执行时间超过long_query_time秒的查询。

可以通过以下方式查看日志：

• 直接打开日志文件，例如，使用文本编辑器。

• 使用MySQL提供的日志查看工具，如mysqlbinlog。

例如，查看慢查询日志：

SHOW VARIABLES LIKE 'slow_query_log';
SHOW VARIABLES LIKE 'slow_query_log_file';
SHOW VARIABLES LIKE 'long_query_time';

启用并查看慢查询日志内容：

SET GLOBAL slow_query_log = 'ON';
SET GLOBAL long_query_time = 2; -- 设置慢查询的阈值为2秒

5.修改日志文件位置

general-log=1

# general_log_file="LAPTOP-BN9EG6N3.log"
general_log_file="D:/java/mysql/general.log"

slow-query-log=1

# slow_query_log_file="LAPTOP-BN9EG6N3-slow.log"
slow_query_log_file="D:/java/mysql/slow_query.log"

long_query_time=10

# Error Logging.
#log-error="LAPTOP-BN9EG6N3.err"
log-error="D:/java/mysql/error.log"

重启 MySQL 服务，使配置生效。

6.mysql windows重启

在Windows环境下重启MySQL服务，可以通过命令行界面（CLI）来完成。以下是重启MySQL服务的步骤：

打开命令提示符（CMD）：

可以通过按下Win + R键打开运行对话框，输入cmd，然后按下Enter键。

停止MySQL服务：

net stop mysql80

注意：这里的MySQL是服务的名称，如果你的MySQL服务名称不是这个，请替换成正确的服务名称。

启动MySQL服务：

net start mysql80

同样，确保使用的是正确的服务名称。

如果你想要让这个过程自动化，可以创建一个包含上述命令的批处理文件（.bat），然后每次需要重启MySQL时，只需要运行这个批处理文件即可。

例如，创建一个名为restart_mysql.bat的文件，并在文件中输入以下内容：

net stop mysql80
net start mysql80

然后，双击restart_mysql.bat文件或者在CMD中运行它：

restart_mysql.bat

这样，你就可以通过运行批处理文件来快速重启MySQL服务了。