In January, ConnectWise announced they are ending support for MySQL 5.7 in Automate. In this blog, we’ll explore what that means and what actions MSPs need to take.
Already End-of-Life
You might be aware that MySQL 5.7 reached end-of-life in October 2023. It stopped receiving security updates, and for security and insurance/compliance reasons, your MySQL instance for ConnectWise Automate should have been upgraded from MySQL 5.7 a couple of years ago. At this point, MySQL 5.7 has known vulnerabilities, and any MSP that is behind on patching should upgrade to the latest version of MySQL 8.0 immediately.
Tailing ConnectWise support for MySQL 5.7
If MySQL 5.7 is already EoL, why is ConnectWise support for it ending now? Well, it’s a blend of tradition and some support and development logistics.
ConnectWise previously announced that support for MySQL 5.5 would be removed in patch 2021.12, released in December 2021. That was actually 3 years after the end-of-life date for MySQL 5.5, which was December 21st, 2018. The announcement came after patch 2021.10, which added support for MySQL 8.0. This points to a trend in which support for older versions is removed as support for newer versions is added.
There are also architectural changes between different versions of MySQL. Things like character encodings, timestamp formats, and connection parameters change over time. Likewise, internal architecture (memory buffers, logging processes, etc.) gets enhanced over time – and all of these things should factor into how software interacts with its database. Additionally, some of these items (such as connection parameters) require software changes, and each database version requires separate application-layer logic for these differences. Eventually, it becomes logical to deprecate older MySQL versions to reduce complexity in development and support.
Upgrading to MySQL 8.0
Currently, MySQL 8.0 is the supported MySQL version for ConnectWise Automate that is still receiving patches. It’s an LTS version of MySQL, and Automate has been stable on MySQL 8.0 since March of 2022 (a connection pool bug was introduced when MySQL 8.0 support was first added, and took several months to resolve).
The jump from MySQL 5.7 to 8.0 is significant. We’ve written blog posts about the upgrade process, which are worth reading if you’re facing an upgrade.
Here at Automation Theory, we advise against the documented process in ConnectWise University for MySQL upgrades. That documentation walks through a “dump and reload” method, which Oracle recommends only in the event of corruption. That process takes hours, is somewhat convoluted, and hasn’t been updated to reflect advancements in MySQL (for example, there are better ways to dump and reload a database if needed).
We recommend in-place upgrades, which are Oracle’s preferred method. The process takes about an hour (barring any troubleshooting from common upgrade snags) and doesn’t require slicing and dicing the database into multiple pieces.
We also suggest upgrading the MySQL connectors to the latest versions. The connectors get security and performance updates quarterly, just like MySQL. The versions are numbered differently, but the latest ODBC and .NET connectors are generally compatible with Automate, and downgrading in the future for troubleshooting can be done quickly if needed.
Support for MySQL 8.4 is on the way
There’s one problem with MySQL 8.0: support for it ends in April 2026. MySQL 8.4 is the next LTS version of MySQL. This has important implications across several realms.
First, any MSP wanting to maintain a good security posture will want to upgrade to a supported version. Installing security updates is part of good cyber hygiene, and MySQL 8.4 includes enhancements that will benefit any MSP running ConnectWise Automate (the defaults are ~50x faster than MySQL 8.0).
Second, most MSP insurance policies exclude end-of-life software and software with known vulnerabilities from coverage. By May 2026, MySQL 8.0 will be end of life, and the next quarterly security release will be in July 2026, which would then make the software known to be vulnerable. Upgrading MySQL would prevent any insurance coverage issues.
Finally, upgrading ensures compliance with security frameworks and vulnerability management policies. For any MSP operating under a compliance framework (ISO 27001, SOC 2, etc.), addressing EoL software versions will be required.
ConnectWise has updated their documentation to indicate that support for MySQL 8.4 is planned.
MySQL Upgrade assistance
Upgrading MySQL isn’t as easy as some would think – and there are several considerations. Here at Automation Theory, we offer MySQL Maintenance Packages for MSPs running ConnectWise Automate. We provide performance tuning, configuration optimization, and ongoing patching and maintenance.
This offering is designed for busy MSPs who want to ensure MySQL is secure and optimized on an ongoing basis. The entire process is structured around the needs of MSPs. Our team monitors MySQL releases, tests the latest patches, and coordinates after-hours upgrade windows. You can find more details about our maintenance package offerings here.
