Clear all

Best practice for modeling Satellites - Mutable Vs Immutable

Posts: 5
Topic starter
Joined: 2 years ago

I have a question on best practices when modeling Satellites .

My understanding so far with DV 2.0 is that Satellites hold descriptive data and are mutable.

To accommodate aforementioned mutability, Satellites  have Load Date Time Stamp as a part of its primary key. So from implementation standpoint, if there is a delta on existing row, delta is inserted as new row with new Load Date Time Stamp. 

What is the best practice to handle the existing row ?

a) Expire by populating  a value in Load End Date ?


b) To leave existing row as is and let the downstream applications make the determination of identifying latest row which in this case would be based on max(Load Date Time Stamp). Is this the best practice more so in terms of performance(updates are expensive).




13 Replies