Upgrade from MySQL 5.7 to MySQL 8.0

Upgrade from MySQL 5.7 to MySQL 8.0
1 © 2020 Oracle MySQL
Olivier Dasini
MySQL Principal Solutions Architect EMEA
olivier.dasini@oracle.com
Twitter : @freshdaz
Blogs : http://dasini.net/blog/en
: http://dasini.net/blog/fr

Safe harbor statement
The following is intended to outline our general product direction. It is intended for information
purposes 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 upon in making purchasing
decisions.
The development, release, timing, and pricing of any features or functionality described for
Oracle’s products may change and remains at the sole discretion of Oracle Corporation.

3
Me, Myself & I

MySQL Geek
 Addicted to MySQL for 15+ years
 Playing with databases for 20+ years

MySQL Writer, Blogger and Speaker
 Also former : DBA, Consultant, Architect, Trainer, ...

MySQL Principal Solutions Architect EMEA at Oracle

Stay up to date!
 Twitter: @freshdaz
 Blog: http://dasini.net/blog
3
Olivier DASINI
Copyright © 2020 Oracle and/or its affiliates. All rights reserved.

Why MySQL ?
Program agenda
1
2
3
4
Why Upgrade ?
The Toolbox
Upgrade to MySQL 8.0
MySQL Enterprise Edition Overview5

Why MySQL ?

The world’s most popular open source database

Some Of Our Customers
 MySQL powers the most demanding Web, E-commerce, SaaS and Online Transaction Processing
(OLTP) applications
 It is a fully integrated transaction-safe, ACID compliant database with full commit, rollback, crash
recovery and row level locking capabilities
 MySQL delivers the ease of use, scalability, and performance to power:

Title only
They Scale
with
MySQL
Mobile Network
Supporting Over 800
Million Subscribers
2+ Billion Active Users
100 TB of User Data for PayPal
IDs Processed for
1 Billion Citizens
850 Million Candy
Crush Game Plays/Day
2 Billion Events/Day for
Booking.com

Explosive Data Growth
Source IDC, 2017 Source Domo, 2018

Why Upgrade ?

Why Upgrade ?
 New features
– InnoDB Cluster, InnoDB ReplicaSet, Clone plugin, Instant Add Column, JSON Document Store, CTE, Window
Functions, JSON, GIS, Functional indexes, Hash Joins, Histograms, Check Constraints, ...
– New features in 8.0: https://mysqlserverteam.com/the-complete-list-of-new-features-in-mysql-8-0/
 Security improvements
– New Authentication Plugin, SSL/TLS, SQL Roles, Tables & Log Encryption, Password management, ...
 Performance/Scalability improvements
– Cost Model, Histograms, P_S, I_S, Scaling R/W workloads, Resource Groups, ...
 Manageability
– Set Persist, Invisible Indexes, Restart command, Instant Add Column,
– InnoDB Cluster / Group Replication, InnoDB ReplicaSet, ...
 Reduce tech debt for the MySQL installation
– Softer upgrades
 Stay on fully supported release
 ...
Because “MySQL 8 Is Great” :) but also for...

Why Upgrade ? - MySQL 8.0 New Features
 What Is New in MySQL 8.0
– https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html
 The complete list of new features in MySQL 8.0
– https://mysqlserverteam.com/the-complete-list-of-new-features-in-mysql-8-0/
 What’s New in MySQL 8.0? (Generally Available)
– https://mysqlserverteam.com/whats-new-in-mysql-8-0-generally-available/
 Changes in MySQL 8.0...
– https://mysqlserverteam.com/changes-in-mysql-8-0-11-general-availability/
– https://mysqlserverteam.com/the-mysql-8-0-12-maintenance-release-is-generally-available/
– ...
– https://mysqlserverteam.com/the-mysql-8-0-21-maintenance-release-is-generally-available/
Over 300 new features in MySQL 8.0

Why Upgrade ? - Performance/Scalability improvements
2x Faster than MySQL 5.7 - SysBench IO Bound Read Only (Point Selects)
OS : Oracle Linux 7.4
CPU : 48cores-HT Intel Skylake 2.7Ghz
(2CPU sockets, Intel(R) Xeon(R) Platinum 8168 CPU)
RAM: 256GB
Storage : x2 Intel Optane flash devices
(Intel (R) Optane (TM) SSD P4800X Series)

Why Upgrade ? - MySQL Security
 SSL enabled by default
 Force root password during install
 Stronger passwords / Better password management features
 New Authentication Plugin
 MySQL Security: https://dev.mysql.com/doc/refman/8.0/en/security.html
 MySQL Enterprise Edition:
– MySQL Enterprise Audit
– MySQL Enterprise Monitor
– MySQL Enterprise Backup
– MySQL Enterprise Firewall
– MySQL Enterprise Encryption
– MySQL Enterprise Transparent Data Encryption
– MySQL Enterprise Data Masking and De-identification
– MySQL Enterprise Thread Pool
 MySQL Enterprise Security Overview: https://dev.mysql.com/doc/refman/8.0/en/mysql-enterprise-security.html
Privacy and Security requirements for GDPR, PCI DSS, HIPAA, …

MySQL Security Achitecture

Why Upgrade ? - Support Life Cycle
Release GA Date Premier Support End Extended Support End Sustaining Support End
MySQL 5.0 Oct 2005 Dec 2011 N/A Indefinite
MySQL 5.1 Dec 2008 Dec 2013 N/A Indefinite
MySQL 5.5 Dec 2010 Dec 2015 Dec 2018 Indefinite
MySQL 5.6 Feb 2013 Feb 2018 Feb 2021 Indefinite
MySQL 5.7 Oct 2015 Oct 2020 Oct 2023 Indefinite
MySQL 8.0 Apr 2018 Apr 2023 Feb 2026 Indefinite
http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf
Ensure that MySQL meets security, reliability & performance requirements

MySQL Upgrade – Supported Paths
 All minor upgrades are supported
– e.g. 8.0.19 → 8.0.20
– or doing a jump e.g. 8.0.17 → 8.0.21
 Upgrading one major release level is supported
– e.g. 5.6 → 5.7 , 5.7 → 8.0 , ...
– It’s recommended upgrading to the latest 5.7 release before moving to 8.0
 Doing long-jumps (e.g. 5.1 → 8.0) is supported if you upgrade one release level at a time
– e.g. 5.1 → 5.5 → 5.6 → 5.7 → 8.0
 Direct upgrades that skip a release level (for example, upgrading directly from MySQL 5.5 to 8.0) is
not recommended
 Yon can not upgrade from DMR to GA

MySQL Upgrade – Before you start !
 Review "Changes in MySQL 8.0" for changes that may require action before upgrading
– https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html
 Review "What Is New in MySQL 8.0" for added / deprecated / removed features
– https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html
 Review "Server and Status Variables and Options Added, Deprecated, or Removed in MySQL 8.0"
– If you use deprecated or removed variables, an upgrade may require configuration changes.
– https://dev.mysql.com/doc/refman/8.0/en/added-deprecated-removed.html
 Review "Release Notes" for information about fixes, changes, and new features
– https://dev.mysql.com/doc/relnotes/mysql/8.0/en/
 Create a plan for your upgrade/downgrade path
https://dev.mysql.com/doc/refman/8.0/en/upgrade-before-you-begin.html

MySQL 8.0 Defaults Changes - Samples
 There are a lot of changes to the defaults in 8.0, see
– https://mysqlserverteam.com/new-defaults-in-mysql-8-0/
 Use “MySQL Parameters” website:
– https://mysql-params.tmtms.net/mysqld/
 Some important ones:
– Default character set and collation to utf8mb4 and utf8mb4_0900_ai_ci
– The default/preferred authentication plugin caching_sha2_password
– log_bin has been changed from OFF to ON

(Some) New Servers Default’s in MySQL 8.0
 charset_set_server = utf8mb4
 collation_server = utf8mb4_0900_ai_ci
 event_scheduler = ON
 log_bin = ON
 server_id = 1
 Log-slave-updates = ON
 expire_log_days = 30
 Master-info-repository = TABLE
 Relay-log-info-repository = TABLE
 Transaction-write-set-extraction = XXHASH64
 … and many more, see link below for more details
– https://mysqlserverteam.com/new-defaults-in-mysql-8-0/

MySQL 8.0 Deprecation/Removals - Samples
 Features removed
– Query Cache, Non-native partitioning, ...
 Options and variables removed
– Log_errors/log_warnings replaced by log_error_verbosity
– SQL Modes removed
– https://dev.mysql.com/doc/refman/8.0/en/added-deprecated-removed.html
 Account management
– The PASSWORD() function has been removed, using GRANT to create users is no longer supported
 Syntaxes affected
– EXTENDED and PARTITIONS keywords for EXPLAIN removed
– N as a synonym for NULL in SQL removed. Use NULL instead

Before you Upgrade – Backups of Your Data!
 Database upgrading is very serious work!
– So backup your data!
 Plan for the worst - Paranoia is not always a bad things
– So backup your data!
 Use your favorite backup tool
– MySQL Enterprise Backup
– dumpInstance() / dumpSchema() / loadDump() from MySQL Shell
●
For MySQL Server 5.7 & 8.0
– mysqldump / mysqlpump
– …
 Double check your backups
 Test your Restore procedure
Credit: https://tricyclefish.com/wp-content/uploads/2016/01/back-up1.jpg

MySQL Enterprise Backup

MySQL Enterprise Backup
 Online, non-locking backup and recovery
– Complete MySQL instance backup (data and config)
– Full & Partial backup and restore
 Direct Cloud storage backups (S3, etc.)
 Incremental backups & Point-in-time recovery
 Advanced compressed and Strong encryption: AES 256
 Backup to tape (SBT)
 Backup validation
 Optimistic backups
 Cross-Platform (Windows, Linux, Unix)
 Certified with Oracle Secure Backup, NetBackup, Tivoli, ...
Ensure availability of end-user data

Instance Dump Utility
Schema Dump Utility
Dump Loading Utility

MySQL Shell dump utilities - dumpInstance & dumpSchemas
 Logical Dump Utilities from MySQL Shell (start with MySQL Shell 8.0.21)
– Instance dump: util.dumpInstance()
●
Dump an entire database instance, including users
– Schema dump: util.dumpSchemas()
●
Dump a set of schemas
– Support the export of all schemas or a selected schema from an on-premise MySQL server instance into a set of
local files or an Oracle Cloud Infrastructure Object Storage bucket
– The schemas can then be imported into a MySQL Database Service DB System using MySQL Shell's new dump
loading utility
– Provide Oracle Cloud Infrastructure Object Storage streaming, MySQL Database Service compatibility checks and
modifications, parallel dumping with multiple threads, and file compression
Export data from a MySQL instance into a set of local files or an OCI Object Storage bucket
https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-utilities-dump-instance-schema.html

MySQL Shell load utility - loadDump
 Logical Load Utility from MySQL Shell (start with MySQL Shell 8.0.21)
– Load a dump: util.loadDump()
●
Load a dump into a target database
– Support the import of schemas dumped using MySQL Shell's new instance dump utility and schema dump utility
into a MySQL instance or a MySQL Database Service DB System
– The dump loading utility provides data streaming from remote storage, parallel loading of tables or table chunks,
progress state tracking, resume and reset capability, and the option of concurrent loading while the dump is taking
place
Import into a MySQL Server instance or a MySQL Database Service DB System of schemas dumped
https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-utilities-load-dump.html

Is your MySQL server instance ready for upgrade?

Is your MySQL server instance ready for upgrade?
 Preliminary checks...
– Usage of old temporal type?
– Conflicting db object names and reserved keywords?
– Usage of utf8mb3 charset?
– Reserved tablenames in mysql schema?
– FK names longer than 64 chars?
– Usage of obsolete sql_mode?
– ENUM/SET column definitions containing elements longer than 255 characters?
– Usage of partitioned tables in shared tablespaces?
– Usage of removed functions?
– Usage of removed GROUP BY ASC/DESC?
– Issues reported by ”check table x for upgrade” command?
– ...
https://dev.mysql.com/doc/refman/8.0/en/upgrade-prerequisites.html

Upgrade Checker Utility
Credit: http://images.clipartpanda.com/superman-clipart-spiderman-logo-clip-art.jpg

MySQL Shell Upgrade Checker Utility - checkForServerUpgrade
 Utility from MySQL Shell (start with MySQL Shell 8.0.13)
– JS> util.checkForServerUpgrade()
 Will check your MySQL 5.7 or 8.0 installation readiness for upgrade
– Check for legacy issues
– Run the tool on the 5.7 before upgrading! - Users can make changes when time permits before the upgrade
– Always use latest version of MySQL Shell
 It is in active development and more checks will be added
 Privileges needed:
– Since 8.0.21: RELOAD, PROCESS & SELECT
https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-utilities-upgrade.html
Examples:
mysqlsh -- util check-for-server-upgrade { --user=root --host=172.25.0.10 }
mysqlsh -e "util.checkForServerUpgrade({user:'root', host:'172.25.0.10'})"
MYSQL JS> util.checkForServerUpgrade("root@172.25.0.10", {outputFormat:'JSON'})
Upgrade checker utility that enables you to verify whether MySQL server instances are ready for upgrade

Ready to Upgrade o/

Just one more thing…
34 Copyright © 2020, Oracle and/or its affiliates. All rights reserved.

Did I mention BACKUP?

In-place Upgrade

In-Place Upgrade
 An in-place upgrade involves:
– Shutting down the old MySQL server
– Replacing the old MySQL binaries or packages with the new ones
– Restarting MySQL on the existing data directory
– Upgrading any remaining parts of the existing installation that require upgrading
●
mysql_upgrade with MySQL versions <= 8.0.15
https://dev.mysql.com/doc/refman/8.0/en/upgrade-binary-package.html#upgrade-procedure-inplace

MySQL Upgrade – In-place Upgrade
1. Do all necessary preparations/plans/upgrade checker as explained earlier
●
e.g. mysqlsh -- util check-for-server-upgrade { --user=admin --host=172.25.0.10 }
2. Create a backup of your MySQL instance (data, logs, config files)
3. Do a graceful shutdown of MySQL (innodb_fast_shutdown=0)
4. Upgrade MySQL 8.0 - replace the old binaries with the new ones
5. Start the new MySQL 8.0 instance using the new binaries and the new my.cnf
6. Check messages in the error log
7. Verify that apps and services are working as expected

What you’ll see in the error log
 Example upgrade from 8.0.17 to 8.0.19
2019-10-15T12:44:14.308874Z mysqld_safe Logging to 'mysqld.err'.
2019-10-15T12:44:14.338620Z mysqld_safe Starting mysqld daemon with databases from data
2019-10-15T12:44:14.371936Z 0 [Warning] [MY-010139] [Server] Changed limits: max_open_files: 1024 (requested 8161)
2019-10-15T12:44:14.371948Z 0 [Warning] [MY-010142] [Server] Changed limits: table_open_cache: 431 (requested 4000)
2019-10-15T12:44:14.636779Z 0 [System] [MY-010116] [Server] mysqld (mysqld 8.0.18) starting as process 18741
2019-10-15T12:44:23.388628Z 4 [System] [MY-013381] [Server] Server upgrade from '80017' to '80018' started.
2019-10-15T12:44:39.925381Z 4 [System] [MY-013381] [Server] Server upgrade from '80017' to '80018' completed.
2019-10-15T12:44:40.153931Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2019-10-15T12:44:40.194680Z 0 [System] [MY-010931] [Server] mysqld: ready for connections. Version: '8.0.18' socket: '/tmp/mysql.sock' port:
3306 MySQL Server.
2019-10-15T12:44:40.422575Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/tmp/mysqlx.sock' bind-address: '::'
port: 33060
2019-10-15T12:45:06.909992Z 0 [System] [MY-010910] [Server] mysqld: Shutdown complete (mysqld 8.0.18) MySQL Server.
2020-01-14T11:09:48.878286Z mysqld_safe Logging to 'mysqld.err'.
2020-01-14T11:09:48.898560Z mysqld_safe Starting mysqld daemon with databases from data
2020-01-14T11:09:48.906717Z 0 [Warning] [MY-010139] [Server] Changed limits: max_open_files: 1024 (requested 8161)
2020-01-14T11:09:48.906726Z 0 [Warning] [MY-010142] [Server] Changed limits: table_open_cache: 431 (requested 4000)
2020-01-14T11:09:49.741917Z 0 [System] [MY-010116] [Server] mysqld (mysqld 8.0.19) starting as process 26998
2020-01-14T11:10:08.740404Z 4 [System] [MY-013381] [Server] Server upgrade from '80018' to '80019' started.
2020-01-14T11:10:49.289995Z 4 [System] [MY-013381] [Server] Server upgrade from '80018' to '80019' completed.
2020-01-14T11:10:50.147909Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-01-14T11:10:50.249474Z 0 [System] [MY-010931] [Server] mysqld: ready for connections. Version: '8.0.19' socket: '/tmp/mysql.sock' port:
3306 MySQL Server.
2020-01-14T11:10:50.384503Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/tmp/mysqlx.sock' bind-address: '::'
port: 33060

Logical Upgrade

Logical Upgrade
 A logical upgrade involves:
– Exporting SQL from the old MySQL instance using an utility such as
●
MySQL Shell Dump utilities : dumpInstance, dumpSchemas
●
mysqldump
●
mysqlpump
– Installing the new MySQL server
– Applying the SQL to your new MySQL instance
https://dev.mysql.com/doc/refman/8.0/en/upgrade-binary-package.html#upgrade-procedure-logical

MySQL Upgrade – Logical Upgrade
1. Do all necessary preparations/plans/upgrade checker as explained earlier
●
e.g. mysqlsh -- util check-for-server-upgrade { --user=admin --host=172.25.0.10 }
2. Create a dump of your MySQL instance (data, logs, config files)
●
Don’t forget your stored routines and your Event Scheduler events
3. Shutdown your MySQL Server
4. Do a clean installation of the new MySQL Server version - Initialize a new data directory
●
Copy the temporary 'root'@'localhost' password displayed to your screen or written to your error log for later use
5. Start the new MySQL 8.0 instance using the new binaries and the new my.cnf
6. Reset the root password
●
ALTER USER USER() IDENTIFIED BY 'new password';
7. Load the dump into the new MySQL server instance
8. Restart the MySQL Server with the --upgrade=FORCE option to perform the remaining upgrade tasks
9. Check messages in the error log
10.Verify that apps and services are working as expected

Troubleshooting

caching_sha2_password

 caching_sha2_password : new default Authentication plugin in 8.0
– Requires password exchange using a secure connection
●
TCP using TLS/SSL credentials,
●
a Unix socket file, or shared memory,
●
or an unencrypted connection that supports password exchange using an RSA key pair
– Then cached a copy of the password hash in memory
– MySQL 5.7 default is mysql_native_password
●
Relies on SHA1 algorithm and NIST has suggested to stop using it

 New users created in MySQL 8.0 will use the caching_sha2_password as their authentication plugin
– User accounts already created in existing instances are not altered as a part of an upgrade
Examples: Existing users who wish to switch to caching_sha2_password
ALTER USER 'daz'@'localhost' IDENTIFIED WITH caching_sha2_password BY '<password>';

caching_sha2_password - Troubleshooting
 If you encounter compatibility issues after upgrading to MySQL 8.0 the simplest way to address
those issues is to reconfigure the server to revert to the previous default authentication plugin,
mysql_native_password :
Example:
[mysqld]
default_authentication_plugin = mysql_native_password
 This setting should be viewed as temporary, not as a long term or permanent solution
 More details
– https://mysqlserverteam.com/mysql-8-0-4-new-default-authentication-plugin-caching_sha2_password/
– https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password

Keep in Mind

MySQL Upgrade – Keep in mind!
 Performance/Scalability monitoring and testing
– Consider MySQL Enterprise Monitor
– Monitor resource usage (iostat, top, vmstat etc)
 Do you need to consider rolling upgrade with MySQL Replication or InnoDB Cluster
– Primary: 5.7 → Replicas/Secondaries: 8.0
 Changes in default values
 Statements creating warnings/errors
 New optimizer features causing query plan changes
 Upgrade connectors as well
 Extensive TESTS and a controlled BACKUP / RESTORE process are your best insurance

MySQL Enterprise Monitor

MySQL Enterprise Monitor
 See a central view of the complete MySQL env
 Real-time MySQL performance and availability monitoring
 Visually find & fix problem queries with the Query Analyzer
 Alerts through email or text message
 Disk monitoring for capacity planning
 Replications monitoring
 Role based access controls
 Cloud friendly architecture
– No agents required
– Policy driven configuration
– Easy integration with DevOps tools
A DBA’s assistant: Visualize problems and tuning opportunities.

MySQL Enterprise Monitor – Query Analyzer
 Real-time query performance
 Visual correlation graphs
 Find & fix expensive queries
 Detailed query statistics
 Query Response Time index (QRTi)
– "Quality of Service" (QoS) measurement for each query
– QoS measurement for a server, group, or every instance
– Single metric for query performance
Visual Query Analysis
“With the MySQL Query Analyzer, we were able to identify and analyze problematic SQL
code, and triple our database performance. More importantly, we were able to accomplish
this in three days, rather than taking weeks.”
Keith Souhrada
Software Development Engineer
Big Fish Games

MySQL Enterprise Monitor – Best Practice Advisors
 Enforce MySQL best practices
 14 Advisor categories
 250+ Advisors
 Threshold-based alerts
– Exponential moving averages
– Rate change detection
 Expert problem resolution advice
Provide a set of rules designed to enforce MySQL best practices
“I definitely recommend the MySQL Enterprise Monitor to DBAs who don't have a ton of
MySQL experience. It makes monitoring MySQL security, performance and availability very
easy to understand and to act on.”
Sandi Barr
Sr. Software Engineer
Schneider Electric

Wrap-Up

MySQL Upgrade – Recap
 PREPARE your upgrade (release notes, resources)
 Preliminary CHECKS
– DO run the Upgrade Checker Utility : util.checkForServerUpgrade()
– Fix issues until it runs clean
 TEST your applications on MySQL 8.0
– Replication can help – Source : 5.7 → Secondary : 8.0
 DO your BACKUP
 UPGRADE to MySQL 8.0
 Post CHECKS
– logs, data consistency, performance, behavior of the application, ...

MySQL Enterprise Edition
https://youtu.be/CtRIc6Hsia8

Oracle Premier
Lifetime Support
Oracle Product
Certifications/IntegrationsMySQL Enterprise
High Availability
MySQL Enterprise
Security
MySQL Enterprise
Scalability
MySQL Enterprise
Backup
MySQL Enterprise
Monitor/Query Analyzer
MySQL Enterprise
Audit
Highest Levels of MySQL Security, Manageability and Reliability

Management ToolsAdvanced Features Support
• Authentication
• Audit
• Encryption / TDE
• Firewall
• Data Masking
• High Availability
• Monitoring
• Backup
• Development
• Administration
• Migration
• Technical Support
• Consultative Support
• Oracle Certifications
Highest Levels of MySQL Security, Manageability and Reliability

 MySQL Enterprise Authentication
– External Authentication Modules
●
Microsoft AD, Linux PAMs, Native LDAP
 MySQL Enterprise Encryption
– Public/Private Key Cryptography
– Asymmetric Encryption
– Digital Signatures, Data Validation
 MySQL Enterprise Firewall
– Block SQL Injection Attacks
– Intrusion Detection
 MySQL Enterprise Audit
– User Activity Auditing, Regulatory Compliance
 MySQL Enterprise Monitor
– Changes in Database Configurations, Users
Permissions, Database Schema, Passwords
 MySQL Enterprise Backup
– Securing Backups, AES 256 encryption
 MySQL Enterprise TDE
– AES 256 encryption
– Key Management
 MySQL Enterprise De-Identification
– Data Masking and Obfuscation
– Formatted Data Randomization
– Pseudonymization, Data Blacklists
– Random Data generation

MySQL Enterprise Support
 Largest MySQL engineering and support organization
 Backed by the MySQL developers
 World-class support, in 29 languages
 Hot fixes & maintenance releases
 24x7x365
 Unlimited incidents
 Consultative support
 Global scale and reach
Get immediate help for any
MySQL issue, plus expert
advice
Get immediate help for any
MySQL issue, plus expert
advice
https://www.mysql.com/fr/support/

MySQL Enterprise Consultative Support
 Remote troubleshooting
 Replication review
 Partitioning review
 Schema review
 Query review
 Performance tuning
 ...and more
https://www.mysql.com/fr/support/consultative.html
Make the Most of your Deployments

References 1/2
 https://dev.mysql.com/doc/refman/8.0/en/upgrading.html
 https://mysqlserverteam.com/inplace-upgrade-from-mysql-5-7-to-mysql-8-0/
 https://mysqlserverteam.com/upgrading-to-mysql-8-0-here-is-what-you-need-to-know/
 https://mysqlserverteam.com/upgrading-to-mysql-8-0-with-spatial-data/
 https://mysqlserverteam.com/upgrading-your-mysql-server-farm/
 https://mysqlserverteam.com/mysql-8-0-collations-migrating-from-older-collations/
 https://mysqlserverteam.com/new-defaults-in-mysql-8-0/
 https://mysqlserverteam.com/whats-new-in-mysql-8-0-generally-available/
 https://mysqlserverteam.com/the-complete-list-of-new-features-in-mysql-8-0/
 https://mysqlserverteam.com/mysql-shell-8-0-4-introducing-upgrade-checker-utility/
 https://mysqlserverteam.com/mysql-shell-dump-load-part-1-demo/
 https://mysqlserverteam.com/mysql-shell-dump-load-part-2-benchmarks/
 https://mysqlserverteam.com/mysql-shell-dump-load-part-3-load-dump/
 https://mysqlserverteam.com/mysql-shell-8-0-21-speeding-up-the-dump-process/

References 2/2
 MySQL Server Team Blog
http://mysqlserverteam.com/
 MySQL High Availability Blog
http://mysqlhighavailability.com/
 MySQL Release Engineering Blog
https://mysqlrelease.com/
 MySQL Dev Team Blog
https://insidemysql.com/
 MySQL Enterprise Team Blogs
https://blogs.oracle.com/mysql/
 Lefred’s blog
https://lefred.be/
 Dimitri’s blog
http://dimitrik.free.fr/blog/
 Andrew’s blog
https://thesubtlepath.com/blog/
 Olivier Dasini’s blog
http://dasini.net/blog/en
 Olivier's MySQL Channel
https://youtube.com/channel/UC12TulyJsJZHoCmby3Nm3WQ

Questions?

Thank you
Olivier Dasini
MySQL Principal Solutions Architect EMEA
Twitter : @freshdaz
Blog : http://dasini.net/blog/en

Upgrade from MySQL 5.7 to MySQL 8.0

Upgrade from MySQL 5.7 to MySQL 8.0

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Upgrade from MySQL 5.7 to MySQL 8.0

Similar to Upgrade from MySQL 5.7 to MySQL 8.0 (20)

More from Olivier DASINI

More from Olivier DASINI (20)

Recently uploaded

Recently uploaded (20)

Upgrade from MySQL 5.7 to MySQL 8.0