A normalized database will have no transient dependencies among its fields and will uniquely identify types of entities in an organization.

The result is that each table is about one thing and one thing only.

The result is that each table is about one thing and one thing only, unless a field must be created for tertiary tables

The result is that each table is about one thing and one thing only, unless it appropriately identifies a many$-$tomany relationship

$$ The result is that each table is about one thing and one thing only when a secondary table has been created