padlocked17
Registered User.
- Local time
- Yesterday, 19:40
- Joined
- Aug 29, 2007
- Messages
- 276
Good Afternoon,
I've got a DB that will require importing JSON and CSV data on a recurring basis. I will need to deal with additions, deletions, and modifications to the data every time I import it to make decisions based on how the currently imported data is being used.
Is is a better practice to keep the data that is imported completely separate via tables in the DB design or merge the data with my current structure and simply have a Key or UID that identifies the record as being from an imported source so that I can deal with changes every time I import and reconcile differences?
I've got a DB that will require importing JSON and CSV data on a recurring basis. I will need to deal with additions, deletions, and modifications to the data every time I import it to make decisions based on how the currently imported data is being used.
Is is a better practice to keep the data that is imported completely separate via tables in the DB design or merge the data with my current structure and simply have a Key or UID that identifies the record as being from an imported source so that I can deal with changes every time I import and reconcile differences?