The table was empty except for the data that mattered. You needed a new column, and you needed it fast. No long deployments. No waiting for migrations to finish while your users sat idle. Just a direct change in the schema, live, without breaking production.
A new column is one of the most common changes in any database. It should be simple. In practice, adding a column often triggers a chain of friction: schema migrations, locks, and downtime risks. On large datasets, a new column can stall writes, backlog jobs, and frustrate release cycles. Engineers have learned to fear what should be routine.
Modern tooling makes it possible to define a new column without blocking the database. Online schema changes let you add columns safely, even under heavy load. You can set default values, define nullability, and apply constraints without freezing queries. Done right, a new column is just a metadata update followed by a background fill.