Jeff Looks like loading to same table seems easier as per your email. Is it possible to partition existing table add data? Karth Sent from my IPhone > On Jun 9, 2014, at 7:21 PM, Jeff C <backseatdba@xxxxxxxxx> wrote: > > I have a data warehouse that loads data from a Point of Sale (POS) system > with data going back 8 years. Basically each button pressed is a row. Well > now the POS is changing to where orders are taken differently. I have made it > so the data load format to the DW is the same but how some rows relate to > each other have different meanings. As well as different item numbers for the > same product between old and new. I plan on grouping them through a lookup > table. > Now my question is do I load this new data in the existing table or is it > better to make a new table for this newer design? I have some applications > where it doesn't matter how the data is, queries will still work. This makes > it easy if I load to the existing table, if I don't then I will have to add a > bunch of Union queries or create some kind of Materialized View. If it is > two tables then it will be easier to distinguish the two and if we have very > specific queries we know how each data set will behave. > > If anybody has experience with a problem like this I would love to here your > experiences. > > Thank you -- //www.freelists.org/webpage/oracle-l