---
answer: direct
beat: dev-practices
source: 1 article · updated: November 14, 2026
---

What commonly breaks in a MySQL 5.7 to 8.0 upgrade?

Query plans that change and slow some queries, stricter SQL modes rejecting sloppy statements, the default collation changing from utf8mb4_unicode_520_ci to utf8mb4_0900_ai_ci, and old client libraries that cannot authenticate or speak the new protocol. All four can be found before cutover with the right tests.

Answered in

Upgrading a Database Major Version Without Downtime: The Side-by-Side Replica Playbook

Add new-version replicas, soak them on real reads, promote, then clean up. The four stages, the point of no return, and the MySQL 5.7 to 8.0 gotchas.

Crashtech Editorial November 14, 2026 Development Best Practices

Read the full analysis

Other questions this article answers

More development best practices questions

Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.