MySQL (64-bit)

最新版本 MySQL 5.7.32 (64-bit)

MySQL 5.7.32 (64-bit)

MySQL 5.7.32 (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.7.32 (64-bit)

檔案名稱 mysql-installer-community-5.7.32.0.msi
檔案大小
系統 Windows XP64 / Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64
軟體類型 開源軟體
作者 Oracle
官網 http://www.mysql.com/
更新日期 2020-10-19
更新日誌

What's new in this version:

Added or Changed:
- LOCK TABLES privilege checking for views was improved

Bugs Fixed:
- InnoDB: A query that updated the clustered index of an internal temporary table returned an incorrect result. The modified pages of the clustered index were not added to the flush list resulting in lost changes when the modified pages were evicted from the buffer pool
- InnoDB: An ALTER TABLE ... IMPORT TABLESPACE operation on a large encrypted and compressed table failed with a Page decompress failed after reading from disk error. The decryption operation did not use the encryption block size used during encryption. Also, the encryption process did not consider compressed length, while the decryption process decrypts data by compressed length only
- InnoDB: A failure occurred during a concurrent update operation. The failure was due to an invalid previous record value
- InnoDB: The function used to process the SHOW ENGINE INNODB MUTEX statement was insufficiently isolated from other threads adding new mutexes concurrently
- InnoDB: The buffer control block structure (buf_block_t) was freed while reducing the size of the buffer pool, causing an assertion failure. The fix for this bug also backports important aspects of the fix for Bug #20735882 / Bug #76343, and replaces the internal buf_block_is_uncompressed() function with the buf_pointer_is_block_field_instance() function. The buf_block_is_uncompressed() function returned false in too many cases, affecting OLTP query throughput
- InnoDB: In session started with START TRANSACTION WITH CONSISTENT SNAPSHOT, a range query returned a truncated result. The end range flag was not reset at the beginning of the index read resulting in an aborted read and missing rows.
- InnoDB: A full-text phrase search raised an assertion failure. Thanks to TXSQL (Tencent MySQL) for the contribution
- InnoDB: A long running statistics calculation operation on a large table blocked other operations requiring access to the table's statistics, causing those operations to fail. A new statistics calculation mutex was introduced, which permits concurrent access table statistics. Thanks to Kamil Holubicki for the contribution.
- InnoDB: Two connections attempted to use the same transaction handler object resulting in a stalled query
- Replication: When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect to replicas, the first time that the source uses a given MEMORY table after startup, it logs an event that notifies replicas that the table must be emptied by writing a statement to the binary log to that effect. Previously, this was a DELETE statement, but it is now a TRUNCATE TABLE statement. A replica server also writes this statement to its own binary log when it shuts down and restarts. The statement is always logged in statement format, even if the binary logging format is set to ROW, and it is written even if read_only or super_read_only mode is set on the server.
- Replication: When the system variable session_track_gtids was set to OWN_GTID on a multithreaded replica, the replica’s performance would degrade over time and begin to lag behind the master. The cause was the buildup of the GTIDs recorded by the replica’s worker threads at each transaction commit, which increased the time taken by the worker threads to insert new ones. Session state tracking is now disabled for worker threads on a multithreaded replica. Thanks to Facebook for the contribution.
- Certain cases of successful LDAP authentication could cause the server to hang
- In bootstrapping mode, certain multiple-statement transactions could cause unexpected server behavior
- Sensitive LDAP authentication plugin system variables now display as asterisks when retrieved in SQL statements
- After the fix for Bug #81009, privilege checks for truncating Performance Schema tables were too restrictive when read_only or super_read_only were enabled, causing truncation to fail even for users with appropriate table privileges
- Some INSERT statements were not handled correctly
- Certain prepared statements could cause an unexpected server exit
- mysqlpump object validation included objects in excluded databases
- LDAP authentication plugins enforced CA verification incorrectly, which could result in use of an incorrect CA
- ORDER BY queries were not executed correctly when sort_buffer_size and max_sort_length were set to values which caused the internal limit on the maximum number of keys allowed per sort buffer to be set to 0.
- A large number of nested arguments in full-text search query caused an error
- When explicit_defaults_for_timestamp was disabled and a NULL was inserted into a generated column declared as TIMESTAMP NOT NULL, the server would attempt to convert the inserted value to CURRENT_TIMESTAMP. Such an insertion is now rejected with ER_BAD_NULL_ERROR.
- An assertion could be raised when the SQL layer passed incorrect information to InnoDB about the type of operation to be performed on a temporary table

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

(mysql-8.0.23-linux-glibc2.12-x86_64.tar.xz), MD5: b7228a20ab3f43d830f0f791cb52c229 ... Linux - Generic (glibc 2.12) (x86, 64-bit), Compressed TAR Archive

https://dev.mysql.com

MySQL 5.7 Reference Manual :: 2.3 Installing ... - MySQL

... installing the server. The package is available at the Microsoft Download Center. MySQL is available for Microsoft Windows, for both 32-bit and 64-bit versions.

https://dev.mysql.com

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

(mysql-8.0.22-linux-glibc2.12-i686.tar.xz), MD5: 5311d79f6b3e726d8364d9b418b870bb | Signature. Linux - Generic (glibc 2.12) (x86, 64-bit), Compressed TAR ...

https://downloads.mysql.com

MySQL :: Download MySQL Installer (Archived Versions)

(mysql-installer-web-community-8.0.22.0.msi), MD5: 6d4c2f4fe997f1e9e8a02b105e7f72c8 | Signature. Windows (x86, 32-bit), MSI Installer, Oct 12, 2020, 405.2 ...

https://downloads.mysql.com

MySQL Community Server 5.6.50 - MySQL :: Download ...

(mysql-5.6.50-linux-glibc2.12-i686.tar.gz), MD5: a59c40798c9c9d64f718d4cb18795b4d | Signature. Linux - Generic (glibc 2.12) (x86, 64-bit), Compressed TAR ...

https://dev.mysql.com

MySQL Community Server 5.7.32

Download. (mysql-community-source_5.7.32-1debian10_amd64.deb), MD5: ... Ubuntu Linux 18.04 (x86, 64-bit), DEB Package, 5.7.32, 50.6M. Download.

https://dev.mysql.com

MySQL Community Server 5.7.32 - MySQL :: Download ...

Download. (mysql-5.7.32.zip), MD5: a26340ee790364a7e086ace5f4128965 | Signature. Debian Linux 10 (x86, 64-bit), DEB Package, 5.7.32, 50.6M. Download. (mysql-community-source_5.7.32-1debian10_amd64.deb...

https://dev.mysql.com

MySQL Community Server 5.7.33 - MySQL :: Download ...

(mysql-5.7.33-linux-glibc2.12-i686.tar.gz), MD5: 7fe7c21df19896744edefd114e1e9078 | Signature. Linux - Generic (glibc 2.12) (x86, 64-bit), Compressed TAR ...

https://dev.mysql.com

MySQL Installer 5.7.33 - MySQL :: Developer Zone

Windows (x86, 32-bit), MSI Installer, 5.7.33, 2.4M. Download. (mysql-installer-web-community-5.7.33.0.msi), MD5: 4bf45b3da5a3c5e4560e5ba91b525035 | ...

https://dev.mysql.com

安裝MySQL Community Server ... - 德瑞克:SQL Server 學習筆記

2017年2月2日 — MySQL for Visual Studio; Documentation. 注意事項: 此MySQL Installer是32位元版本,但其內包含了32位元與64位元 ...

http://sharedderrick.blogspot.