maxmangion
AWF VIP
- Local time
- Today, 23:43
- Joined
- Feb 26, 2003
- Messages
- 2,805
Hi,
I am creating my main table of a database, and while i am planning the setup i am noticing that some of the fields are going to change often ... now i remember myself reading somewhere that ideally fields which have their data changed often should be created in a different table, and not within the table which the other fields data will remain somewhat static.
My question is this: since i am not interested to keep track of the previous values in these fields in a history table, is it ok if i bend the rules of normalization and go with creating the frequently changed and the fairly static fields all in the same table since they are all related the item?
Thanks
I am creating my main table of a database, and while i am planning the setup i am noticing that some of the fields are going to change often ... now i remember myself reading somewhere that ideally fields which have their data changed often should be created in a different table, and not within the table which the other fields data will remain somewhat static.
My question is this: since i am not interested to keep track of the previous values in these fields in a history table, is it ok if i bend the rules of normalization and go with creating the frequently changed and the fairly static fields all in the same table since they are all related the item?
Thanks