{"id":3000,"date":"2019-12-19T01:00:43","date_gmt":"2019-12-19T01:00:43","guid":{"rendered":"https:\/\/www.canspace.ca\/blog\/?p=3000"},"modified":"2020-01-15T23:34:34","modified_gmt":"2020-01-16T04:34:34","slug":"whats-new-in-mysql-8-0","status":"publish","type":"post","link":"https:\/\/www.canspace.ca\/blog\/hosting-servers\/whats-new-in-mysql-8-0\/","title":{"rendered":"What’s new in MySQL 8.0?"},"content":{"rendered":"

If you\u2019re a database administrator, the recently released MySQL 8.0 is probably the most exciting event of the year. The new version offers some significant benefits to the previous version (5.7).<\/p>\n

At CanSpace, we will support MySQL 8.0 as soon as it is officially supported by cPanel, which should be within a few months.<\/p>\n

Here are some of the features you can look forward to in MySQL 8.0:<\/p>\n

\"\"<\/a><\/p>\n

Data dictionary<\/h2>\n

MySQL now incorporates a transactional data dictionary that stores information about database objects. In previous MySQL releases, dictionary data was stored in metadata files and nontransactional tables. For more information, see Chapter 14, MySQL Data Dictionary<\/a>.<\/p>\n

Resource management<\/h2>\n

MySQL now supports creation and management of resource groups, and permits assigning threads running within the server to particular groups so that threads execute according to the resources available to the group.<\/p>\n

Group attributes enable control over its resources, to enable or restrict resource consumption by threads in the group. DBAs can modify these attributes as appropriate for different workloads. Currently, CPU time is a manageable resource, represented by the concept of \u201cvirtual CPU\u201d as a term that includes CPU cores, hyperthreads, hardware threads, and so forth. The server determines at startup how many virtual CPUs are available, and database administrators with appropriate privileges can associate these CPUs with resource groups and assign threads to groups. For more information, see Section 8.12.5, \u201cResource Groups\u201d<\/a>.<\/p>\n

Table encryption management<\/h2>\n

Table encryption can now be managed globally by defining and enforcing encryption defaults. The default_table_encryption<\/a> variable defines an encryption default for newly created schemas and general tablespace. The encryption default for a schema can also be defined using the DEFAULT ENCRYPTION clause when creating a schema. By default, a table inherits the encryption of the schema or general tablespace it is created in. Encryption defaults are enforced by enabling the table_encryption_privilege_check<\/a> variable. The privilege check occurs when creating or altering a schema or general tablespace with an encryption setting that differs from the default_table_encryption<\/a> setting, or when creating or altering a table with an encryption setting that differs from the default schema encryption. The TABLE_ENCRYPTION_ADMIN<\/a> privilege permits overriding default encryption settings when table_encryption_privilege_check<\/a> is enabled. For more information, see Defining an Encryption Default for Schemas and General Tablespaces<\/a>.<\/p>\n

Security and account management<\/h2>\n

These enhancements were added to improve security and enable greater DBA flexibility in account management:<\/p>\n