Rollbacks, Red Eyes And Unreliable Deployments
This series is about the stress of database deployments on the people behind them, and the small, steady changes that help relieve it. – Felicity Questier, Redgate Software.
We spoke to data professionals from a range of industries about the impact of unreliable database deployments — not just on their systems, but on their workload, time, and well-being. From delayed releases to weekend firefighting, and the fallout for teams and customers, they share the day-to-day pressures they face and the small changes that help make deployments, and life, a little less stressful.
What stood out from these conversations? They reveal how fragile deployments affect not just software but the people and teams behind it — often driving stress, burnout, and blame. But they also show how better processes and steady improvements can build a culture where success no longer relies on heroic late-night fixes.
Get the next stories straight to your inbox. This is just the first batch — sign up for the Redgate Update and we’ll send them as soon as they’re published. You’ll also get industry news, Redgate announcements, event invites, and more.
Click on each ambassador’s story below to read more.
 Adam Hafner
Senior Database Engineer, Interstates
“When one failed deployment can cost thousands, testing is what lets you sleep at night.”
|
 Ryan Hird
Technical Lead, Bennetts
“We used to do out-of-hours releases, but no one does their best work at 2 am…”
|
 Thomas Rushton
Principal Data Platform Engineer, Coeo
“Learn the lesson from every failed deployment, and over time, the stress will ease.”
|
 Tracy Boggiano
Senior SQL Developer, Abarca Health
“I’m always worried I’ll miss something. In healthcare, you can’t afford mistakes.”
|
You may also like
Blog
The best decisions are never made at 2 AM…
Blog