MySQL (64-bit)

最新版本 MySQL 5.6.29 (64-bit)

MySQL 5.6.29 (64-bit)

MySQL 5.6.29 (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.29 (64-bit)

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

What's new in this version:

Functionality Added or Changed:
- InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate temporary file directory for online ALTER TABLE operations. This option was introduced to help avoid tmpdir overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir is a SESSION variable and can be configured dynamically using a SET statement
- yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites
- The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11

Bugs Fixed:
- InnoDB: A small InnoDB buffer pool size with a large innodb_stats_persistent_sample_pages setting resulted in a Difficult to find free blocks in the buffer pool warning
- InnoDB: Starting the server with an empty innodb_data_home_dir entry in the configuration file caused InnoDB to look for the buffer pool file in the root directory, resulting in a startup error
- InnoDB: A full-text query run under high concurrency caused a server exit due to an invalid memory access
- InnoDB: With a large innodb_sort_buffer_size setting, adding an index on an empty table performed more slowly than expected
- Replication: When DML invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column, that DML has to be marked as an unsafe statement. If the tables are locked in the transaction prior to the DML statement (for example by using LOCK TABLES), then the DML statement was not being marked as an unsafe statement. The fix ensures that such DML statements are marked correctly as unsafe
- Replication: As part of the fix for Bug #16290902, when writing a DROP TEMPORARY TABLE IF EXISTS query into the binary log, the query is no longer preceded by a USE `db` statement. Instead the query uses a fully qualified table name, for example DROP TEMPORARY TABLE IF EXISTS `db`.`t1`;. This changed the application of replicate-rewrite-db filter rules, as they work only on the default database specified in a USE statement. This caused slaves to fail when the resulting CREATE TEMPORARY TABLE was applied. The fix ensures that at the time of writing a DROP TEMPORARY TABLE IF EXISTS query into the binary log, a check is made for the default database. If it exists then the query is written as USE default_db in the binary log. If a default database is not present then the query is logged with the qualified table name
- Replication: If generating a GTID for a transaction fails, the transaction is not written to the binary log but still gets committed. Although running out of GTIDs is a rare situation, if it did occur an error was written to the binary log as a sync stage error. With binlog_error_action=ABORT_SERVER, the server aborts on such an error, avoiding data inconsistency. When binlog_error_action=IGNORE_ERROR, the server continues binary logging after such an error, potentially leading to data inconsistency between the master and the slave. The fix changes the error to be correctly logged as a flush stage error
- Replication: When using --gtid-mode=on , --enforce-gtid-consistency , and --binlog-format=row, if a user defined function with multiple DROP TEMPORARY TABLE statements was executed on a master, the resulting binary log caused an error on slaves. The fix ensures that stored functions and triggers are also considered multi-statement transactions, and that when --enforce-gtid-consistency is enabled, functions with CREATE TEMPORARY TABLE or DROP TEMPORARY TABLE statements generate an ER_GTID_UNSAFE_CREATE_DROP_TEMPORARY_TABLE_IN_TRANSACTION error
- Replication: Stored procedure local variables that were used in an ALTER EVENT statement were not being replicated correctly. This was related to the fact that CALL statements are not written into the binary log. Instead each statement executed in a stored procedure is binary logged separately, with the exception that the query string is modified so that uses of stored procedure local variables are replaced with NAME_CONST('spvar_name', 'spvar-value') calls. DDL statements (which are always binary logged in statement binary log mode irrespective of the current binary log format) can also use stored procedure local variables and a clash could cause them to not be replicated correctly. The fix ensures that any stored procedure local variables used in a query are replaced with NAME_CONST(...), except for the case when it is a DML query and the binary log format is ROW
- Replication: DROP TABLE statements are regenerated by the server before being written to the binary log. If a table or database name contained a non-regular character, such as non-latin characters, the regenerated statement was using the wrong name, breaking replication. The fix ensures that in such a case the regenerated name is correctly converted back to the original character set. Also during work on this bug, it was discovered that in the rare case that a table or database name contained 64 characters, the server was throwing an assert(M_TBLLEN < 128) assertion. The assertion has been corrected to be less than or equal 128
- Replication: Irrespective of the current binlog_format setting, DDL that changes metadata on a master is always identified and written to the binary log in STATEMENT format. Such DDL could occur from event based SQL statements, such as CREATE EVENT or DROP EVENT, or transactions that had unsafe functions such as sysdate(). When binlog_format=MIXED and attempting to replicate such DDL, it was not being correctly identified and therefore was not being correctly replicated
- Inserting a token of 84 4-byte characters into a full-text index raised an assertion. The maximum token length was 84 characters up to a maximum of 252 bytes, which did not account for 4-byte characters. The maximum byte length is now 336 bytes
- If a client attempted to use an unsupported client character set (ucs2, utf16, utf32), the error message reported to the client differed for SSL and non-SSL connections
- Data corruption or a server exit could occur if a stored procedure had a variable declared as TEXT or BLOB and data was copied to that variable using SELECT ... INTO syntax from a TEXT or BLOB column
- CREATE TEMPORARY TABLE .. SELECT statements involving BIT columns that resulted in a column type redefinition could cause a server exit or an improperly created table
- Added Microsoft Visual Studio 2015 support. Changes include using the native (added in VS 2015) timespec library if it exists, renamed lfind/lsearch and timezone/tzname to avoid redefinition problems, set TMPDIR to "" by default as P_tmpdir no longer exists, deprecated std::hash_map in favor of std::unordered_map, and added Wix Toolset 3.10 support
- With character_set_server=utf16le, some values of ft_boolean_syntax could cause a server exit for full-text searches
- With LOCK TABLES in force, an attempt to open a temporary MERGE table consisting of a view in its list of tables (not the last table in the list) caused a server exit
- For certain prepared statements, the optimizer could transform join conditions such that it used a pointer to a temporary table field that was no longer available after the initial execution. Subsequent executions caused a server exit
- Repeated execution of ALTER TABLE v1 CHECK PARTITION as a prepared statement, where v1 is a view, led to a server exit
- In addition, output for some administrative operations, when they are attempted on a view, changes from “Corrupt” to “Operation failed”. These include ANALYZE TABLE, OPTIMIZE TABLE, and REPAIR TABLE, and ALTER TABLE statements that perform ANALYZE PARTITION, CHECK PARTITION, OPTIMIZE PARTITION, and REPAIR PARTITION operations
- Valgrind detected some possibly unsafe use of string functions in code used for asymmetric encryption
- SSL connections ignored any change made by passing the MYSQL_OPT_READ_TIMEOUT option to the mysql_options() C API function
- Solaris packages failed to note the dependency of the MySQL client library on the libstlport library
- Using systemd to start mysqld failed if configuration files contained multiple datadir lines. Now the last datadir line is used
- If server was started with --thread-handling=no-threads, no foreground thread was created for a client connection. The Performance Schema did not account for the possibility of no foreground threads for queries on the session_connect_attrs table, causing an assertion to be raised
- ALTER TABLE ... CONVERT TO CHARACTER SET operations that used the INPLACE algorithm were ineffective if the table contained only numeric data types. Also, such operations failed to clean up their temporary .frm file
- Heavy SHOW PROCESSLIST or SELECT ... FROM INFORMATION_SCHEMA.PROCESSLIST activity could result in the server accepting more than max_connections connections
- When used with the libmysqld embedded server, the mysql_stmt_execute() C API function failed with a malformed communication packet error, even for simple prepared statements

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

5.6.29, 5.6.28, 5.6.27, 5.6.26, 5.6.25, 5.6.24, 5.6.23 ... 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)

Windows (x86, 32-bit), MSI Installer, Jan 2, 2024, 2.1M · Download ; (mysql-installer-web-community-8.0.36.0.msi), MD5: 81061532541f716cf6c6e2c4881a154c | ...

https://downloads.mysql.com

Downloading MySQL 5.6.29 (64-bit) from FileHorse.com

MySQL is an open-source, community-driven RDBMS that provides a robust and scalable platform for storing, managing, and retrieving data.

https://www.filehorse.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.29 (64-bit) Download

2016年2月8日 — Download MySQL 5.6.29 (64-bit) for Windows PC from FileHorse. 100% Safe and Secure ✓ Free Download 64-bit Software Version.

https://www.filehorse.com

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

5.6.29, 5.6.28, 5.6.27, 5.6.26, 5.6.25, 5.6.24, 5.6.23 ... Linux - Generic (glibc 2.5) (x86, 32-bit), Linux ... Linux - Generic (glibc 2.5) (x86, 64-bit), RPM ...

https://downloads.mysql.com

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

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

https://mirrors.aliyun.com

mysql5.6.29 64位下载_免安装版mysql-5.6.29-winx64 下载

2021年1月19日 — mysql5.6.29 64位下载_免安装版mysql-5.6.29-winx64 下载,配置 原创 ... 1.去官网下载mysql-5.6.29-winx64.zip. 2.解压到你想安装的的目录,我的是E:-db- ...

https://blog.csdn.net

免安装版mysql-5.6.29-winx64 下载,配置

2021年1月19日 — mysql 5.6.29 下载_免安装版mysql-5.6.29-winx64 下载,配置 原创 · 1.去官网下载mysql-5.6.29-winx64.zip. · 2.解压到你想安装的的目录,我的是E:-db-mysql ...

https://blog.csdn.net