MySQL (64-bit)

最新版本 MySQL 5.6.19 (64-bit)

MySQL 5.6.19 (64-bit)

MySQL 5.6.19 (64-bit)
MySQL 64 位專為企業組織提供關鍵業務數據庫應用程序而設計。它為企業開發人員,數據庫管理員和 ISV 提供了一系列新的企業功能,以提高開發,部署和管理工業強度應用程序的效率.

如果您需要 MySQL 數據庫的 GUI,可以下載 - NAVICAT(MySQL GUI)。它支持將 MySQL,MS SQL,MS Access,Excel,CSV,XML 或其他格式導入到 MySQL.

MySQL 數據庫服務器提供了新的企業功能,包括:ACID 事務處理,以構建可靠和安全的業務關鍵型應用程序。存儲過程來提高開發人員的生產力。觸發器在數據庫級執行複雜的業務規則。保證敏感信息的觀點不受影響。信息架構,以便於訪問元數據。分佈式事務(XA)支持跨多個數據庫的複雜事務。下載適用於 Windows 的 64 位 MySQL 離線安裝程序安裝程序

Top 使用 MySQL 的 10 個理由:

可擴展性和靈活性 51235896 MySQL 數據庫服務器提供了極高的可擴展性,體現了處理深度嵌入式應用程序的能力,僅佔用 1MB 的空間以運行海量數據倉庫, information.

高性能
獨特的存儲引擎架構允許數據庫專業人員專門為特定應用程序配置 MySQL 數據庫服務器,最終的結果是驚人的性能結果.

高可用性
堅如磐石的可靠性和持續可用性是 MySQL 的標誌,客戶依賴於 MySQL 保證全天候正常運行.

Robust 交易支持
MySQL 64 位提供了市場上最強大的交易數據庫引擎之一。  功能包括完整的 ACID(原子性,一致性,隔離性,持久性)事務支持,無限的行級鎖定以及更多功能.

Web 和數據倉庫優勢
MySQL 是高流量網站的事實標準,因為它具有高性能的查詢引擎,極快的數據插入能力,以及對快速全文搜索等專業網頁功能的強大支持。下載 MySQL 離線安裝程序設置 64bit for Windows!

強大的數據保護
由於守衛企業的數據資產是數據庫專業人員的頭號工作,MySQL 提供了卓越的安全功能,確保絕對的數據保護.

綜合應用程序開發
MySQL 是世界上最流行的原因之一開源數據庫就是它為每個應用程序開發提供了全面的支持需求。在數據庫中,支持存儲過程,觸發器,函數,視圖,游標,ANSI 標準 SQL 等等。分鐘.

開源自由和 24×7 支持
許多公司都不願意完全致力於開源軟件,因為他們認為他們不能得到他們目前依靠專有軟件的支持類型或專業服務安全網,以確保他們的關鍵應用程序.

Lowest 總體擁有成本
By 將當前的數據庫驅動器應用程序遷移到 MySQL,或使用 MySQL 進行新的開發項目,企業正在實現成本節省,多次延伸到七位數.

也可用:下載 MySQL for Mac

ScreenShot

軟體資訊
檔案版本 MySQL 5.6.19 (64-bit)

檔案名稱 mysql-5.6.19-winx64.msi
檔案大小 40.86 MB
系統 Windows XP64 / Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64
軟體類型 開源軟體
作者 Oracle
官網 http://www.mysql.com/
更新日期 2014-06-02
更新日誌

What's new in this version:

Functionality Added or Changed:
- The obsolete and unmaintained charset2html utility has been removed from MySQL distributions. (Bug #71897, Bug #18352347)
- The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and will be removed in MySQL 5.7. Bugs Fixed:
- InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in an assertion failure. (Bug #18634201, Bug #72079)
- InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call. (Bug #17858679, Bug #71014)
- InnoDB: Enabling the InnoDB Table Monitor would result in a ib_table->stat_initialized assertion failure. (Bug #17039528, Bug #69641)
- InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages unflushed. Buffer pool flushing is initiated when the percentage of dirty pages is greater innodb_max_dirty_pages_pct. The internal variables that store the innodb_max_dirty_pages_pct value and the percentage of dirty pages (buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool flushing.
- To address this problem, the buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct internal variables are redefined as double data types, which changes the range value for innodb_max_dirty_pages_pct and innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer pool flushing is now initiated when the percentage of dirty pages is “greater than or equal to” innodb_max_dirty_pages_pct. (Bug #13029450, Bug #62534)
- Replication: Log rotation events could cause group_relay_log_pos to be moved forward incorrectly within a group. This meant that, when the transaction was retried, or if the SQL thread was stopped in the middle of a transaction following one or more log rotations (such that the transaction or group spanned multiple relay log files), part or all of the group was silently skipped.
- This issue has been addressed by correcting a problem in the logic used to avoid touching the coordinates of the SQL thread when updating the log position as part of a relay log rotation whereby it was possible to update the SQL thread's coordinates when not using a multi-threaded slave, even in the middle of a group. (Bug #18482854)
- Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by START SLAVE resulted in a mismatch between the information provided by INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables existed, but Slave_open_temp_tables had a nonzero value. (Bug #18364070)
- References: See also Bug #18236612.
- Replication: In certain cases, the server mishandled triggers and stored procedures that tried to modify other tables when called by CREATE TABLE ... SELECT. This is now handled correctly as an error. (Bug #18137535)
- Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave.
- Now in such cases TRUNCATE TABLE is logged only when it executes successfully. (Bug #17942050, Bug #71070)
- Replication: The server did not always handle the auto.cnf file correctly in cases where this file's permissions were incorrect. (Bug #17786581, Bug #70891)
- Replication: When the binary log was rotated due to receipt of a SIGHUP signal, the new binary log did not contain the Previous_gtid_event required for subsequent processing of that binary log's GTID events. Now when SIGHUP is received, steps are taken to insure that the server writes the necessary Previous_gtid_event to the new log before writing any GTID events to the new log. (Bug #17026898) Replication: When gtid_mode=ON, and a transaction is filtered out on the slave, the GTID of the transaction is still logged on the slave as an “empty” transaction (consisting of a GTID followed immediately by BEGIN and then COMMIT). This is necessary to prevent the transaction from being retransmitted the next time the slave reconnects or is involved in a failover. The current fix addresses two issues relating to such “empty” transactions:
- No empty transaction was generated for CREATE TEMPORARY TABLE or DROP TEMPORARY TABLE statements.
- If the slave used a database filter (--replicate-do-db or --replicate-ignore-db option), no empty transaction was generated.
- (Bug #71326, Bug #18095502, Bug #18145032)
- The server could fail to properly reprepare triggers that referred to another table after that table was truncated. (Bug #18596756)
- Certain INFORMATION_SCHEMA queries could cause a server exit. (Bug #18319790)
- For indexes on prefixes or character string columns, index corruption could occur for assignment of binary data to the column due to improper character counting. (Bug #18359924)
- Solaris-specific scripts were included in and installed by non-Solaris packages. (Bug #18305641)
- Concurrent execution of a FLUSH TABLE operation and a stored program that used a cursor could cause a server exit. (Bug #18158639)
- The client library could cause clients to exit due to incorrectly mapping the client error number to the corresponding message, if reallocation of packet buffer memory occurred. (Bug #18080920)
- Calling mysql_get_server_version() with an invalid connection handler argument caused the client to exit. Now it returns 0 and reports a CR_COMMANDS_OUT_OF_SYNC error. (Bug #18053212)
- mysqldump could create table definitions in the dump file that resulted in Too many columns errors when reloading the dump file. (Bug #17477959)
- On Windows, calling mysql_thread_init() call without mysql_init() caused the client to exit. windows. Now it returns a nonzero result because it is an error to call mysql_thread_init() before the client library is initialized with mysql_library_init(). (Bug #17514920)
- The optimizer trace could cause a server exit in cases where a subquery was transformed away. (Bug #17458054)
- The Debug Sync facility could lose a signal, leading to a spurious ER_DEBUG_SYNC_TIMEOUT error. (Bug #14765080, Bug #18221750)
- Compilation problems were fixed for errors reported by Clang and gcc when compiling in C++11 mode. (Bug #66803, Bug #14631159)
- CMake produced not-useful warnings about INTERFACE_LINK_LIBRARIES policy. (Bug #71089, Bug #17905155, Bug #17894997)
- LOAD DATA LOCAL INFILE could use all CPU if import errors occurred when there were no line delimiters. (Bug #51840, Bug #11759519)
On Windows, REPAIR TABLE and OPTIMIZE TABLE failed for MyISAM tables with .MYD files larger than 4GB. (Bug #69683, Bug #17235179)
- A statement of the following form broke row-based replication because it created a table having a field of data type BIGINT with a display width of 3000, which is beyond the maximum acceptable value of 255: CREATE TABLE t1 AS SELECT REPEAT('A',1000) DIV 1 AS a; (Bug #71179, Bug #17994219)
- Updates could fail to update all applicable rows in cases where multiple key values were identical except for trailing spaces. (Bug #69684, Bug #17156940)

MySQL 5.6.19 (64-bit) 相關參考資料
Download MySQL Community Server (Archived Versions)

5.6.19, 5.6.17, 5.6.16, 5.6.15, 5.6.14, 5.6.13, 5.6.12 ... Linux - Generic (glibc 2.28) (x86, 64-bit), Compressed TAR Archive ... Linux - Generic (glibc 2.28) (ARM, ...

https://downloads.mysql.com

Download MySQL Installer (Archived Versions)

5.6.19, 5.6.17, 5.6.16, 5.6.15, 5.6.14, 5.6.13, 5.6.12 ... Windows (x86, 32-bit). Windows (x86, 32-bit), MSI ... Windows (x86, 32-bit), MSI Installer, Jan 2, 2024 ...

https://downloads.mysql.com

Index of MySQLDownloadsMySQL-5.6

Index of /MySQL/Downloads/MySQL-5.6/ ../ MySQL-5.6.49-1.el6.i686.rpm-bundle.tar 03-Jun-2020 05:40 231413760 MySQL ... 64bit.pkg.gz 02-Jun-2020 04:42 690009145 ...

http://ftp.ntu.edu.tw

Index of pubMySQLDownloadsMySQL-5.6

Index of /pub/MySQL/Downloads/MySQL-5.6/ ../ MySQL-5.6.49-1.el6.i686.rpm-bundle ... 64bit.pkg.gz.asc 03-Jun-2020 09:20 173 mysql-5.6.49-solaris10-sparc-64bit ...

http://ftp.ntu.edu.tw

mysql 5.6.19 win32_mysql-5.6.19-win32 安装配置原创

2021年1月27日 — Windows64位MySql 5.6.19 · Windows 64 Bit MySql V5.6.19,安装后需要自行设置密码 · mysql5.19和非常详细的安装教程 · 刚开始使用mysql的时候不得要领, ...

https://blog.csdn.net

MySQL :: Download MySQL Community Server (Archived ...

5.6.19, 5.6.17, 5.6.16, 5.6.15, 5.6.14, 5.6.13, 5.6.12 ... Linux - Generic (glibc 2.5) (x86, 32-bit), Linux ... Linux - Generic (glibc 2.5) (x86, 64-bit), RPM ...

https://downloads.mysql.com

mysql-5.6.19-winx64安装教程原创

2018年3月27日 — mysql-5.6.19-winx64安装教程 原创 · 1.先找到mysql bin目录下的my.ini文件,在[mysql]下面加上skip-grant-tables 用于跳过密码 · 2.重启服务器 · 3.进入cmd ...

https://blog.csdn.net

MySQL-5.6.19免安装版(zip版)安装配置教程

2015年11月1日 — MySQL Installer 5.6 for Windows 这是一个.msi可执行安装文件. Windows (x86, 64-bit), ZIP Archive 64位免安装zip格式文件,适用64位操作系统.

https://www.cnblogs.com

mysql-MySQL-5.6安装包下载 - 阿里巴巴开源镜像站

mysql-MySQL-5.6安装包是阿里云官方提供的开源镜像免费下载服务,每天下载量过亿,阿里巴巴开源镜像站为包含mysql-MySQL-5.6安装包的几百个操作系统镜像和依赖包镜像 ...

https://mirrors.aliyun.com

遂先安装了Mysql 5.6.19 64bit 版本的数据库,结果 ...

2022年9月3日 — 数据库版本: Mysql 5.6.19 64 bit. 案例介绍:. 今天开始学习mysql,遂先安装了Mysql 5.6.19 64bit 版本的数据库,结果安装成功了,但是使用root登录时 ...

https://www.cnblogs.com