MySQL5.5安装到最后一步一直无响应的解决方案

昨天卸载了mysql8.0由于卸载不干净,导致安装5.5版本到最后一步始终无响应,我重置了系统,结果安装到最后一步他又是始终无响应,然后我参考了两位大佬的解决方案如下
大佬方案一
大佬方案二

两个方案都试了一遍后我的安装还是不行
如下图:
在这里插入图片描述

我的最终解决方案是这样的

进入服务,我发现我的服务里没有MySQL!!!

1.先打开自己的安装目录下看看有没有my.ini文件,如果没有就到桌面新建一个txt文本,名字改为my.ini,里面的内容可复制本文最下方的,然后把这个文件复制到安装目录下,向这样,注意后缀是ini,而不是txt;(更改后缀,不会的自己百度)
在这里插入图片描述
文件代码如下:

# 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]

#skip-grant-tables

# 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 (x86)/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=15M

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


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

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

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

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

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

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

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

注意:basedir="C:/Program Files (x86)/MySQL/MySQL Server 5.5/"这里把路径换成你自己的安装包路径

2.以管理员身份进入cmd命令,向图片中这样找到你的安装包路径
在这里插入图片描述
3.然后在命令行输入 mysqld.exe –install 回车 显示
Service successfully installed
再输入 net start mysql 回车 显示正在启动 启动成功 (如果没效果就可以尝试卸载MySQL重装,也是可能成功的)
4.去百度一下检查mysql是否安装成功的方法,对着查看一下

mysql的root的初始密码为空,就是你的密码没有,让你输密码你就回车

5.然后用navicat等可视化工具链接mysql,如果能成功链接那就可以了,如下图
在这里插入图片描述
到这里我的安装问题就解决了!!至于那个配置过程的卡死,我也没有办法,放弃吧。

下次一定要记住不要轻易卸载!!否则卸载不干净非常麻烦

  • 4
    点赞
  • 32
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
### 回答1: MySQL 5.5MySQL数据库管理系统的一个版本,而zip是一种常见的压缩文件格式。题目中的"mysql5.5zip"并不是一个常见的词组,无法直接解释。以下为对MySQL 5.5和zip的简单介绍: MySQL 5.5MySQL数据库的一个版本,它是2009年发布的,至今仍被广泛使用。MySQL是一个开源关系型数据库管理系统,被用于存储和管理大量结构化数据。MySQL 5.5在性能方面进行了优化,并增加了一些新功能,如Semi-Synchronous Replication,使数据库更加可靠和高效。 zip是一种常见的文件压缩格式,它可以将一个或多个文件或文件夹压缩成一个较小的文件,以节省存储空间和传输时间。压缩后的文件可以通过解压缩操作恢复为原始的文件或文件夹。 如果"mysql5.5zip"指的是将MySQL 5.5版本压缩成zip格式,这通常是为了方便传输或备份MySQL数据库。通过将数据库的文件和文件夹进行压缩,可以减少文件大小,并且可以更方便地进行移动和存储。压缩后的文件可以通过解压缩操作进行恢复,以重新创建MySQL 5.5数据库。 总之,MySQL 5.5是一个数据库管理系统的版本,而zip是一种常见的文件压缩格式。如果"mysql5.5zip"指的是将MySQL 5.5版本压缩成zip格式,那么可以通过这种方式方便地传输和备份MySQL数据库。 ### 回答2: MySQL 5.5zip是指MySQL数据库的一个版本,这个版本是以压缩格式(zip)进行发布和分发的。MySQL是一种关系型数据库管理系统,被广泛应用于各种Web应用程序的开发中。MySQL 5.5MySQL数据库的一个较为成熟和稳定的版本,它在性能、安全性和功能等方面都有很好的表现。 MySQL 5.5zip的压缩格式使得安装和部署变得更加简便和快速。用户可以通过解压zip文件,并进行一些简单的配置设置,就能够轻松地安装MySQL 5.5数据库。同时,这种格式也方便了软件的传播和分发,用户可以直接下载zip文件,并进行安装使用,省去了繁琐的安装步骤。 MySQL 5.5zip作为一个数据库管理系统,具备了很多功能和特性。它支持ACID(原子性、一致性、隔离性和持久性)事务,可以保证数据的完整性和安全性。同时,MySQL 5.5zip还提供了丰富的查询语句和灵活的数据操作方式,支持多种编程语言的开发接口,方便开发人员进行数据库的开发和维护工作。 除此之外,MySQL 5.5zip还具备良好的性能表现。它通过各种优化手段,提高了数据库的读写效率和响应速度,能够在高并发的情况下保持较低的系统负载。这使得MySQL 5.5zip在大规模、高访问量的Web应用场景下表现出色。 总之,MySQL 5.5zip是MySQL数据库的一个特定版本,它通过压缩格式的发布和分发,简化了安装和部署的步骤。这个版本具备了丰富的功能和特性,可以满足不同应用场景下的需求,并且拥有良好的性能表现。 ### 回答3: MySQL 5.5 Zip是指MySQL数据库的一个压缩文件版本。MySQL是一个开放源码的关系型数据库管理系统。它提供了一个高效,可靠和安全的数据存储和检索解决方案,被广泛用于各种网站和应用程序的开发中。 MySQL 5.5 Zip是将MySQL 5.5版包装成一个ZIP压缩文件的形式。这种形式使得在安装和使用MySQL时更加方便和简单。用户只需下载MySQL 5.5 Zip文件,解压缩到目标文件夹,然后进行必要的配置和初始化,就可以开始使用MySQL数据库了。 MySQL 5.5版本是MySQL数据库管理系统的一个较旧的版本,虽然现在已经有了更高的版本,但MySQL 5.5仍然被许多用户广泛使用。MySQL 5.5具有许多功能和优点,如高性能,可扩展性,稳定性和易用性。 MySQL 5.5 Zip文件适用于那些希望使用MySQL 5.5版本并且需要快速和简便安装的用户。通过使用ZIP文件,用户可以避免繁琐的安装过程,只需解压缩文件即可使用MySQL 5.5数据库。 总之,MySQL 5.5 Zip是MySQL数据库的一种压缩文件形式,可以方便安装和使用MySQL 5.5版本,并提供高效、可靠和安全的数据存储和检索解决方案
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值