A new column is more than storage. It is a new dimension in data. It reshapes indexes. It changes query plans. It can remove joins or create them. When you add a column, you alter the contract between your application and its database.
In relational systems, a new column needs precision. Define its data type with purpose. Choose nullable or not with intent. Understand the cost of default values. In NoSQL systems, a new column—often called a field—can be added without migrations, but it still impacts reads, writes, and storage.
Performance depends on how you introduce the column. Adding to a small table is trivial. Adding to a table with millions of rows can lock writes, trigger long-running alterations, or demand online schema changes. MySQL, Postgres, and modern cloud databases each handle column creation differently. Know your engine’s capabilities before executing.