MySQL (64-bit)

最新版本 MySQL 5.6.35 (64-bit)

MySQL 5.6.35 (64-bit)

MySQL 5.6.35 (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


檔案版本 MySQL 5.6.35 (64-bit)

檔案名稱 mysql-5.6.35-winx64.msi
檔案大小 37.18 MB
系統 Windows XP64 / Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64
軟體類型 開源軟體
作者 Oracle
更新日期 2016-12-15

What's new in this version:

MySQL Enterprise Notes:
- Enterprise Encryption for MySQL Enterprise Edition now enables server administrators to impose limits on maximum key length by setting environment variables. These can be used to prevent clients from using excessive CPU resources by passing very long key lengths to key-generation operations. For more information, see Enterprise Encryption Usage and Examples

Security Notes:
Incompatible Change: These changes were made to mysqld_safe:
- Unsafe use of rm and chown in mysqld_safe could result in privilege escalation. chown now can be used only when the target directory is /var/log. An incompatible change is that if the directory for the Unix socket file is missing, it is no longer created; instead, an error occurs. Due to these changes, /bin/bash is required to run mysqld_safe on Solaris. /bin/sh is still used on other Unix/Linux platforms
- The --ledir option now is accepted only on the command line, not in option files
- mysqld_safe ignores the current working directory

Other related changes:
- Initialization scripts that invoke mysqld_safe pass --basedir explicitly
- Initialization scripts create the error log file only if the base directory is /var/log or /var/lib
- Unused systemd files for SLES were removed
- MySQL Server now includes a plugin library that enables administrators to introduce an increasing delay in server response to clients after a certain number of consecutive failed connection attempts. This capability provides a deterrent that slows down brute force attacks that attempt to access MySQL user accounts. For more information, see The Connection-Control Plugin
- OpenSSL is ending support for version 1.0.1 in December 2016; Consequently, MySQL Commercial Server builds now use version 1.0.2 rather than version 1.0.1, and the linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1 to version 1.0.2j. For a description of issues fixed in this version, This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead

Functionality Added or Changed:
- InnoDB: By default, InnoDB reads uncommitted data when calculating statistics. In the case of an uncommitted transaction that deletes rows from a table, InnoDB excludes records that are delete-marked when calculating row estimates and index statistics, which can lead to non-optimal execution plans for other transactions that are operating on the table concurrently using a transaction isolation level other than READ UNCOMMITTED. To avoid this scenario, a new configuration option, innodb_stats_include_delete_marked, can be enabled to ensure that InnoDB includes delete-marked records when calculating persistent optimizer statistics
- Unit testing now uses Google Mock 1.8

Bugs Fixed:
- Incompatible Change: A change made in MySQL 5.6.32 for handling of multibyte character sets by LOAD DATA was reverted due to the replication incompatibility
- InnoDB: The GCC mach_parse_compressed function should load one to five bytes depending on the value of the first byte. Due to a GCC bug, GCC 5 and 6 emit code to load four bytes before the first byte value is checked . A workaround prevents this behavior
- InnoDB: Due to a glibc bug, short-lived detached threads could exit before the caller had returned from pthread_create(), causing a server exit
- InnoDB: An error during a table-rebuilding operation on a table with only a generated clustered index (GEN_CLUST_INDEX) raised and assertion due to an error called with an invalid key name
- InnoDB: On a table without an explicitly defined primary key, InnoDB did not replace the implicit clustered index (GEN_CLUST_INDEX) when a unique key was defined on a NOT NULL column
- InnoDB: InnoDB failed to free memory used by the full-text optimizer thread
- InnoDB: SHOW ENGINE INNODB STATUS output showed a “cleaning up” state for an idle thread. Thread state information was not reset after statement execution
- InnoDB: After a server restart, concurrent INSERT operations a table with an auto-increment primary key resulted in a duplicate entry error. The current auto-increment value was not changed after auto_increment_increment and auto_increment_offset settings were modified
- Replication: Tables with special DEFAULT columns, such as DEFAULT CURRENT_TIMESTAMP, that existed only on a slave were not being updated when using row-based replication (binlog_format=ROW)
- Replication: Enabling semisynchronous replication when a server was during the commit stage could cause the master to stop unexpectedly
- Replication: The fix for Bug #81657 was correctly merged into MySQL 5.6
- Some Linux startup scripts did not process the datadir setting correctly
- CREATE TABLE with a DATA DIRECTORY clause could be used to gain extra privileges
- OEL RPM packages now better detect which platforms have multilib support (for which 32-bit and 64-bit libraries can be installed). Thanks to Alexey Kopytov for the patch
- Compiling MySQL using Microsoft Visual Studio 2015 Version 14.0.25420.1 in relwithdebinfo mode failed with linking errors
- Warnings occurring during CREATE TABLE ... SELECT could cause a server exit
- For segmentation faults on FreeBSD, the server did not generate a stack trace
- The .mylogin.cnf option file is intended for use by client programs, but the server was reading it as well. The server no longer reads it
- If mysqladmin shutdown encountered an error determining the server process ID file, it displayed an error message that did not clearly indicate the error was nonfatal. It now indicates that execution continues
- The data structure used for ZEROFILL columns could experience memory corruption, leading eventually to a server exit
- Use of very long subpartition names could result in a server exit. Now partition or subpartition names larger than 64 characters produce an ER_TOO_LONG_IDENT error
- On Solaris, gettimeofday() could return an invalid value and cause a server shutdown
- A union query resulting in tuples larger than max_join_size could result in a server exit
- The optimizer could choose ref access on a secondary index rather than range access on the primary key, even when the cost was higher
- For some deeply nested expressions, the optimizer failed to detect stack overflow, resulting in a server exit
- When taking the server offline, a race condition within the Performance Schema could lead to a server exit
- The Performance Schema events_statements_summary_by_digest table could contain multiple rows for the same statement digest and schema combination, rather than the expected single (unique) row
- For debug builds: Adding a unique index to a POINT NOT NULL column triggered a warning and the key was not promoted to a primary key. Creating a unique index on a different non-NULL column in the same table then raised an assertion
- Compiling using Clang 3.5 or higher with AddressSanitizer (ASAN) enabled caused the gen_lex_hash utility to abort on Clang LeakSanitizer memory leak check failures
- Miscalculation of memory requirements for qsort operations could result in stack overflow errors in situations with a large number of concurrent server connections

MySQL 5.6.35 (64-bit) 相關參考資料
Download MySQL Community Server

MySQL Community Server 8.0.33 ; Linux - Generic (glibc 2.28) (x86, 64-bit), Compressed TAR Archive, 8.0.33, 514.9M ; (mysql-8.0.33-linux-glibc2.28-x86_64.tar.gz) ...

Download MySQL Community Server (Archived Versions)

Linux - Generic (glibc 2.12) (x86, 64-bit), Compressed TAR Archive, Dec 17, 2022, 582.0M ; (mysql-8.0.32-linux-glibc2.12-x86_64.tar.xz), MD5: ...

Downloading MySQL 5.6.35 (64-bit) from

The world`s most popular open-source relational database management system · MySQL 5.6.35 (64-bit) · Key details about this download.

Index of MySQLDownloadsMySQL-5.6

MySQL-5.6.49-1.el6.i686.rpm-bundle.tar 03-Jun-2020 05:40 231413760 ... 09:21 173 MySQL-5.6.49-1.el7.x86_64.rpm-bundle.tar.md5 03-Jun-2020 09:19 75 ...

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

(MySQL-5.6.23-1.linux_glibc2.5.x86_64.rpm-bundle.tar), MD5: 8e870bf6c20208deedbf44e600bf086c | ... Linux - Generic (glibc 2.5) (x86, 64-bit), RPM Package

MySQL Community Server

Linux - Generic (glibc 2.12) (x86, 64-bit), Compressed TAR Archive, Mar 15, 2019, 313.9M. Download. (mysql-5.6.44-linux-glibc2.12-x86_64.tar.gz) ...

MySQL Installer - (Archived Versions)

Windows (x86, 32-bit), MSI Installer, Jan 3, 2023, 2.4M · Download ; (mysql-installer-web-community-, MD5: 0f882590f8338adc614e9dc5cb00ca0b | ...