Handling name changes

How do you accommodate for name changes when designing a database? For
example in Northwind they store the Customer ID in the Orders table not the
customer name, which is what have always heard should be done, but my boss
tells me that a customer or patient, etc. can changer her/his name and you
still want to see past transaction reports with her/his name at the time the
transactions happened, for that you store the ID but also the name of the
customer in your Orders table. Is that the correct way to handle this kind
of situations? This seems like a very common scenario so there must be best
practices about how to handle the design of the tables and their
relationship. Could somebody post a brief description of table names, fields
and relationship to cover this scenario in the design correctly? I don't
remember seeing an explanation in any database book I have read.



Thanks,



Tim.


.

Relevant Pages

  • Re: Best way to do so.
    ... It's a design mistake to try and optimize storage. ... you maximum flexibility and ease in conducting ad-hoc querying etc. ... > customer itself? ... > but as what I see, I've about 50'000 search/month, and I don't store them ...
    (comp.lang.php)
  • Re: Database Design Problem
    ... Design is a hard thing to do if you want a good design that is. ... because of bad database design. ... There are lots of normalization rules ... and why I include the customer PO in the OrderDetails is because ...
    (microsoft.public.sqlserver.programming)
  • Re: .NET Framwork and VB
    ... Generally what you are doing in terms of distributed design methodology is ... Not quite sure why you divide the database operations into ... For example, if I want to write a Cusomter business component, do I ... CustomerSingleSelect - a calss which gets data from customer based on ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: JDO or O/R Mapper ?
    ... >> Only in rare cases do I need persistance of an object that is part of an ... >> I often need a well designed relational database and an evenly well ... They do not design an archtitecture but start with selecting tools: ... If I need a customer to be accessed as a "record" a SELECT of the ...
    (comp.lang.java.databases)
  • Re: JDO or O/R Mapper ?
    ... >> Only in rare cases do I need persistance of an object that is part of an ... >> I often need a well designed relational database and an evenly well ... They do not design an archtitecture but start with selecting tools: ... If I need a customer to be accessed as a "record" a SELECT of the ...
    (comp.lang.java.programmer)