本文目录一览：
怎样彻底删除MySQL数据库
一、在控制面板，卸载MySQL的所有组件
控制面板——》所有控制面板项——》程序和功能，卸载所有和MySQL有关的程序
二、找到你的MysQL安装路径，看还有没有和MySQL有关的文件夹，全删
如果安装在C盘，检查一下C:\Program Files (x86)和C:\Program Files 这两个文件夹
三、删除关于MySQL的注册表
在文件资源管理器中输入“C:\Windows\regedit.exe"会弹出注册表
删除HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\Application\MySQL文件夹
如果能找到如下内容，删除
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Eventlog\Application\MySQL
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\MySQL
四、将以下红字部分粘贴到文件资源管理器地址栏中 （这是一个隐藏的文件夹）
C:\ProgramData\MySQL
删除此文件夹下的所有内容
五、重启电脑
六、提示：
如果以上删除文件夹时删除不了，可以试一下以下步骤：
1.检查是否还有有关MySQL的程序在运行，到任务管理器中去找，然后结束任务
2.试试360粉碎文件能不能粉碎
3.进入安全模式，删除
大功告成
现在可以重新安装MySQL了
如何在Windows中完全卸载MySQL数据库
并且有可能产生其他的问题，最好的办法是给自己一个空白的环境，这样我们就可以排除MySQL安装不成功造成的错误。
具体卸载步骤如下：
1.
在你从电脑里卸载旧的MYSQL数据库服务时，首先先在WINDOWS服务里停掉MYSQL的服务。
2.
再到控制面板里的增加删除程序内进行删除。
3.
但是你并不能完整的把MYSQL服务删除，那么就要在注册表里(regedit)清除你的MYSQL服务。这里有几个地方:
HKEY_LOCAL_MACHINE/SYSTEM/ControlSet001/Services/Eventlog/Application/MySQL
目录删除;
HKEY_LOCAL_MACHINE/SYSTEM/ControlSet002/Services/Eventlog/Application/MySQL
目录删除;
如何完全卸载MySQL数据库
您好，首先要有：1、数据库：MySQL 5.7
2、安装包：mysql-installer-community-5.7.4.0-m14.1411728256.msi
之后就可以这样：
1、双击MySQL数据库的.msi安装文件，进入MySQL安装界面。
2、在MySQL安装界面，点击"Remove MySQL Products"（卸载MySQL产品）。
3、在卸载产品界面，单击"Execute"（执行）。
4、弹出是否确认删除窗口，单击"是（Y）"。等待MySQL待卸载产品准备就绪后单击"Next"。
5、进入清空现有数据界面，勾选"uninstall the mysql installer"(卸载MySQL安装程序)，单击"Finish"完成MySQL数据库的完全卸载。
如何删除mysql数据库
1、找到mysql安装所在的文件夹,将mysql的配置文件my.ini备份一下。
2、删除mysql安装所在的文件夹
3、打开我的电脑
4、找到programdata
5、打开programdata并找到mysql文件夹并将其删除
6、如果找不到programdata或mysql文件夹，可以在工具栏中找到工具选项
7、在工具选项卡中找到查看文件夹,并将“显示隐藏文件夹、文件”选中保存即可
8、找到Mysql文件后将其删除即可。
centos中怎么删除mysql数据库
查看已经安装的服务
rpm –qa|grep -i mysql
-i 作用是不区分大小写
yum remove mysql mysql-server mysql-libs compat-mysql51
rm -rf /var/lib/mysql
rm /etc/my.cnf
查看是否还有mysql软件：
rpm -qa|grep mysql
有的话继续删除
可以看到有两个安装包
MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
MySQL-client-5.6.19-1.linux_glibc2.5.x86_64.rpm
删除这两个服务(去掉后缀)
rpm –e MySQL-client-5.6.19-1.linux_glibc2.5.x86_64
rpm -e MySQL-server-5.6.19-1.linux_glibc2.5.x86_64
查看残留的目录：
whereis mysql
然后删除mysql目录：
rm –rf /usr/lib64/mysql
删除相关文件：
rm –rf /usr/my.cnf
rm -rf /root/.mysql_sercret
最关键的：
rm -rf /var/lib/mysql
如果这个目录如果不删除，再重新安装之后，密码还是之前的密码，不会重新初始化！
网上查了很久都没有文章提到这个，最后还是自己摸索找出来的。
卸载完成！怎么确定是不是真的卸载干净了呢？
一是看安装输出：
如果没有卸载干净，安装server时输入只有两行：
[root @localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
Preparing... ########################################### [100%]
1:MySQL-server ########################################### [100%]
卸载干净了安装输入如下：
[root @localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
Preparing... ########################################### [100%]
1:MySQL-server ########################################### [100%]
2014-09-23 07:22:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-09-23 07:22:43 26041 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-09-23 07:22:43 26041 [Note] InnoDB: The InnoDB memory heap is disabled
2014-09-23 07:22:43 26041 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-09-23 07:22:43 26041 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-09-23 07:22:43 26041 [Note] InnoDB: Using Linux native AIO
2014-09-23 07:22:43 26041 [Note] InnoDB: Using CPU crc32 instructions
2014-09-23 07:22:43 26041 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-09-23 07:22:43 26041 [Note] InnoDB: Completed initialization of buffer pool
2014-09-23 07:22:43 26041 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2014-09-23 07:22:43 26041 [Note] InnoDB: Database physically writes the file full: wait...
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2014-09-23 07:22:45 26041 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2014-09-23 07:22:45 26041 [Warning] InnoDB: New log files created, LSN=45781
2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer not found: creating new
2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer created
2014-09-23 07:22:45 26041 [Note] InnoDB: 128 rollback segment(s) are active.
2014-09-23 07:22:45 26041 [Warning] InnoDB: Creating foreign key constraint system tables.
2014-09-23 07:22:45 26041 [Note] InnoDB: Foreign key constraint system tables created
2014-09-23 07:22:45 26041 [Note] InnoDB: Creating tablespace and datafile system tables.
2014-09-23 07:22:45 26041 [Note] InnoDB: Tablespace and datafile system tables created.
2014-09-23 07:22:45 26041 [Note] InnoDB: Waiting for purge to start
2014-09-23 07:22:45 26041 [Note] InnoDB: 5.6.19 started; log sequence number 0
A random root password has been set. You will find it in '/root/.mysql_secret'.
2014-09-23 07:22:46 26041 [Note] Binlog end
2014-09-23 07:22:46 26041 [Note] InnoDB: FTS optimize thread exiting.
2014-09-23 07:22:46 26041 [Note] InnoDB: Starting shutdown...
2014-09-23 07:22:48 26041 [Note] InnoDB: Shutdown completed; log sequence number 1625977
2014-09-23 07:22:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-09-23 07:22:48 26065 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-09-23 07:22:48 26065 [Note] InnoDB: The InnoDB memory heap is disabled
2014-09-23 07:22:48 26065 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-09-23 07:22:48 26065 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-09-23 07:22:48 26065 [Note] InnoDB: Using Linux native AIO
2014-09-23 07:22:48 26065 [Note] InnoDB: Using CPU crc32 instructions
2014-09-23 07:22:48 26065 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-09-23 07:22:48 26065 [Note] InnoDB: Completed initialization of buffer pool
2014-09-23 07:22:48 26065 [Note] InnoDB: Highest supported file format is Barracuda.
2014-09-23 07:22:48 26065 [Note] InnoDB: 128 rollback segment(s) are active.
2014-09-23 07:22:48 26065 [Note] InnoDB: Waiting for purge to start
2014-09-23 07:22:48 26065 [Note] InnoDB: 5.6.19 started; log sequence number 1625977
2014-09-23 07:22:48 26065 [Note] Binlog end
2014-09-23 07:22:48 26065 [Note] InnoDB: FTS optimize thread exiting.
2014-09-23 07:22:48 26065 [Note] InnoDB: Starting shutdown...
2014-09-23 07:22:50 26065 [Note] InnoDB: Shutdown completed; log sequence number 1625987
A RANDOM PASSWORD HAS BEEN SET FOR THE MySQL root USER !
You will find that password in '/root/.mysql_secret'.
You must change that password on your first connect,
no other statement but 'SET PASSWORD' will be accepted.
See the manual for the semantics of the 'password expired' flag.
Also, the account for the anonymous user has been removed.
In addition, you can run:
/usr/bin/mysql_secure_installation
which will also give you the option of removing the test database.
This is strongly recommended for production servers.
See the manual for more instructions.
Please report any problems at
The latest information about MySQL is available on the web at
Support MySQL by buying support/licenses at
New default config file was created as /usr/my.cnf and
will be used by default by the server when you start it.
You may edit this file to change server settings
最后一段中提示了重要信息，很多人因为不喜欢读英文，导致接下来不知道怎么操作！
二就是安装完成，启动服务之后
使用命令：“mysql -uroot -p”输入你之前安装后设置的密码，看能不能登录，如果还可以登录，说明没有卸载干净！
