Adding a new column is one of the most common operations in database management, but it carries real consequences. Done right, it extends your schema without breaking queries. Done wrong, it can lock tables, slow writes, or corrupt data integrity.
A new column changes the shape of your data. Plan for it before touching ALTER TABLE. Ask: will it store nullable values? Will you add a default? Will constraints apply? These choices decide whether migrations are painless or painful.
For SQL databases, use ALTER TABLE table_name ADD COLUMN column_name data_type;. Test this in a staging environment. Measure performance before and after. For large datasets, consider adding the column without a default, then backfill in controlled batches.
In NoSQL systems, adding a field is often schema-less in theory but not in practice. You still manage compatibility in application code. Backfill where needed. Avoid hidden null checks that slow down queries.