Clear all

How to model derived/summary tables from source system

Posts: 8
Topic starter
Active Member
Joined: 2 years ago

I have a question about the best way to model derived summary tables from a source. An example would be a billing summary table. This is an aggregate table that is generated by the ERP source application. It is not a transactional table, it is derived. My first thought was to treat it like a Non-Historized link, but it is possible that some fields such as dates and status could change. On the other hand I don't need to track history, that can be done using the transactional tables. Does it make sense to structure it as a Non-Historized link with no satellite and do a truncate and load? I could keep the source loads in the data lake for historical purposes...

Thanks in advance!

4 Replies