RE: Is Redundant Data Ok?
From: Nigel Rivett (sqlnr_at_hotmail.com)
Date: Sat, 6 Nov 2004 16:10:02 -0800
You have some choices.
You can keep all versions of membership data and have an active flag or a
start/end date on it. In that way the winner data will always be available.
When a member wins then take a copy of the data and save it in the members
table for the winners table to link to.
when a member wins flag the entry as being linked from the winners table -
any changes made then create another version of the entry.
Have an audit trail on the memberst table so that the winners table can
always link to a version of the data.
Reall up to you - think I wouldn't hold the data in the winners table but
maybe another version of the members table so that can have mutiple winner
entries linking to the same members entry.
> I have two tables one name members and the other name winners. The members
> table hold such information as FirstName, LastName, Email, etc., and the
> winner table hold such information as FirstName, LastName, Email, Prize,
> Address, City, etc. However, as you can see these two table holds pretty
> much the same data, but they are used for two different purposes. The member
> table is use for member registration in which the member can edit there
> personal information on the fly, a member can also be deleted from the
> member table, but the winner table is use for member that have won a prize
> in which winners can never be deleted from this table, information can never
> be edit, the winner table mainly keep a lifelong track second of all past
> and present members ("even if they no longer have a record in the member
> Is it ok to have redundant data in my database in this situation? and is
> this situation pretty common in database design?