Skip to content
Why Database Schema Changes Need Online Migration Not Downtime episode artwork

Jul 25, 2026 8 min

Why Database Schema Changes Need Online Migration Not Downtime

from Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations Hosted by Fexingo

Most teams still schedule maintenance windows to add a column or change a table schema, but in production databases with millions of rows, those windows can stretch into hours of downtime. This episode explains why online schema migration tools like gh-ost and pt-online-schema-change are the safer, faster alternative. Lucas walks through the trigger-based and binlog-based approaches, compares lock vs. non-blocking strategies, and breaks down a real case: how a mid-size e-commerce company cut a 4-hour migration to 15 minutes with row-based replication and asynchronous shadow tables. Luna asks the critical questions about rollback safety and performance impact during the copy phase. No clickbait, just the architecture behind zero-downtime schema changes. #DatabaseSchemaMigration #OnlineMigration #MySQL #ghost #ptOnlineSchemaChange #ZeroDowntime #DataMigration #DatabaseOperations #SQL #NoSQL #TechPodcast #DatabaseEngineer #ProductionDatabase #SchemaChange #TechTalk #FexingoBusiness #BusinessPodcast #DatabaseTech Keep every episode free: buymeacoffee.com/fexingo

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Why Database Schema Changes Need Online Migration Not Downtime

0:00 8:14

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

How long is this episode of Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations?

This episode is 8 minutes long.

When was this Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations episode published?

This episode was published on July 25, 2026.

Can I download this Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.