Deprecated: Function Yoast\WP\SEO\Conditionals\Schema_Blocks_Conditional::get_feature_flag is deprecated since version Yoast SEO 20.5 with no alternative available. in /home1/minerho3/public_html/wp-includes/functions.php on line 6078

Deprecated: Function Yoast\WP\SEO\Conditionals\Schema_Blocks_Conditional::get_feature_flag is deprecated since version Yoast SEO 20.5 with no alternative available. in /home1/minerho3/public_html/wp-includes/functions.php on line 6078

Deprecated: Function Yoast\WP\SEO\Conditionals\Schema_Blocks_Conditional::get_feature_flag is deprecated since version Yoast SEO 20.5 with no alternative available. in /home1/minerho3/public_html/wp-includes/functions.php on line 6078

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/minerho3/public_html/wp-includes/functions.php:6078) in /home1/minerho3/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831
{"id":1688,"date":"2018-06-19T13:50:22","date_gmt":"2018-06-19T13:50:22","guid":{"rendered":"http:\/\/minervadb.com\/?p=1688"},"modified":"2018-06-27T10:35:46","modified_gmt":"2018-06-27T10:35:46","slug":"mysql-5-7-to-mysql-8-upgrade","status":"publish","type":"post","link":"https:\/\/minervadb.com\/index.php\/2018\/06\/19\/mysql-5-7-to-mysql-8-upgrade\/","title":{"rendered":"Using MySQL Shell 8.0.11 “upgrade checker” to upgrade from MySQL 5.7 to MySQL 8.0 successfully"},"content":{"rendered":"

We are really excited about MySQL 8.0 new features (https:\/\/dev.mysql.com\/doc\/refman\/8.0\/en\/mysql-nutshell.html<\/a>) and our consultants spend several hours weekly, testing new features and doing research on how best we can create value for our customers from having those in production. Being an pure-play MySQL consulting, support and remote DBA services company, We are fully accountable for our customer database infrastructure operations performance, scalability, high availability and reliability. \u00a0As we are aggressive about gaining maximum results from MySQL 8 investments made by our customers, We are equally conservative (our customer data reliability is critical for us !) \u00a0on adopting new features, until we are fully confident after several rounds of testing (at different scales on multiple platforms) and technical review (we engage both internal and external consultants for acceptance) and acceptance before deployment in production infrastructure. In the previous versions of MySQL, before every upgrade our consultants manually spend several hours testing compatibility but MySQL 8 made this simple by introducing “upgrade checker” javascript with MySQL Shell 8.0.11 , In this blog we are writing about “upgrade checker” utility and upgrade from MySQL 5.7 to MySQL 8.0 .<\/p>\n

Using MySQL Shell 8.0.11 “upgrade checker<\/strong>”<\/p>\n

Typical “upgrade checker<\/strong>”\u00a0run will look similar to this:<\/p>\n

 MySQL  JS >  util.checkForServerUpgrade(\"root@localhost:3306\")\r\nPlease provide the password for 'root@localhost:3306': **********\r\nThe MySQL server at localhost:3306 will now be checked for compatibility issues for upgrade to MySQL 8.0...\r\nMySQL version: 5.7.22-log - MySQL Community Server (GPL)\r\n\r\n1) Usage of db objects with names conflicting with reserved keywords in 8.0\r\n  No issues found\r\n\r\n2) Usage of utf8mb3 charset\r\n  Warning: The following objects use the utf8mb3 character set. It is recommended to convert them to use utf8mb4 instead, for improved Unicode support.\r\n\r\n  sakila.actor.first_name - column's default character set: utf8\r\n  sakila.actor.last_name - column's default character set: utf8\r\n  sakila.actor_info.first_name - column's default character set: utf8\r\n  sakila.actor_info.last_name - column's default character set: utf8\r\n  sakila.actor_info.film_info - column's default character set: utf8\r\n  sakila.address.address - column's default character set: utf8\r\n  sakila.address.address2 - column's default character set: utf8\r\n  sakila.address.district - column's default character set: utf8\r\n  sakila.address.postal_code - column's default character set: utf8\r\n  sakila.address.phone - column's default character set: utf8\r\n  sakila.category.name - column's default character set: utf8\r\n  sakila.city.city - column's default character set: utf8\r\n  sakila.country.country - column's default character set: utf8\r\n  sakila.customer.first_name - column's default character set: utf8\r\n  sakila.customer.last_name - column's default character set: utf8\r\n  sakila.customer.email - column's default character set: utf8\r\n  sakila.customer_list.name - column's default character set: utf8\r\n  sakila.customer_list.address - column's default character set: utf8\r\n  sakila.customer_list.zip code - column's default character set: utf8\r\n  sakila.customer_list.phone - column's default character set: utf8\r\n  sakila.customer_list.city - column's default character set: utf8\r\n  sakila.customer_list.country - column's default character set: utf8\r\n  sakila.customer_list.notes - column's default character set: utf8\r\n  sakila.film.title - column's default character set: utf8\r\n  sakila.film.description - column's default character set: utf8\r\n  sakila.film.rating - column's default character set: utf8\r\n  sakila.film.special_features - column's default character set: utf8\r\n  sakila.film_list.title - column's default character set: utf8\r\n  sakila.film_list.description - column's default character set: utf8\r\n  sakila.film_list.category - column's default character set: utf8\r\n  sakila.film_list.rating - column's default character set: utf8\r\n  sakila.film_list.actors - column's default character set: utf8\r\n  sakila.film_text.title - column's default character set: utf8\r\n  sakila.film_text.description - column's default character set: utf8\r\n  sakila.language.name - column's default character set: utf8\r\n  sakila.nicer_but_slower_film_list.title - column's default character set: utf8\r\n  sakila.nicer_but_slower_film_list.description - column's default character set: utf8\r\n  sakila.nicer_but_slower_film_list.category - column's default character set: utf8\r\n  sakila.nicer_but_slower_film_list.rating - column's default character set: utf8\r\n  sakila.nicer_but_slower_film_list.actors - column's default character set: utf8\r\n  sakila.sales_by_film_category.category - column's default character set: utf8\r\n  sakila.sales_by_store.store - column's default character set: utf8\r\n  sakila.sales_by_store.manager - column's default character set: utf8\r\n  sakila.staff.first_name - column's default character set: utf8\r\n  sakila.staff.last_name - column's default character set: utf8\r\n  sakila.staff.email - column's default character set: utf8\r\n  sakila.staff.username - column's default character set: utf8\r\n  sakila.staff.password - column's default character set: utf8\r\n  sakila.staff_list.name - column's default character set: utf8\r\n  sakila.staff_list.address - column's default character set: utf8\r\n  sakila.staff_list.zip code - column's default character set: utf8\r\n  sakila.staff_list.phone - column's default character set: utf8\r\n  sakila.staff_list.city - column's default character set: utf8\r\n  sakila.staff_list.country - column's default character set: utf8\r\n\r\n3) Usage of use ZEROFILL\/display length type attributes\r\n  Notice: The following table columns specify a ZEROFILL\/display length attributes. Please be aware that they will be ignored in MySQL 8.0\r\n\r\n  sakila.customer.active - tinyint(1)\r\n  sakila.staff.active - tinyint(1)\r\n\r\n4) Issues reported by 'check table x for upgrade' command\r\n  No issues found\r\n\r\n5) Table names in the mysql schema conflicting with new tables in 8.0\r\n  No issues found\r\n\r\n6) Usage of old temporal type\r\n  No issues found\r\n\r\n7) Foreign key constraint names longer than 64 characters\r\n  No issues found\r\n\r\n8) Usage of obsolete MAXDB sql_mode flag\r\n  No issues found\r\n\r\n9) Usage of obsolete sql_mode flags\r\n  No issues found\r\n\r\n10) Usage of partitioned tables in shared tablespaces\r\n  No issues found\r\n\r\n11) Usage of removed functions\r\n  No issues found\r\n\r\nNo fatal errors were found that would prevent a MySQL 8 upgrade, but some potential issues were detected. Please ensure that the reported issues are not significant before upgrading.\r\n1\r\n<\/pre>\n

At the end, \u00a0“upgrade checker<\/strong>” prints a summary and returns an integer value describing he severity of the issues found:<\/p>\n