MySQL 8: Successful upgrade of millions of databases, and unmatched customer experience
Table of Contents
We are happy to announce that we’ve successfully upgraded our servers to MySQL 8, and that roughly 3 million databases are now using it at full steam. More importantly, this massive transition required zero effort on the behalf of webmasters and site owners! Our unique approach to this task allowed us to provide customers with all the benefits of the newest MySQL version, and at the same time mitigate the high risk of updating such a vital underlying website technology.
While many web hosts would change their MySQL version and let customers deal with the consequences, that just doesn’t align with our values. We took it upon ourselves to bring the benefits of MySQL 8 to all our clients, and prepared extensively in order to make the adoption painless and risk-free for them. That meant testing and evaluating seemingly countless application configurations (Joomla, Drupal, WordPress and other CMSs, and all their extensions and themes that come in different setups) to foresee the tons of possible post-upgrade problems – and then eliminate them proactively and swiftly without any work or hassle for the clients.
Let’s dive into how we made that happen.
The Challenge: MySQL8 upgrade is risky and creates heavy workload for the website owners and webmasters
Upgrading a website’s MySQL is always risky: these big version updates bring with them truly innovative features, but it also means that existing applications and web setups may not be compatible. Because of that, it usually takes years until they get largely adopted. For example, the first version of MySQL 8 premiered in 2018 and a year after its release it only had a 17% global adoption rate.
The decision about if and when to switch to a newer MySQL version requires the webmaster to weigh potential problems that might occur against the benefits it brings, and invest time and money in fixing post-upgrade problems. This creates a huge burden for website owners and webmasters.
That’s where web hosting companies might be of huge help – or not – depending on how they manage their servers and the level of service they provide to their customers. Among our competitors there are two popular approaches to such large-scale upgrades: either enable the new MySQL version on only the new servers you launch, and if current clients want the new version they need to relocate to the new servers; or put both the old and new MySQL’s on one server, which would increase the resource usage of the server and might ultimately deteriorate the performance of the sites hosted on it.
Neither of these options is ideal though. In both cases, the burden of risk still falls on the website owner or webmaster, as they would need to do the work to make their sites compatible with the new MySQL. The likely outcome is that many would just not upgrade, thus missing out on performance, security and other benefits. What’s worse, many clients would continue using an older version of MySQL for so long that it would become vulnerable and unsupported by the official developers. This would put their websites at serious risk. Not a great plan.
SiteGround’s unique approach: millions of databases automatically updated to MySQL8 without hassle for the clients
At SiteGround our philosophy is to ensure that all our customers can benefit from the latest technologies, and with the least possible hassle: no work, no risk, no extra investment, just take it out of the box and use it. When we offer a new software like MySQL 8 that comes with multiple benefits, we make sure all clients can safely and easily enjoy it.
This is why our approach to this upgrade was different. We didn’t leave it to our clients to figure out how to upgrade to MySQL8; we did it for them and took on all the work to eliminate incompatibilities and resolve post-upgrade problems. That upgrade process included evaluating the level of risk, researching all possible incompatibilities and upgrade errors, automatically fixing problems, and manually verifying the results. As a result, millions of sites are now using MySQL 8 without any extra headaches.
Extensive research and multiple dry runs to reduce upgrade fail rate
We began by extensively researching the incompatibilities of MySQL 5.7 (the previously used version of MySQL). The goal was to discover which issues could act as potential blockers to updating a database to MySQL 8.
Next, we copied and isolated hundreds of servers and started dry-run upgrades. The objective was to identify problematic software and setups that break after the transition, find solutions for them in advance, and document all results carefully. We used all that data to minimize the upgrade fail rate and to automate the aftermath problem resolution.
Automated and quick fixes of broken sites
Building on the extensive research and testing, our engineers developed a smart system that essentially served as a skilled mechanic for your website. It would run a compatibility check with MySQL 8 based on your specific application configuration and database structure. If it detected incompatibilities, it would patch them on the spot.
As a result, after the upgrade this automatic system helped us to immediately remove errors and broken queries for thousands of websites, and it spared us tons of manual work, in addition to resolution wait time for the clients.
Manual fix of 7518 websites by our experts (free of charge for the clients)
The automated checks did a tremendous job, but we went even further. After a server was upgraded, our technicians would open pretty much all websites hosted on it to make sure they were fully functional. Of those, they identified 7518 websites with issues, which they then fixed manually after the migration in due time.
804 sites provided with a time extension (at our expense)
All our automated and manual checks left us with an impressively low number of sites that remained incompatible with the new MySQL version — below 0.001% of all. For these clients we provided a custom server setup where they would be able to use MySQL 5.7 for two additional months allowing them enough time to address significant query incompatibilities and to get ready for the new version. We believe each of our users should be given the option to receive the best service, so at this time we’ve absorbed the cost of maintaining the old version on additional servers.
Efficient server upgrade schedule paid off in fast problem resolution
One of the internal challenges during the process was to schedule the servers for upgrade so that we would have had enough people to not only address potential issues, but also complete the upgrade successfully in the shortest possible time frame. Based on our statistics from the dry runs, we could predict how many websites would have had issues per server, and therefore knew how many servers to schedule and how many technicians to staff so that we could address problems quickly. At some point, our process was so efficient that it allowed us to successfully upgrade as many as 180,000 websites in 24 hours!
Timely and honest communication with customers
Those of you who’ve been customers for a while surely already know how much we value transparent and clear communication when it comes to events that impact your websites. This upgrade to MySQL8 was no exception. We notified each client at least seven days prior to the transition, informing them of the day and hours we would upgrade their websites (always non-business hours for their respective region).
The Summary
Our top priority in this upgrade process was that all sites would be fully functional as usual after the upgrade – no problems, just benefits from the newer MySQL. The outcome? We had a 99.99%+ success rate of the migration process!
- With solid planning, preparation and precise execution, we successfully upgraded roughly 3 million databases and made them fully compatible with MySQL 8 without any work for our clients.
- It took us only 63 migration days to achieve this for all websites hosted on our platform, totally free of charge, all while making sure that every single client website had been thoroughly taken care of. Well, let’s not forget the month or two we invested in preparation work,including research, dry runs, and automations.
- A special team of 34 people worked for a total of 1228 hours on the actual upgrade, completing the process with utmost efficiency and professionalism – it took them an average of seven minutes per server to switch and resolve issues.
It was an enormous task on a staggering scale, especially considering the high bar we set for ourselves. But in the end all the hard work on our part paid off in absolutely no work for our clients. And that in itself, for us, is the end goal that justifies all the effort.
Comments ( 14 )
Thanks! Your comment will be held for moderation and will be shortly published, if it is related to this blog article. Comments for support inquiries or issues will not be published, if you have such please report it through
Louis Dallara Photography
So why do I see this on my site? It's not updated. My account "Web server" Apache Database client version: libmysql - mysqlnd 7.4.33 PHP extension: mysqli Documentation curl Documentation mbstring Documentation PHP version: 7.4.33
Lina Asenova Siteground Team
Hey there, the information you’re seeing is related to libmysql, which differs from the actual MySQL server version. We can confirm that your website and the server it's hosted on were successfully updated to MySQL 8 on April 29th. To verify the current version for your website, go to Site Tools > Site > MySQL > phpMyAdmin > Access phpMyAdmin. Under the Database Server section on the right side, find Server Version where the MySQL version is listed. If you have any further questions or concerns, please reach out directly to our support team. They will be more than happy to assist you with any inquiry. Here are the steps to contact us: https://stgrnd.co/contactus.
Louis Dallara
Thank you for the excellent explanation.
Lina Asenova Siteground Team
You're most welcome! :)
Zoltan
Thank You, well done!
Lina Asenova Siteground Team
Thank you for the kind words! :)
Fungai
All my sites have been down since the upgrade.
Lina Asenova Siteground Team
Thank you for reaching out, Fungai. We understand how frustrating website downtime can be. We've located your account and noticed that you have already contacted our support team. It looks like the issue was related to insufficient disk space, which prevented MySQL from starting properly. Our administrators have freed up some space, restoring normal operations, and your websites are now up and running. If you encounter any other issues or have any questions, don't hesitate to reach out to our support team. We're always here whenever you need us.
Kevin
Is there an EOL for PHP 7.4.33 on Siteground? I know you have previously stated that PHP 7.3 will be removed in 2025, but I haven't seen mention of 7.4?
Mila Kanazirska Siteground Team
At this time, there is no EOL date for PHP 7.4. If you choose to use this version, it will be set as the default Manual PHP version. You can select this option from your Site Tools Panel by navigating to PHP Manager. Should you have any further questions or need assistance, please feel free to contact our support team anytime.
John lee, Wagin Camara Club
Would this have anything to do with my error log showing the word deprecated, am unable to do any editing due to http error 500
Ivan Naidenov Siteground Team
Hey there! The warnings in your error log and the HTTP 500 error you're experiencing could be related, but it's difficult to say for certain without more information. These issues can have various causes, ranging from plugin conflicts to server configuration problems. To determine the exact cause and resolve the issue, it would be best to contact our support team directly by following these steps: https://stgrnd.co/contactus Our team will be able to investigate the error and guide you through resolving it. We look forward to hearing from you!
STB
That's a great read, and thankyou for the effort taken. Architecture stuff is such a hassle, so massively appreciated not having to deal with it too deeply. I had a sinlge minor issue with a particular date format in some contexts. Realising how much worse this upgrade could have been..
Lina Asenova Siteground Team
Thank you so much for the kind words! We're glad our content helped simplify things, especially with the complexities of architecture. If you ever need assistance or run into any issues, don't hesitate to reach out. We're always here to help!
Start discussion
Thanks! Your comment will be held for moderation and will be shortly published, if it is related to this blog article. Comments for support inquiries or issues will not be published, if you have such please report it through