SlideShare a Scribd company logo

preFOSDEM MySQL Day - Best Practices to Upgrade to MySQL 8.0

Frederic Descamps, profile picture
Frederic Descamps

The document provides instructions for upgrading from MySQL 5.5 to MySQL 8.0. It outlines two main upgrade methods - performing a logical dump and restore of the data, or doing an in-place upgrade. For a logical dump and restore, the steps are to dump the data, upgrade binaries, erase old data, restore data, and restart MySQL. For an in-place upgrade, the steps are to stop MySQL, upgrade binaries, run mysql_upgrade, and restart MySQL. It also provides checks to verify the upgrade and discusses SQL mode changes and compatibility issues to watch for.

Software
1 of 66
Downloaded 37 times
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
1 / 66
Frédéric Descamps Community Manager MySQL Best practices to upgrade to MySQL 8.0 MySQL 8 is Great ! 2 / 66
  Safe Harbor The following is intended to outline our general product direction. It is intended for information purpose only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied up in making purchasing decisions. The development, release, timing and pricing of any features or functionality described for Oracle´s product may change and remains at the sole discretion of Oracle Corporation. Statement in this presentation relating to Oracle´s future plans, expectations, beliefs, intentions and ptospects are "forward-looking statements" and are subject to material risks and uncertainties. A detailed discussion of these factors and other risks that a ect our business is contained in Oracle´s Securities and Exchange Commission (SEC) lings, including our most recent reports on Form 10-K and Form 10-Q under the heading "Risk Factors". These lings are available on the SEC´s website or on Oracle´s website at h p://www.oracle.com/investor. All information in this presentation is current as of September 2019 and Oracle undertakes no duty to update any statement in light of new information or future events. Copyright @ 2020 Oracle and/or its affiliates. 3 / 66
about.me/lefred Who am I ? Copyright @ 2020 Oracle and/or its affiliates. 4 / 66
Frédéric Descamps @lefred MySQL Evangelist Managing MySQL since 3.23 devops believer living in Belgium 🇧🇪 h ps://lefred.be Copyright @ 2020 Oracle and/or its affiliates. 5 / 66
Migrating to MySQL 8.0 Why ? Copyright @ 2020 Oracle and/or its affiliates. 6 / 66
DB-Engines 2019 Database Ranking Copyright @ 2020 Oracle and/or its affiliates. 7 / 66
DB-Engines 2019 Database Ranking MySQL is the 2nd most popular database Copyright @ 2020 Oracle and/or its affiliates. 8 / 66
DB-Engines 2019 Database Ranking MySQL is the 2nd most popular database MySQL is the most Open Source popular database Copyright @ 2020 Oracle and/or its affiliates. 9 / 66
MySQL is the DBMS of the Year 2019 ! Copyright @ 2020 Oracle and/or its affiliates. 10 / 66
MySQL Developer Popularity Stack Overflow Developer Survey 2019 Copyright @ 2020 Oracle and/or its affiliates. 11 / 66
MySQL is the most popular database with developers MySQL Developer Popularity Stack Overflow Developer Survey 2019 Copyright @ 2020 Oracle and/or its affiliates. 12 / 66
April 2018 (8.0 GA) August 2019 MySQL 8.0: fastest adoption !! Copyright @ 2020 Oracle and/or its affiliates. 13 / 66
"This is a landmark release as MySQL eventually evolved beyond SQL-92 and the purely relational dogma. Among a few other standard SQL features, MySQL now supports window functions (over) and common table expressions (with). Without a doubt, these are the two most important post-SQL-92 features.” MySQL 8.0: one giant leap for SQL Copyright @ 2020 Oracle and/or its affiliates. 14 / 66
and many more features ! Copyright @ 2020 Oracle and/or its affiliates. 15 / 66
I want to upgrade to MySQL 8.0 First Steps Copyright @ 2020 Oracle and/or its affiliates. 16 / 66
Some Mandatory Literature... DISCLAMER: No need to read the full manual each time MySQL releases a new version /cc @marcotusa Copyright @ 2020 Oracle and/or its affiliates. 17 / 66
Some Mandatory Literature... DISCLAMER: No need to read the full manual each time MySQL releases a new version /cc @marcotusa For any upgrade (minor and major), you need to rst read the release notes: h ps://dev.mysql.com/doc/relnotes/mysql/8.0/en/ Copyright @ 2020 Oracle and/or its affiliates. 18 / 66
Some Mandatory Literature... DISCLAMER: No need to read the full manual each time MySQL releases a new version /cc @marcotusa For any upgrade (minor and major), you need to rst read the release notes: h ps://dev.mysql.com/doc/relnotes/mysql/8.0/en/ Changes in MySQL 8: h ps://dev.mysql.com/doc/refman/8.0/en/upgrading-from- previous-series.html Copyright @ 2020 Oracle and/or its affiliates. 19 / 66
Some Mandatory Literature... DISCLAMER: No need to read the full manual each time MySQL releases a new version /cc @marcotusa For any upgrade (minor and major), you need to rst read the release notes: h ps://dev.mysql.com/doc/relnotes/mysql/8.0/en/ Changes in MySQL 8: h ps://dev.mysql.com/doc/refman/8.0/en/upgrading-from- previous-series.html Verify your con guration le for removed se ings: h ps://dev.mysql.com/doc/refman/8.0/en/added-deprecated-removed.html Copyright @ 2020 Oracle and/or its affiliates. 20 / 66
Is My Application Ready ? There are some points very important to verify before upgrading to MySQL 8.0: Copyright @ 2020 Oracle and/or its affiliates. 21 / 66
Is My Application Ready ? There are some points very important to verify before upgrading to MySQL 8.0: Is the driver recent enough and if not can it be upgraded ? Copyright @ 2020 Oracle and/or its affiliates. 22 / 66
Is My Application Ready ? There are some points very important to verify before upgrading to MySQL 8.0: Is the driver recent enough and if not can it be upgraded ? Is my application using a speci c SQL mode ? Copyright @ 2020 Oracle and/or its affiliates. 23 / 66
Is My Application Ready ? There are some points very important to verify before upgrading to MySQL 8.0: Is the driver recent enough and if not can it be upgraded ? Is my application using a speci c SQL mode ? Is my application using queries speci c to some SQL mode ? Copyright @ 2020 Oracle and/or its affiliates. 24 / 66
Is My Application Ready ? There are some points very important to verify before upgrading to MySQL 8.0: Is the driver recent enough and if not can it be upgraded ? Is my application using a speci c SQL mode ? Is my application using queries speci c to some SQL mode ? Does my replication relies somehow to Information_Schema or other system (mysql.*) tables ? Copyright @ 2020 Oracle and/or its affiliates. 25 / 66
Connector and Authentication the new default authentication plugin (caching_sha2_password) is more secure but not supported with old connectors. all the new connectors provided by MySQL are compatible. Copyright @ 2020 Oracle and/or its affiliates. 26 / 66
Connector and Authentication the new default authentication plugin (caching_sha2_password) is more secure but not supported with old connectors. all the new connectors provided by MySQL are compatible. if your connector doesn't support the new authentication plugin, you should force the use of the old native one by adding in my.cnf: default-authentication-plugin = mysql_native_password Copyright @ 2020 Oracle and/or its affiliates. 27 / 66
mysql> select user, plugin from mysql.user limit 2; +-------+-----------------------+ | user | plugin | +-------+-----------------------+ | books | mysql_native_password | | dev | caching_sha2_password | +-------+-----------------------+ 2 rows in set (0.00 sec) 8.0 Connector and Authentication (2) be sure the credentials used by your application use the right plugin: Copyright @ 2020 Oracle and/or its affiliates. 28 / 66
Example of PHP Support Copyright @ 2020 Oracle and/or its affiliates. 29 / 66
Example of PHP Support (2) Copyright @ 2020 Oracle and/or its affiliates. 30 / 66
Example of PHP Support (3) Copyright @ 2020 Oracle and/or its affiliates. 31 / 66
SQL Mode The SQL Mode default has been changed Version Default SQL Mode 5.6 NO_ENGINE_SUBSTITUTION 5.7 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_AUTO_CREATE_USER, NO_ENGINE_SUBSTITUTION 8.0 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_ENGINE_SUBSTITUTION Copyright @ 2020 Oracle and/or its affiliates. 32 / 66
SQL Mode The SQL Mode default has been changed Version Default SQL Mode 5.6 NO_ENGINE_SUBSTITUTION 5.7 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_AUTO_CREATE_USER, NO_ENGINE_SUBSTITUTION 8.0 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_ENGINE_SUBSTITUTION #1055 - Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'xxx' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by Copyright @ 2020 Oracle and/or its affiliates. 33 / 66
SQL Mode The SQL Mode default has been changed Version Default SQL Mode 5.6 NO_ENGINE_SUBSTITUTION 5.7 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_AUTO_CREATE_USER, NO_ENGINE_SUBSTITUTION 8.0 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_ENGINE_SUBSTITUTION #1055 - Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'xxx' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by And be aware that some have been removed and might cause error: frameworks had Error: PDOException::("SQLSTATE[42000]: Syntax error or access violation: 1231 Variable 'sql_mode' can't be set to the value of 'NO_AUTO_CREATE_USER'") Copyright @ 2020 Oracle and/or its affiliates. 34 / 66
Upgrade Checker Copyright @ 2020 Oracle and/or its affiliates. 35 / 66
Don't forget to use MySQL Shell Upgrade Checker Utility New tool in MySQL Shell Will check your MySQL 5.7 or 8.0 installation readiness for upgrade to latest version Check for legacy issues Run the tool on the 5.7 before upgrading! Always use latest version of MySQL Shell Copyright @ 2020 Oracle and/or its affiliates. 36 / 66
Don't forget to use MySQL Shell Upgrade Checker Utility New tool in MySQL Shell Will check your MySQL 5.7 or 8.0 installation readiness for upgrade to latest version Check for legacy issues Run the tool on the 5.7 before upgrading! Always use latest version of MySQL Shell Util.checkForServerUpgrade: Detected MySQL server version is 5.5.62, but this tool requires server to be at least at version 5.7 (LogicError) Copyright @ 2020 Oracle and/or its affiliates. 37 / 66
usage of old temporal type usage of new reserved keywords usage of udt8mb3 charset con icting name in mysql schema partitions with engine not supporting native partitioning foreign key constraint names longer than 64 characters usage of obsolete MAXDB SQL mode ag usage of orther obsolete SQL mode ags ENUM/SET column de nitions containing elements longer than 255 characters usage of partitioned tables in shared tablespaces MySQL Shell Upgrade Checker Utility Upgrade Checker performs the following checks: Copyright @ 2020 Oracle and/or its affiliates. 38 / 66
circular directory references in tablespace data le paths usage of removed functions usage of removed GROUP BY ASC/DESC syntax removed system variables for error logging to the system log con guration removed system variables system variables with new default values schema inconsistencies resulting from le removal or corruption table names containing 'FTS' issues reported by 'check table x for upgrade' command MySQL Shell Upgrade Checker Utility (2) Copyright @ 2020 Oracle and/or its affiliates. 39 / 66
MySQL Upgrade Checker: how to use it? From the system shell: $ mysqlsh -- util checkForServerUpgrade user@localhost:3306 --target-version=8.0.19 --output-format=JSON --con g-path=/etc/mysql/my.cnf From the New MySQL Shell: mysqlsh> util.checkForServerUpgrade('user@example.com:3306', {"password":"password", "targetVersion":"8.0.19", "con gPath":"/etc/my.cnf"}) mysqlsh> util.checkForServerUpgrade() Copyright @ 2020 Oracle and/or its affiliates. 40 / 66
I want to upgrade to MySQL 8.0 Let's do it ! Copyright @ 2020 Oracle and/or its affiliates. 41 / 66
From MySQL 5.5 to MySQL 8.0 To migrate to a newer version we have 2 options: logical dump & restore in-place upgrade Copyright @ 2020 Oracle and/or its affiliates. 42 / 66
Logical Dump & Restore This is the easiest option if you don't have too much data or if you can a ord a long dump and import time: dump the data: $ mysqldump -A > dump.sql stop the MySQL Service: $ sudo systemctl stop mysqld upgrade the binaries: $ sudo yum upgrade mysql-community* Copyright @ 2020 Oracle and/or its affiliates. 43 / 66
Logical Dump & Restore (2) erase the content of the data directory: $ sudo rm -f /var/lib/mysql/* if you plan to load the system tables (like in this example), please change in my.cnf: default-authentication-plugin = mysql_native_password start the MySQL Service (that will initialize the service): $ sudo systemctl start mysqld A new password has been generated, you can nd it in the error log. You need to change it, it's a good time to use a new password for root ;-) Copyright @ 2020 Oracle and/or its affiliates. 44 / 66
Logical Dump & Restore (3) restore the data: $ mysql -u root -p < dump.sql as we restored system tables too, it's be er to restart mysqld and force and upgrade: $ sudo systemctl set-environment MYSQLD_OPTS="--upgrade=FORCE" $ sudo systemctl restart mysqld $ sudo systemctl unset-environment MYSQLD_OPTS Copyright @ 2020 Oracle and/or its affiliates. 45 / 66
Logical Dump & Restore (3) restore the data: $ mysql -u root -p < dump.sql as we restored system tables too, it's be er to restart mysqld and force and upgrade: $ sudo systemctl set-environment MYSQLD_OPTS="--upgrade=FORCE" $ sudo systemctl restart mysqld $ sudo systemctl unset-environment MYSQLD_OPTS mysql> s -------------- mysql Ver 8.0.19 for Linux on x86_64 (MySQL Community Server - GPL) Copyright @ 2020 Oracle and/or its affiliates. 46 / 66
In-place Upgrade When you have a lot of data and that you consider that a single-thread logical dump and restore is not an option: 5.5 to 5.6 edit my.cnf and add for the full upgrade process: innodb_fast_shutdown = 0 stop the MySQL Service: $ sudo systemctl stop mysqld upgrade the binaries to 5.6: $ sudo yum upgrade mysql-community-* --disablerepo=mysql* --enablerepo=mysql56-community Copyright @ 2020 Oracle and/or its affiliates. 47 / 66
In-place Upgrade (2) start the MySQL Service: $ sudo systemctl start mysqld 2020-01-27 21:46:42 21955 [ERROR] Column count of mysql.threads is wrong. Expected 14, found 3. Created with MySQL 50562, now running 50647. Please use mysql_upgrade to x this error. as the error log recommends it, we must also run mysql_upgrade: $ sudo mysql_upgrade and don't forget to restart again MySQL: $ sudo systemctl restart mysqld Copyright @ 2020 Oracle and/or its affiliates. 48 / 66
In-place Upgrade (3) We can perform some checks on InnoDB Formats: mysql> SELECT FILE_FORMAT, ROW_FORMAT, count(*) Tot FROM INFORMATION_SCHEMA.INNODB_SYS_TABLES GROUP BY FILE_FORMAT, ROW_FORMAT; +-------------+------------+-----+ | FILE_FORMAT | ROW_FORMAT | Tot | +-------------+------------+-----+ | Antelope | Compact | 15 | | Antelope | Redundant | 4 | +-------------+------------+-----+ Let's check if we have old temporal columns: Copyright @ 2020 Oracle and/or its affiliates. 49 / 66
In-place Upgrade (4) mysql> SELECT t.TABLE_SCHEMA,t.ENGINE,t.TABLE_NAME,c.COLUMN_NAME,c.COLUMN_TYPE FROM INFORMATION_SCHEMA.TABLES t INNER JOIN INFORMATION_SCHEMA.COLUMNS c ON c.TABLE_SCHEMA = t.TABLE_SCHEMA AND c.TABLE_NAME = t.TABLE_NAME LEFT OUTER JOIN INFORMATION_SCHEMA.INNODB_SYS_TABLES ist ON ist.NAME = CONCAT(t.TABLE_SCHEMA,'/',t.TABLE_NAME) LEFT OUTER JOIN INFORMATION_SCHEMA.INNODB_SYS_COLUMNS isc ON isc.TABLE_ID = ist.TABLE_ID AND isc.NAME = c.COLUMN_NAME WHERE c.COLUMN_TYPE IN ('time', 'timestamp', 'datetime') AND t.TABLE_SCHEMA NOT IN ('mysql', 'information_schema', 'performance_schema') AND t.TABLE_TYPE = 'base table' AND (t.ENGINE != 'innodb' OR (t.ENGINE = 'innodb' AND isc.MTYPE = 6)) ORDER BY t.TABLE_SCHEMA, t.TABLE_NAME, c.COLUMN_NAME; +--------------+--------+-------------+---------------+-------------+ | TABLE_SCHEMA | ENGINE | TABLE_NAME | COLUMN_NAME | COLUMN_TYPE | +--------------+--------+-------------+---------------+-------------+ | sbtest_tpcc | InnoDB | customer1 | c_since | datetime | | sbtest_tpcc | InnoDB | history1 | h_date | datetime | | sbtest_tpcc | InnoDB | orders1 | o_entry_d | datetime | | sbtest_tpcc | InnoDB | orders2 | o_entry_d | datetime | | sbtest_tpcc | InnoDB | order_line1 | ol_delivery_d | datetime | +--------------+--------+-------------+---------------+-------------+ Copyright @ 2020 Oracle and/or its affiliates. 50 / 66
In-place Upgrade (5) 5.6 to 5.7 stop the MySQL Service: $ sudo systemctl stop mysqld upgrade the binaries to 5.7: $ sudo yum upgrade mysql-community-* --disablerepo=mysql* --enablerepo=mysql57-community start the MySQL Service: $ sudo systemctl start mysqld Copyright @ 2020 Oracle and/or its affiliates. 51 / 66
In-place Upgrade (6) we run mysql_upgrade: $ sudo mysql_upgrade We can see that the process also repairs some tables (with the previous old time format): Checking databases. sbtest_tpcc.customer1 error : Table rebuild required. Please do "ALTER TABLE `customer1` FORCE" or dump/reload to x it! ... Repairing tables `sbtest_tpcc`.`customer1` Running : ALTER TABLE `sbtest_tpcc`.`customer1` FORCE status : OK ... Upgrade process completed successfully. Copyright @ 2020 Oracle and/or its affiliates. 52 / 66
In-place Upgrade (7) and don't forget to restart again MySQL: $ sudo systemctl restart mysqld let's verify mysql> SELECT FILE_FORMAT, ROW_FORMAT, count(*) Tot FROM INFORMATION_SCHEMA.INNODB_SYS_TABLES GROUP BY FILE_FORMAT, ROW_FORMAT; +-------------+------------+-----+ | FILE_FORMAT | ROW_FORMAT | Tot | +-------------+------------+-----+ | Antelope | Compact | 5 | | Antelope | Redundant | 5 | | Barracuda | Dynamic | 25 | +-------------+------------+-----+ Copyright @ 2020 Oracle and/or its affiliates. 53 / 66
In-place Upgrade (8) 5.7 to 8.0 now we can use MySQL Upgrade Checker: $ mysqlsh -- util checkForServerUpgrade root@localhost --con g-path=/etc/my.cnf The MySQL server at localhost, version 5.7.29 - MySQL Community Server (GPL), will now be checked for compatibility issues for upgrade to MySQL 8.0.19... ... Errors: 0 Warnings: 28 Notices: 0 No fatal errors were found that would prevent an upgrade, but some potential issues were detected. Please ensure that the reported issues are not signi cant before upgrading. Copyright @ 2020 Oracle and/or its affiliates. 54 / 66
MySQL Upgrade Checker : details 16) System variables with new default values Warning: Following system variables that are not de ned in your con guration le will have new default values. Please review if you rely on their current values and if so de ne them before performing upgrade. More information: https://mysqlserverteam.com/new-defaults-in-mysql-8-0/ back_log - default value will change character_set_server - default value will change from latin1 to utf8mb4 collation_server - default value will change from latin1_swedish_ci to utf8mb4_0900_ai_ci event_scheduler - default value will change from OFF to ON explicit_defaults_for_timestamp - default value will change from OFF to ON innodb_autoinc_lock_mode - default value will change from 1 (consecutive) to 2 (interleaved) innodb_ ush_method - default value will change from NULL to fsync (Unix), unbuffered (Windows) innodb_ ush_neighbors - default value will change from 1 (enable) to 0 (disable) innodb_max_dirty_pages_pct - default value will change from 75 (%) 90 (%) innodb_max_dirty_pages_pct_lwm - default value will change from_0 (%) to 10 (%) innodb_undo_log_truncate - default value will change from OFF to ON ... Copyright @ 2020 Oracle and/or its affiliates. 55 / 66
MySQL Upgrade Checker : details (2) 17) Zero Date, Datetime, and Timestamp values Warning: By default zero date/datetime/timestamp values are no longer allowed in MySQL, as of 5.7.8 NO_ZERO_IN_DATE and NO_ZERO_DATE are included in SQL_MODE by default. These modes should be used with strict mode as they will be merged with strict mode in a future release. If you do not include these modes in your SQL_MODE setting, you are able to insert date/datetime/timestamp values that contain zeros. It is strongly advised to replace zero values with valid ones, as they may not work correctly in the future. More information: https://lefred.be/content/mysql-8-0-and-wrong-dates/ sbtest_tpcc.orders2.o_entry_d - column has zero default value: 0000-00-00 00:00:00 Copyright @ 2020 Oracle and/or its affiliates. 56 / 66
Let's go to 🎱 ! stop the MySQL Service: $ sudo systemctl stop mysqld upgrade the binaries to 8.0: $ sudo yum upgrade mysql-community-* --disablerepo=mysql* --enablerepo=mysql80-community start the MySQL Service: $ sudo systemctl start mysqld Jan 27 22:55:13 mysql2 mysqld[23209]: 2020-01-27T22:55:13.783334Z 2 [System] [MY-011003] [Server] Finished populating Data Dictionary tables with data. Jan 27 22:55:14 mysql2 mysqld[23209]: 2020-01-27T22:55:14.432342Z 5 [System] [MY-013381] [Server] Server upgrade from '50700' to '80019' started. Jan 27 22:55:23 mysql2 mysqld[23209]: 2020-01-27T22:55:23.439943Z 5 [System] [MY-013381] [Server] Server upgrade from '50700' to '80019' completed. Copyright @ 2020 Oracle and/or its affiliates. 57 / 66
Woooohoooo o/ Copyright @ 2020 Oracle and/or its affiliates. 58 / 66
MySQL 8.0 is Great ! Copyright @ 2020 Oracle and/or its affiliates. 59 / 66
Post Checks MySQL Upgrade Checker warned us about the invalid default date, but it doesn't scan the data. It's possible to write some queries to verify this... or use a plugin for the MySQL Shell: Copyright @ 2020 Oracle and/or its affiliates. 60 / 66
Post Checks (2) Let's verify the authentication methods used on our system: Copyright @ 2020 Oracle and/or its affiliates. 61 / 66
Post Checks (3) Comparing Results from previous version is not a straight forward task, and even if you can rely on PFS tables, you cannot link the results between version relying on the digest as it's created during parsing tree fragments and it di ers accross versions. I you want to compare, I advise you to create a view like this one and link the results using the new common_hash: CREATE ALGORITHM=MERGE SQL SECURITY INVOKER VIEW `events_statements_summary_by_digest_hash` AS SELECT *, SHA2(TRIM(DIGEST_TEXT), 224) COMMON_HASH FROM performance_schema.events_statements_summary_by_digest; Copyright @ 2020 Oracle and/or its affiliates. 62 / 66
Thank you ! Copyright @ 2020 Oracle and/or its affiliates. 63 / 66
Don't forget that in one year MySQL 5.6 is EOL ! Copyright @ 2020 Oracle and/or its affiliates. 64 / 66
Upgrade to MySQL 8.0 It's time to upgrade to MySQL 8.0, the fastest MySQL adoption release ever ! Copyright @ 2020 Oracle and/or its affiliates. 65 / 66
Upgrade to MySQL 8.0 It's time to upgrade to MySQL 8.0, the fastest MySQL adoption release ever ! Copyright @ 2020 Oracle and/or its affiliates. 66 / 66

More Related Content

PDF
MySQL InnoDB Cluster / ReplicaSet - Tutorial
Kenny Gryp
 
PDF
Redo log
PaweOlchawa1
 
PPTX
MySQL_MariaDB로의_전환_기술요소-202212.pptx
NeoClova
 
PDF
Performance Schema for MySQL troubleshooting
Sveta Smirnova
 
PDF
DataOpsbarcelona 2019: Deep dive into MySQL Group Replication... the magic e...
Frederic Descamps
 
PDF
Open Source 101 2022 - MySQL Indexes and Histograms
Frederic Descamps
 
PDF
MySQL Advanced Administrator 2021 - 네오클로바
NeoClova
 
PPTX
MySQL8.0_performance_schema.pptx
NeoClova
 
MySQL InnoDB Cluster / ReplicaSet - Tutorial
Kenny Gryp
 
Redo log
PaweOlchawa1
 
MySQL_MariaDB로의_전환_기술요소-202212.pptx
NeoClova
 
Performance Schema for MySQL troubleshooting
Sveta Smirnova
 
DataOpsbarcelona 2019: Deep dive into MySQL Group Replication... the magic e...
Frederic Descamps
 
Open Source 101 2022 - MySQL Indexes and Histograms
Frederic Descamps
 
MySQL Advanced Administrator 2021 - 네오클로바
NeoClova
 
MySQL8.0_performance_schema.pptx
NeoClova
 

What's hot (20)

PDF
MySQL Administrator 2021 - 네오클로바
NeoClova
 
PDF
MySQL InnoDB Cluster - A complete High Availability solution for MySQL
Olivier DASINI
 
PDF
MySQL 5.7 InnoDB Cluster (Jan 2018)
Olivier DASINI
 
PPT
MySQL Enterprise Edition
MySQL Brasil
 
PDF
MySQL Router REST API
Frederic Descamps
 
PDF
Greenplum Architecture
Alexey Grishchenko
 
PDF
MySQL Performance for DevOps
Sveta Smirnova
 
PPTX
ProxySQL for MySQL
Mydbops
 
PDF
MAA Best Practices for Oracle Database 19c
Markus Michalewicz
 
PDF
InnoDB Internal
mysqlops
 
PDF
MySQL 8.0 InnoDB Cluster - Easiest Tutorial
Frederic Descamps
 
PDF
MySQL InnoDB Cluster - Group Replication
Frederic Descamps
 
PDF
MySQL Performance Tuning. Part 1: MySQL Configuration (includes MySQL 5.7)
Aurimas Mikalauskas
 
PDF
MySQL InnoDB Cluster - Advanced Configuration & Operations
Frederic Descamps
 
PDF
Hash join in MySQL 8
Erik Frøseth
 
PDF
Introduction to Greenplum
Dave Cramer
 
PDF
MySQL Parallel Replication: All the 5.7 and 8.0 Details (LOGICAL_CLOCK)
Jean-François Gagné
 
PDF
Oracle_Multitenant_19c_-_All_About_Pluggable_D.pdf
SrirakshaSrinivasan2
 
PDF
MySQL Performance Schema in Action
Sveta Smirnova
 
PDF
MySQL InnoDB Cluster - New Features in 8.0 Releases - Best Practices
Kenny Gryp
 
MySQL Administrator 2021 - 네오클로바
NeoClova
 
MySQL InnoDB Cluster - A complete High Availability solution for MySQL
Olivier DASINI
 
MySQL 5.7 InnoDB Cluster (Jan 2018)
Olivier DASINI
 
MySQL Enterprise Edition
MySQL Brasil
 
MySQL Router REST API
Frederic Descamps
 
Greenplum Architecture
Alexey Grishchenko
 
MySQL Performance for DevOps
Sveta Smirnova
 
ProxySQL for MySQL
Mydbops
 
MAA Best Practices for Oracle Database 19c
Markus Michalewicz
 
InnoDB Internal
mysqlops
 
MySQL 8.0 InnoDB Cluster - Easiest Tutorial
Frederic Descamps
 
MySQL InnoDB Cluster - Group Replication
Frederic Descamps
 
MySQL Performance Tuning. Part 1: MySQL Configuration (includes MySQL 5.7)
Aurimas Mikalauskas
 
MySQL InnoDB Cluster - Advanced Configuration & Operations
Frederic Descamps
 
Hash join in MySQL 8
Erik Frøseth
 
Introduction to Greenplum
Dave Cramer
 
MySQL Parallel Replication: All the 5.7 and 8.0 Details (LOGICAL_CLOCK)
Jean-François Gagné
 
Oracle_Multitenant_19c_-_All_About_Pluggable_D.pdf
SrirakshaSrinivasan2
 
MySQL Performance Schema in Action
Sveta Smirnova
 
MySQL InnoDB Cluster - New Features in 8.0 Releases - Best Practices
Kenny Gryp
 
Ad

Similar to preFOSDEM MySQL Day - Best Practices to Upgrade to MySQL 8.0 (20)

PDF
MySQL Day Virtual: Best Practices Tips - Upgrading to MySQL 8.0
Frederic Descamps
 
PDF
Upgrade from MySQL 5.7 to MySQL 8.0
Olivier DASINI
 
PDF
MySQL Day Paris 2018 - Upgrade from MySQL 5.7 to MySQL 8.0
Olivier DASINI
 
PDF
Oracle Open World Middle East - MySQL 8 a Giant Leap for SQL
Frederic Descamps
 
PDF
Upgrading to my sql 8.0
Ståle Deraas
 
PDF
State of the Dolphin 2020 - 25th Anniversary of MySQL with 8.0.20
Frederic Descamps
 
PDF
the State of the Dolphin - October 2020
Frederic Descamps
 
PDF
MySQL : State of the Dolphin May 2019
Frederic Descamps
 
PDF
Automatic upgrade and new error logging in my sql 8.0
Ståle Deraas
 
PDF
MySQL Day Paris 2018 - Introduction & The State of the Dolphin
Olivier DASINI
 
PDF
MySQL Innovation: from 5.7 to 8.0
Frederic Descamps
 
PDF
MySQL Innovation from 5.7 to 8.0
Frederic Descamps
 
PDF
MySQL 8: Ready for Prime Time
Arnab Ray
 
PPTX
Upgrading to MySQL 8.0 webinar slides November 27th, 2019
Dave Stokes
 
PPTX
MySQL Quick Dive
Sudipta Kumar Sahoo
 
PPTX
MySQL 8.0 in a nutshell
OracleMySQL
 
PPTX
State ofdolphin short
Mandy Ang
 
PDF
MySQL Community Meetup in China : Innovation driven by the Community
Frederic Descamps
 
PDF
01 upgrade to my sql8
Ted Wennmark
 
PDF
Upgrade to MySQL 8.0!
Ted Wennmark
 
MySQL Day Virtual: Best Practices Tips - Upgrading to MySQL 8.0
Frederic Descamps
 
Upgrade from MySQL 5.7 to MySQL 8.0
Olivier DASINI
 
MySQL Day Paris 2018 - Upgrade from MySQL 5.7 to MySQL 8.0
Olivier DASINI
 
Oracle Open World Middle East - MySQL 8 a Giant Leap for SQL
Frederic Descamps
 
Upgrading to my sql 8.0
Ståle Deraas
 
State of the Dolphin 2020 - 25th Anniversary of MySQL with 8.0.20
Frederic Descamps
 
the State of the Dolphin - October 2020
Frederic Descamps
 
MySQL : State of the Dolphin May 2019
Frederic Descamps
 
Automatic upgrade and new error logging in my sql 8.0
Ståle Deraas
 
MySQL Day Paris 2018 - Introduction & The State of the Dolphin
Olivier DASINI
 
MySQL Innovation: from 5.7 to 8.0
Frederic Descamps
 
MySQL Innovation from 5.7 to 8.0
Frederic Descamps
 
MySQL 8: Ready for Prime Time
Arnab Ray
 
Upgrading to MySQL 8.0 webinar slides November 27th, 2019
Dave Stokes
 
MySQL Quick Dive
Sudipta Kumar Sahoo
 
MySQL 8.0 in a nutshell
OracleMySQL
 
State ofdolphin short
Mandy Ang
 
MySQL Community Meetup in China : Innovation driven by the Community
Frederic Descamps
 
01 upgrade to my sql8
Ted Wennmark
 
Upgrade to MySQL 8.0!
Ted Wennmark
 
Ad

More from Frederic Descamps (20)

PDF
MySQL Innovation & Cloud Day - Document Store avec MySQL HeatWave Database Se...
Frederic Descamps
 
PDF
MySQL Day Roma - MySQL Shell and Visual Studio Code Extension
Frederic Descamps
 
PDF
RivieraJUG - MySQL Indexes and Histograms
Frederic Descamps
 
PDF
RivieraJUG - MySQL 8.0 - What's new for developers.pdf
Frederic Descamps
 
PDF
MySQL User Group NL - MySQL 8
Frederic Descamps
 
PDF
State of the Dolphin - May 2022
Frederic Descamps
 
PDF
Percona Live 2022 - MySQL Shell for Visual Studio Code
Frederic Descamps
 
PDF
Percona Live 2022 - The Evolution of a MySQL Database System
Frederic Descamps
 
PDF
Percona Live 2022 - MySQL Architectures
Frederic Descamps
 
PDF
LinuxFest Northwest 2022 - The Evolution of a MySQL Database System
Frederic Descamps
 
PDF
Pi Day 2022 - from IoT to MySQL HeatWave Database Service
Frederic Descamps
 
PDF
Confoo 2022 - le cycle d'une instance MySQL
Frederic Descamps
 
PDF
FOSDEM 2022 MySQL Devroom: MySQL 8.0 - Logical Backups, Snapshots and Point-...
Frederic Descamps
 
PDF
Les nouveautés de MySQL 8.0
Frederic Descamps
 
PDF
Les nouveautés de MySQL 8.0
Frederic Descamps
 
PDF
State of The Dolphin - May 2021
Frederic Descamps
 
PDF
MySQL Shell for DBAs
Frederic Descamps
 
PDF
Deploying Magento on OCI with MDS
Frederic Descamps
 
PDF
From single MySQL instance to High Availability: the journey to MySQL InnoDB ...
Frederic Descamps
 
PDF
Cloud native - Why to use MySQL 8.0 and how to use it on oci with MDS
Frederic Descamps
 
MySQL Innovation & Cloud Day - Document Store avec MySQL HeatWave Database Se...
Frederic Descamps
 
MySQL Day Roma - MySQL Shell and Visual Studio Code Extension
Frederic Descamps
 
RivieraJUG - MySQL Indexes and Histograms
Frederic Descamps
 
RivieraJUG - MySQL 8.0 - What's new for developers.pdf
Frederic Descamps
 
MySQL User Group NL - MySQL 8
Frederic Descamps
 
State of the Dolphin - May 2022
Frederic Descamps
 
Percona Live 2022 - MySQL Shell for Visual Studio Code
Frederic Descamps
 
Percona Live 2022 - The Evolution of a MySQL Database System
Frederic Descamps
 
Percona Live 2022 - MySQL Architectures
Frederic Descamps
 
LinuxFest Northwest 2022 - The Evolution of a MySQL Database System
Frederic Descamps
 
Pi Day 2022 - from IoT to MySQL HeatWave Database Service
Frederic Descamps
 
Confoo 2022 - le cycle d'une instance MySQL
Frederic Descamps
 
FOSDEM 2022 MySQL Devroom: MySQL 8.0 - Logical Backups, Snapshots and Point-...
Frederic Descamps
 
Les nouveautés de MySQL 8.0
Frederic Descamps
 
Les nouveautés de MySQL 8.0
Frederic Descamps
 
State of The Dolphin - May 2021
Frederic Descamps
 
MySQL Shell for DBAs
Frederic Descamps
 
Deploying Magento on OCI with MDS
Frederic Descamps
 
From single MySQL instance to High Availability: the journey to MySQL InnoDB ...
Frederic Descamps
 
Cloud native - Why to use MySQL 8.0 and how to use it on oci with MDS
Frederic Descamps
 

Recently uploaded (20)

PPTX
Essential Infomation Tech presentation.pptx
pradeepjava2016
 
PDF
Internet Downloader Manager (IDM) Crack 6.42 Build 42 Updates Latest 2025
itskinga12
 
PDF
How to Choose the Right IT Partner for Your Business in Malaysia
Asian Business Services & Technologies
 
PDF
Flood Susceptibility Mapping Using Image-Based 2D-CNN Deep Learnin. Overview ...
lawrenceomai2
 
PDF
Navsoft: AI-Powered Business Solutions & Custom Software Development
Navsoft
 
PDF
Adobe Illustrator 28.6 Crack My Vision of Vector Design
ghrom2211g
 
PDF
EN-Survey-Report-SAP-LeanIX-EA-Insights-2025.pdf
deepakkhaitan3
 
PDF
System and Network Administraation Chapter 3
jaramharo
 
PDF
SAP S4 Hana Brochure 3 (PTS SYSTEMS AND SOLUTIONS)
pts464036
 
PDF
Audit Checklist Design Aligning with ISO, IATF, and Industry Standards — Omne...
rohnjim07
 
PPTX
Operating system designcfffgfgggggggvggggggggg
rmskumara09
 
PPTX
Transform Your Business with a Software ERP System
Canada Software Company
 
PDF
T3DD25 TYPO3 Content Blocks - Deep Dive by André Kraus
Andre Kraus
 
PDF
Adobe Premiere Pro 2025 (v24.5.0.057) Crack free
ghrom2211g
 
PDF
System and Network Administration Chapter 2
jaramharo
 
PPTX
Reimagine Home Health with the Power of Agentic AI​
AutomationEdge Technologies
 
PDF
top salesforce developer skills in 2025.pdf
CloudMetic
 
PDF
wealthsignaloriginal-com-DS-text-... (1).pdf
skmiani786
 
PDF
medical staffing services at VALiNTRY
Tiyan Grayson
 
PDF
Design an Analysis of Algorithms I-SECS-1021-03
DilanEscobar1
 
Essential Infomation Tech presentation.pptx
pradeepjava2016
 
Internet Downloader Manager (IDM) Crack 6.42 Build 42 Updates Latest 2025
itskinga12
 
How to Choose the Right IT Partner for Your Business in Malaysia
Asian Business Services & Technologies
 
Flood Susceptibility Mapping Using Image-Based 2D-CNN Deep Learnin. Overview ...
lawrenceomai2
 
Navsoft: AI-Powered Business Solutions & Custom Software Development
Navsoft
 
Adobe Illustrator 28.6 Crack My Vision of Vector Design
ghrom2211g
 
EN-Survey-Report-SAP-LeanIX-EA-Insights-2025.pdf
deepakkhaitan3
 
System and Network Administraation Chapter 3
jaramharo
 
SAP S4 Hana Brochure 3 (PTS SYSTEMS AND SOLUTIONS)
pts464036
 
Audit Checklist Design Aligning with ISO, IATF, and Industry Standards — Omne...
rohnjim07
 
Operating system designcfffgfgggggggvggggggggg
rmskumara09
 
Transform Your Business with a Software ERP System
Canada Software Company
 
T3DD25 TYPO3 Content Blocks - Deep Dive by André Kraus
Andre Kraus
 
Adobe Premiere Pro 2025 (v24.5.0.057) Crack free
ghrom2211g
 
System and Network Administration Chapter 2
jaramharo
 
Reimagine Home Health with the Power of Agentic AI​
AutomationEdge Technologies
 
top salesforce developer skills in 2025.pdf
CloudMetic
 
wealthsignaloriginal-com-DS-text-... (1).pdf
skmiani786
 
medical staffing services at VALiNTRY
Tiyan Grayson
 
Design an Analysis of Algorithms I-SECS-1021-03
DilanEscobar1
 

preFOSDEM MySQL Day - Best Practices to Upgrade to MySQL 8.0

  • 2. Frédéric Descamps Community Manager MySQL Best practices to upgrade to MySQL 8.0 MySQL 8 is Great ! 2 / 66
  • 3.   Safe Harbor The following is intended to outline our general product direction. It is intended for information purpose only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied up in making purchasing decisions. The development, release, timing and pricing of any features or functionality described for Oracle´s product may change and remains at the sole discretion of Oracle Corporation. Statement in this presentation relating to Oracle´s future plans, expectations, beliefs, intentions and ptospects are "forward-looking statements" and are subject to material risks and uncertainties. A detailed discussion of these factors and other risks that a ect our business is contained in Oracle´s Securities and Exchange Commission (SEC) lings, including our most recent reports on Form 10-K and Form 10-Q under the heading "Risk Factors". These lings are available on the SEC´s website or on Oracle´s website at h p://www.oracle.com/investor. All information in this presentation is current as of September 2019 and Oracle undertakes no duty to update any statement in light of new information or future events. Copyright @ 2020 Oracle and/or its affiliates. 3 / 66
  • 4. about.me/lefred Who am I ? Copyright @ 2020 Oracle and/or its affiliates. 4 / 66
  • 5. Frédéric Descamps @lefred MySQL Evangelist Managing MySQL since 3.23 devops believer living in Belgium 🇧🇪 h ps://lefred.be Copyright @ 2020 Oracle and/or its affiliates. 5 / 66
  • 6. Migrating to MySQL 8.0 Why ? Copyright @ 2020 Oracle and/or its affiliates. 6 / 66
  • 7. DB-Engines 2019 Database Ranking Copyright @ 2020 Oracle and/or its affiliates. 7 / 66
  • 8. DB-Engines 2019 Database Ranking MySQL is the 2nd most popular database Copyright @ 2020 Oracle and/or its affiliates. 8 / 66
  • 9. DB-Engines 2019 Database Ranking MySQL is the 2nd most popular database MySQL is the most Open Source popular database Copyright @ 2020 Oracle and/or its affiliates. 9 / 66
  • 10. MySQL is the DBMS of the Year 2019 ! Copyright @ 2020 Oracle and/or its affiliates. 10 / 66
  • 11. MySQL Developer Popularity Stack Overflow Developer Survey 2019 Copyright @ 2020 Oracle and/or its affiliates. 11 / 66
  • 12. MySQL is the most popular database with developers MySQL Developer Popularity Stack Overflow Developer Survey 2019 Copyright @ 2020 Oracle and/or its affiliates. 12 / 66
  • 13. April 2018 (8.0 GA) August 2019 MySQL 8.0: fastest adoption !! Copyright @ 2020 Oracle and/or its affiliates. 13 / 66
  • 14. "This is a landmark release as MySQL eventually evolved beyond SQL-92 and the purely relational dogma. Among a few other standard SQL features, MySQL now supports window functions (over) and common table expressions (with). Without a doubt, these are the two most important post-SQL-92 features.” MySQL 8.0: one giant leap for SQL Copyright @ 2020 Oracle and/or its affiliates. 14 / 66
  • 15. and many more features ! Copyright @ 2020 Oracle and/or its affiliates. 15 / 66
  • 16. I want to upgrade to MySQL 8.0 First Steps Copyright @ 2020 Oracle and/or its affiliates. 16 / 66
  • 17. Some Mandatory Literature... DISCLAMER: No need to read the full manual each time MySQL releases a new version /cc @marcotusa Copyright @ 2020 Oracle and/or its affiliates. 17 / 66
  • 18. Some Mandatory Literature... DISCLAMER: No need to read the full manual each time MySQL releases a new version /cc @marcotusa For any upgrade (minor and major), you need to rst read the release notes: h ps://dev.mysql.com/doc/relnotes/mysql/8.0/en/ Copyright @ 2020 Oracle and/or its affiliates. 18 / 66
  • 19. Some Mandatory Literature... DISCLAMER: No need to read the full manual each time MySQL releases a new version /cc @marcotusa For any upgrade (minor and major), you need to rst read the release notes: h ps://dev.mysql.com/doc/relnotes/mysql/8.0/en/ Changes in MySQL 8: h ps://dev.mysql.com/doc/refman/8.0/en/upgrading-from- previous-series.html Copyright @ 2020 Oracle and/or its affiliates. 19 / 66
  • 20. Some Mandatory Literature... DISCLAMER: No need to read the full manual each time MySQL releases a new version /cc @marcotusa For any upgrade (minor and major), you need to rst read the release notes: h ps://dev.mysql.com/doc/relnotes/mysql/8.0/en/ Changes in MySQL 8: h ps://dev.mysql.com/doc/refman/8.0/en/upgrading-from- previous-series.html Verify your con guration le for removed se ings: h ps://dev.mysql.com/doc/refman/8.0/en/added-deprecated-removed.html Copyright @ 2020 Oracle and/or its affiliates. 20 / 66
  • 21. Is My Application Ready ? There are some points very important to verify before upgrading to MySQL 8.0: Copyright @ 2020 Oracle and/or its affiliates. 21 / 66
  • 22. Is My Application Ready ? There are some points very important to verify before upgrading to MySQL 8.0: Is the driver recent enough and if not can it be upgraded ? Copyright @ 2020 Oracle and/or its affiliates. 22 / 66
  • 23. Is My Application Ready ? There are some points very important to verify before upgrading to MySQL 8.0: Is the driver recent enough and if not can it be upgraded ? Is my application using a speci c SQL mode ? Copyright @ 2020 Oracle and/or its affiliates. 23 / 66
  • 24. Is My Application Ready ? There are some points very important to verify before upgrading to MySQL 8.0: Is the driver recent enough and if not can it be upgraded ? Is my application using a speci c SQL mode ? Is my application using queries speci c to some SQL mode ? Copyright @ 2020 Oracle and/or its affiliates. 24 / 66
  • 25. Is My Application Ready ? There are some points very important to verify before upgrading to MySQL 8.0: Is the driver recent enough and if not can it be upgraded ? Is my application using a speci c SQL mode ? Is my application using queries speci c to some SQL mode ? Does my replication relies somehow to Information_Schema or other system (mysql.*) tables ? Copyright @ 2020 Oracle and/or its affiliates. 25 / 66
  • 26. Connector and Authentication the new default authentication plugin (caching_sha2_password) is more secure but not supported with old connectors. all the new connectors provided by MySQL are compatible. Copyright @ 2020 Oracle and/or its affiliates. 26 / 66
  • 27. Connector and Authentication the new default authentication plugin (caching_sha2_password) is more secure but not supported with old connectors. all the new connectors provided by MySQL are compatible. if your connector doesn't support the new authentication plugin, you should force the use of the old native one by adding in my.cnf: default-authentication-plugin = mysql_native_password Copyright @ 2020 Oracle and/or its affiliates. 27 / 66
  • 28. mysql> select user, plugin from mysql.user limit 2; +-------+-----------------------+ | user | plugin | +-------+-----------------------+ | books | mysql_native_password | | dev | caching_sha2_password | +-------+-----------------------+ 2 rows in set (0.00 sec) 8.0 Connector and Authentication (2) be sure the credentials used by your application use the right plugin: Copyright @ 2020 Oracle and/or its affiliates. 28 / 66
  • 29. Example of PHP Support Copyright @ 2020 Oracle and/or its affiliates. 29 / 66
  • 30. Example of PHP Support (2) Copyright @ 2020 Oracle and/or its affiliates. 30 / 66
  • 31. Example of PHP Support (3) Copyright @ 2020 Oracle and/or its affiliates. 31 / 66
  • 32. SQL Mode The SQL Mode default has been changed Version Default SQL Mode 5.6 NO_ENGINE_SUBSTITUTION 5.7 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_AUTO_CREATE_USER, NO_ENGINE_SUBSTITUTION 8.0 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_ENGINE_SUBSTITUTION Copyright @ 2020 Oracle and/or its affiliates. 32 / 66
  • 33. SQL Mode The SQL Mode default has been changed Version Default SQL Mode 5.6 NO_ENGINE_SUBSTITUTION 5.7 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_AUTO_CREATE_USER, NO_ENGINE_SUBSTITUTION 8.0 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_ENGINE_SUBSTITUTION #1055 - Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'xxx' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by Copyright @ 2020 Oracle and/or its affiliates. 33 / 66
  • 34. SQL Mode The SQL Mode default has been changed Version Default SQL Mode 5.6 NO_ENGINE_SUBSTITUTION 5.7 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_AUTO_CREATE_USER, NO_ENGINE_SUBSTITUTION 8.0 ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE, ERROR_FOR_DIVISION_BY_ZERO, NO_ENGINE_SUBSTITUTION #1055 - Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'xxx' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by And be aware that some have been removed and might cause error: frameworks had Error: PDOException::("SQLSTATE[42000]: Syntax error or access violation: 1231 Variable 'sql_mode' can't be set to the value of 'NO_AUTO_CREATE_USER'") Copyright @ 2020 Oracle and/or its affiliates. 34 / 66
  • 35. Upgrade Checker Copyright @ 2020 Oracle and/or its affiliates. 35 / 66
  • 36. Don't forget to use MySQL Shell Upgrade Checker Utility New tool in MySQL Shell Will check your MySQL 5.7 or 8.0 installation readiness for upgrade to latest version Check for legacy issues Run the tool on the 5.7 before upgrading! Always use latest version of MySQL Shell Copyright @ 2020 Oracle and/or its affiliates. 36 / 66
  • 37. Don't forget to use MySQL Shell Upgrade Checker Utility New tool in MySQL Shell Will check your MySQL 5.7 or 8.0 installation readiness for upgrade to latest version Check for legacy issues Run the tool on the 5.7 before upgrading! Always use latest version of MySQL Shell Util.checkForServerUpgrade: Detected MySQL server version is 5.5.62, but this tool requires server to be at least at version 5.7 (LogicError) Copyright @ 2020 Oracle and/or its affiliates. 37 / 66
  • 38. usage of old temporal type usage of new reserved keywords usage of udt8mb3 charset con icting name in mysql schema partitions with engine not supporting native partitioning foreign key constraint names longer than 64 characters usage of obsolete MAXDB SQL mode ag usage of orther obsolete SQL mode ags ENUM/SET column de nitions containing elements longer than 255 characters usage of partitioned tables in shared tablespaces MySQL Shell Upgrade Checker Utility Upgrade Checker performs the following checks: Copyright @ 2020 Oracle and/or its affiliates. 38 / 66
  • 39. circular directory references in tablespace data le paths usage of removed functions usage of removed GROUP BY ASC/DESC syntax removed system variables for error logging to the system log con guration removed system variables system variables with new default values schema inconsistencies resulting from le removal or corruption table names containing 'FTS' issues reported by 'check table x for upgrade' command MySQL Shell Upgrade Checker Utility (2) Copyright @ 2020 Oracle and/or its affiliates. 39 / 66
  • 40. MySQL Upgrade Checker: how to use it? From the system shell: $ mysqlsh -- util checkForServerUpgrade user@localhost:3306 --target-version=8.0.19 --output-format=JSON --con g-path=/etc/mysql/my.cnf From the New MySQL Shell: mysqlsh> util.checkForServerUpgrade('user@example.com:3306', {"password":"password", "targetVersion":"8.0.19", "con gPath":"/etc/my.cnf"}) mysqlsh> util.checkForServerUpgrade() Copyright @ 2020 Oracle and/or its affiliates. 40 / 66
  • 41. I want to upgrade to MySQL 8.0 Let's do it ! Copyright @ 2020 Oracle and/or its affiliates. 41 / 66
  • 42. From MySQL 5.5 to MySQL 8.0 To migrate to a newer version we have 2 options: logical dump & restore in-place upgrade Copyright @ 2020 Oracle and/or its affiliates. 42 / 66
  • 43. Logical Dump & Restore This is the easiest option if you don't have too much data or if you can a ord a long dump and import time: dump the data: $ mysqldump -A > dump.sql stop the MySQL Service: $ sudo systemctl stop mysqld upgrade the binaries: $ sudo yum upgrade mysql-community* Copyright @ 2020 Oracle and/or its affiliates. 43 / 66
  • 44. Logical Dump & Restore (2) erase the content of the data directory: $ sudo rm -f /var/lib/mysql/* if you plan to load the system tables (like in this example), please change in my.cnf: default-authentication-plugin = mysql_native_password start the MySQL Service (that will initialize the service): $ sudo systemctl start mysqld A new password has been generated, you can nd it in the error log. You need to change it, it's a good time to use a new password for root ;-) Copyright @ 2020 Oracle and/or its affiliates. 44 / 66
  • 45. Logical Dump & Restore (3) restore the data: $ mysql -u root -p < dump.sql as we restored system tables too, it's be er to restart mysqld and force and upgrade: $ sudo systemctl set-environment MYSQLD_OPTS="--upgrade=FORCE" $ sudo systemctl restart mysqld $ sudo systemctl unset-environment MYSQLD_OPTS Copyright @ 2020 Oracle and/or its affiliates. 45 / 66
  • 46. Logical Dump & Restore (3) restore the data: $ mysql -u root -p < dump.sql as we restored system tables too, it's be er to restart mysqld and force and upgrade: $ sudo systemctl set-environment MYSQLD_OPTS="--upgrade=FORCE" $ sudo systemctl restart mysqld $ sudo systemctl unset-environment MYSQLD_OPTS mysql> s -------------- mysql Ver 8.0.19 for Linux on x86_64 (MySQL Community Server - GPL) Copyright @ 2020 Oracle and/or its affiliates. 46 / 66
  • 47. In-place Upgrade When you have a lot of data and that you consider that a single-thread logical dump and restore is not an option: 5.5 to 5.6 edit my.cnf and add for the full upgrade process: innodb_fast_shutdown = 0 stop the MySQL Service: $ sudo systemctl stop mysqld upgrade the binaries to 5.6: $ sudo yum upgrade mysql-community-* --disablerepo=mysql* --enablerepo=mysql56-community Copyright @ 2020 Oracle and/or its affiliates. 47 / 66
  • 48. In-place Upgrade (2) start the MySQL Service: $ sudo systemctl start mysqld 2020-01-27 21:46:42 21955 [ERROR] Column count of mysql.threads is wrong. Expected 14, found 3. Created with MySQL 50562, now running 50647. Please use mysql_upgrade to x this error. as the error log recommends it, we must also run mysql_upgrade: $ sudo mysql_upgrade and don't forget to restart again MySQL: $ sudo systemctl restart mysqld Copyright @ 2020 Oracle and/or its affiliates. 48 / 66
  • 49. In-place Upgrade (3) We can perform some checks on InnoDB Formats: mysql> SELECT FILE_FORMAT, ROW_FORMAT, count(*) Tot FROM INFORMATION_SCHEMA.INNODB_SYS_TABLES GROUP BY FILE_FORMAT, ROW_FORMAT; +-------------+------------+-----+ | FILE_FORMAT | ROW_FORMAT | Tot | +-------------+------------+-----+ | Antelope | Compact | 15 | | Antelope | Redundant | 4 | +-------------+------------+-----+ Let's check if we have old temporal columns: Copyright @ 2020 Oracle and/or its affiliates. 49 / 66
  • 50. In-place Upgrade (4) mysql> SELECT t.TABLE_SCHEMA,t.ENGINE,t.TABLE_NAME,c.COLUMN_NAME,c.COLUMN_TYPE FROM INFORMATION_SCHEMA.TABLES t INNER JOIN INFORMATION_SCHEMA.COLUMNS c ON c.TABLE_SCHEMA = t.TABLE_SCHEMA AND c.TABLE_NAME = t.TABLE_NAME LEFT OUTER JOIN INFORMATION_SCHEMA.INNODB_SYS_TABLES ist ON ist.NAME = CONCAT(t.TABLE_SCHEMA,'/',t.TABLE_NAME) LEFT OUTER JOIN INFORMATION_SCHEMA.INNODB_SYS_COLUMNS isc ON isc.TABLE_ID = ist.TABLE_ID AND isc.NAME = c.COLUMN_NAME WHERE c.COLUMN_TYPE IN ('time', 'timestamp', 'datetime') AND t.TABLE_SCHEMA NOT IN ('mysql', 'information_schema', 'performance_schema') AND t.TABLE_TYPE = 'base table' AND (t.ENGINE != 'innodb' OR (t.ENGINE = 'innodb' AND isc.MTYPE = 6)) ORDER BY t.TABLE_SCHEMA, t.TABLE_NAME, c.COLUMN_NAME; +--------------+--------+-------------+---------------+-------------+ | TABLE_SCHEMA | ENGINE | TABLE_NAME | COLUMN_NAME | COLUMN_TYPE | +--------------+--------+-------------+---------------+-------------+ | sbtest_tpcc | InnoDB | customer1 | c_since | datetime | | sbtest_tpcc | InnoDB | history1 | h_date | datetime | | sbtest_tpcc | InnoDB | orders1 | o_entry_d | datetime | | sbtest_tpcc | InnoDB | orders2 | o_entry_d | datetime | | sbtest_tpcc | InnoDB | order_line1 | ol_delivery_d | datetime | +--------------+--------+-------------+---------------+-------------+ Copyright @ 2020 Oracle and/or its affiliates. 50 / 66
  • 51. In-place Upgrade (5) 5.6 to 5.7 stop the MySQL Service: $ sudo systemctl stop mysqld upgrade the binaries to 5.7: $ sudo yum upgrade mysql-community-* --disablerepo=mysql* --enablerepo=mysql57-community start the MySQL Service: $ sudo systemctl start mysqld Copyright @ 2020 Oracle and/or its affiliates. 51 / 66
  • 52. In-place Upgrade (6) we run mysql_upgrade: $ sudo mysql_upgrade We can see that the process also repairs some tables (with the previous old time format): Checking databases. sbtest_tpcc.customer1 error : Table rebuild required. Please do "ALTER TABLE `customer1` FORCE" or dump/reload to x it! ... Repairing tables `sbtest_tpcc`.`customer1` Running : ALTER TABLE `sbtest_tpcc`.`customer1` FORCE status : OK ... Upgrade process completed successfully. Copyright @ 2020 Oracle and/or its affiliates. 52 / 66
  • 53. In-place Upgrade (7) and don't forget to restart again MySQL: $ sudo systemctl restart mysqld let's verify mysql> SELECT FILE_FORMAT, ROW_FORMAT, count(*) Tot FROM INFORMATION_SCHEMA.INNODB_SYS_TABLES GROUP BY FILE_FORMAT, ROW_FORMAT; +-------------+------------+-----+ | FILE_FORMAT | ROW_FORMAT | Tot | +-------------+------------+-----+ | Antelope | Compact | 5 | | Antelope | Redundant | 5 | | Barracuda | Dynamic | 25 | +-------------+------------+-----+ Copyright @ 2020 Oracle and/or its affiliates. 53 / 66
  • 54. In-place Upgrade (8) 5.7 to 8.0 now we can use MySQL Upgrade Checker: $ mysqlsh -- util checkForServerUpgrade root@localhost --con g-path=/etc/my.cnf The MySQL server at localhost, version 5.7.29 - MySQL Community Server (GPL), will now be checked for compatibility issues for upgrade to MySQL 8.0.19... ... Errors: 0 Warnings: 28 Notices: 0 No fatal errors were found that would prevent an upgrade, but some potential issues were detected. Please ensure that the reported issues are not signi cant before upgrading. Copyright @ 2020 Oracle and/or its affiliates. 54 / 66
  • 55. MySQL Upgrade Checker : details 16) System variables with new default values Warning: Following system variables that are not de ned in your con guration le will have new default values. Please review if you rely on their current values and if so de ne them before performing upgrade. More information: https://mysqlserverteam.com/new-defaults-in-mysql-8-0/ back_log - default value will change character_set_server - default value will change from latin1 to utf8mb4 collation_server - default value will change from latin1_swedish_ci to utf8mb4_0900_ai_ci event_scheduler - default value will change from OFF to ON explicit_defaults_for_timestamp - default value will change from OFF to ON innodb_autoinc_lock_mode - default value will change from 1 (consecutive) to 2 (interleaved) innodb_ ush_method - default value will change from NULL to fsync (Unix), unbuffered (Windows) innodb_ ush_neighbors - default value will change from 1 (enable) to 0 (disable) innodb_max_dirty_pages_pct - default value will change from 75 (%) 90 (%) innodb_max_dirty_pages_pct_lwm - default value will change from_0 (%) to 10 (%) innodb_undo_log_truncate - default value will change from OFF to ON ... Copyright @ 2020 Oracle and/or its affiliates. 55 / 66
  • 56. MySQL Upgrade Checker : details (2) 17) Zero Date, Datetime, and Timestamp values Warning: By default zero date/datetime/timestamp values are no longer allowed in MySQL, as of 5.7.8 NO_ZERO_IN_DATE and NO_ZERO_DATE are included in SQL_MODE by default. These modes should be used with strict mode as they will be merged with strict mode in a future release. If you do not include these modes in your SQL_MODE setting, you are able to insert date/datetime/timestamp values that contain zeros. It is strongly advised to replace zero values with valid ones, as they may not work correctly in the future. More information: https://lefred.be/content/mysql-8-0-and-wrong-dates/ sbtest_tpcc.orders2.o_entry_d - column has zero default value: 0000-00-00 00:00:00 Copyright @ 2020 Oracle and/or its affiliates. 56 / 66
  • 57. Let's go to 🎱 ! stop the MySQL Service: $ sudo systemctl stop mysqld upgrade the binaries to 8.0: $ sudo yum upgrade mysql-community-* --disablerepo=mysql* --enablerepo=mysql80-community start the MySQL Service: $ sudo systemctl start mysqld Jan 27 22:55:13 mysql2 mysqld[23209]: 2020-01-27T22:55:13.783334Z 2 [System] [MY-011003] [Server] Finished populating Data Dictionary tables with data. Jan 27 22:55:14 mysql2 mysqld[23209]: 2020-01-27T22:55:14.432342Z 5 [System] [MY-013381] [Server] Server upgrade from '50700' to '80019' started. Jan 27 22:55:23 mysql2 mysqld[23209]: 2020-01-27T22:55:23.439943Z 5 [System] [MY-013381] [Server] Server upgrade from '50700' to '80019' completed. Copyright @ 2020 Oracle and/or its affiliates. 57 / 66
  • 58. Woooohoooo o/ Copyright @ 2020 Oracle and/or its affiliates. 58 / 66
  • 59. MySQL 8.0 is Great ! Copyright @ 2020 Oracle and/or its affiliates. 59 / 66
  • 60. Post Checks MySQL Upgrade Checker warned us about the invalid default date, but it doesn't scan the data. It's possible to write some queries to verify this... or use a plugin for the MySQL Shell: Copyright @ 2020 Oracle and/or its affiliates. 60 / 66
  • 61. Post Checks (2) Let's verify the authentication methods used on our system: Copyright @ 2020 Oracle and/or its affiliates. 61 / 66
  • 62. Post Checks (3) Comparing Results from previous version is not a straight forward task, and even if you can rely on PFS tables, you cannot link the results between version relying on the digest as it's created during parsing tree fragments and it di ers accross versions. I you want to compare, I advise you to create a view like this one and link the results using the new common_hash: CREATE ALGORITHM=MERGE SQL SECURITY INVOKER VIEW `events_statements_summary_by_digest_hash` AS SELECT *, SHA2(TRIM(DIGEST_TEXT), 224) COMMON_HASH FROM performance_schema.events_statements_summary_by_digest; Copyright @ 2020 Oracle and/or its affiliates. 62 / 66
  • 63. Thank you ! Copyright @ 2020 Oracle and/or its affiliates. 63 / 66
  • 64. Don't forget that in one year MySQL 5.6 is EOL ! Copyright @ 2020 Oracle and/or its affiliates. 64 / 66
  • 65. Upgrade to MySQL 8.0 It's time to upgrade to MySQL 8.0, the fastest MySQL adoption release ever ! Copyright @ 2020 Oracle and/or its affiliates. 65 / 66
  • 66. Upgrade to MySQL 8.0 It's time to upgrade to MySQL 8.0, the fastest MySQL adoption release ever ! Copyright @ 2020 Oracle and/or its affiliates. 66 / 66