I’m curious how others deal with this workflow.
In my job we have many SQL Server instances with multiple environments (dev/test/prod copies). Almost every day we need to update database structures or run batches of scripts across dozens of databases on several servers.

Doing it manually in SSMS was slow and error‑prone, so a few years ago I built an internal tool to speed things up. It lets us load servers, fetch databases, select targets, run scripts in sequence or in parallel, see per‑database success/failure, timeline, dry‑run, etc.

I’m not linking anything here — I’m more interested in the concept than promoting a tool.

My questions to you:

• How do you handle multi‑server / multi‑database updates?
• Do you use custom tools, SSMS, scripts, CI/CD, something else?
• Would features like parallel execution, dry‑run, or execution timeline be useful in your workflow?
• What would be a “must have” vs “nice to have”?

I’d like to understand how others approach this problem and what matters most in real‑world scenarios.