database normalization - Audit columns - join or copy? -

database normalization - Audit columns - join or copy? -

i have seen many business systems not using joins on users table instead copying user name (or firstname+lastname) createdby audit field.

i see 1 issue approach - user might marry , alter lastly name, , createdby field maintain old value.

is there reason why draw info normalization , create redundant text info createdby field?

storing someone's name without using foreign key reference lets delete users without affecting info rows created. whether wise application-dependent.

in organizations, if it's of import know someone's name 3 years ago, there's way it. might not in database. might be, "go inquire jerry in hr. remembers everyone." whether this wise application-dependent.

in case, doesn't violate guidelines of normalization. in 1 case, you're storing current name or preferred name of user. in other case, you're storing name of user @ time row created, , still constitutes true fact.

audit database-normalization