Load data, from a Time Variant table, into one or more Satellites.

Process: {Configuration Database}.[dbo].[dv_load_sats_for_source_table]


  • Data is loaded, from a Time Variant table, into the Satellite.
  • For modelling and efficiency purposes, the Satellite may be split into two or more Satellites.
  • Split Satellites, which are fed from a single source, remain a single logical entity, and must be subservient to a single Hub or Link.
  • The Load process will not automatically create all missing Hub and Link entries, for new keys which have arrived through the Time Variant table.
    • Satellites are normally processed as part of an orchestrated Time Variant Table load, which manages the processing of Hub and Link Keys.
  • Satellite Data is held as a time series, with Row Start and End Dates named according to the Defaults held in the Configuration database.
  • The Server Clock is used to Start and End Date all Entries.
  • Current Rows will be End Dated using the High Date as specified in the Default Configuration.
  • Satellite Data is merged. New rows are created only when a change is detected.
  • When theTime Variant table is marked as a “Full” load, keys which are present in the Satellite (Hub or Link), but not in theTime Variant table, are treated as “Deleted”.
    • In this case, the currently Active row is marked deleted by end dating it and creating a  new Tombstone Row for the Key.
  • When the Time Variant table is marked as a “Delta” load, Rows are never marked as Deleted and no Tombstone Rows are created.
  • When the Time Variant table is marked as a “CDC” load, all Inserts, Updates and Deletes, for the requested period in time, are merged into the Satellite.

Testing the Raw Vault Satellite Load

How to add a new Satellite to the Raw Vault