I need help with updating my MySQL database server. Right now my process is pretty messy and takes forever.
Currently I do this:
Make a full database backup
Remove the old MySQL version completely
Clean up leftover files manually
Install the new MySQL release
Import my backup using MySQL tools
The problem is I have to recreate all my database users and their permissions every single time. This is really annoying and time consuming.
I’m running a student registration application built with VB.Net that connects to MySQL. I can only do maintenance work after hours when students aren’t using the system.
Is there a smarter way to upgrade MySQL that keeps my user accounts and settings intact? I feel like I’m doing way more work than necessary.
You’re overcomplicating this. MySQL’s built-in upgrade utilities do the heavy lifting for you. Don’t remove the old version completely - install the new one alongside it, then run mysql_upgrade. This checks tables for compatibility issues and updates system tables automatically. Your user accounts and privileges stay intact. I did manual upgrades for months before figuring this out. Stop MySQL service, backup your data directory, install new version, restart service, run mysql_upgrade. Takes 30 minutes instead of hours, and you keep all user configs. Just test in staging first since you’re handling student data.
honestly, just do an in-place upgrade. back up your mysql data folder, install the newer version right over the existing one (don’t uninstall first), then run mysql_upgrade. it’ll fix everything automatically and keep all your users. way easier than what you’re doing now and saves a ton of time.
Your manual approach is exactly why I built automated workflows for database upgrades. Managing multiple production databases was eating up my entire weekends.
Game changer was setting up automated pipelines that handle everything without me babysitting it. Configure workflows that backup your data, validate integrity, run the MySQL upgrade, do post-upgrade checks, and rollback if things go sideways.
Best part? It triggers automatically during maintenance windows. No more staying up late running commands manually. The system handles user permissions, checks VB.Net connection compatibility, and emails you when it’s done.
I’ve seen teams go from 4-5 hour upgrades down to 30 minutes with zero manual steps. Your student registration system downtime becomes predictable and minimal.
For complex database stuff like this, Latenode makes building these workflows super simple without writing complex scripts. You can drag and drop components for backups, MySQL operations, and validation checks.
Try MySQL Workbench’s Server Upgrade feature if you haven’t yet. It handles everything through a GUI and automatically migrates schemas, user accounts, and permissions. I switched to this after dealing with similar production nightmares. The tool checks compatibility first and creates restore points automatically. For your VB.Net app, check if your connection string works with the new MySQL version - older connectors break with newer releases. I found this out the hard way upgrading from 5.7 to 8.0 when auth methods changed. Always test connections from your app server after upgrading, even if the database looks good.