Satellite naming

Data Vault 2.0
1

My Question is around naming of satellite:

System A sends data to system B .

System B passes the same data to EDW where we are doing RDV. System B is not doing any transformation of the data, it’s simply passing the data to EDW.

In EDW when we create the satellites, should I use System A or System B in satellite naming? E.g. S_Customer_< System A > or S_Customer_< System B>..

My preference is System A because that’s the actual data originating system. System B is not playing any data creator role in this case.

What would you recommend please?

Thanks!

2

Sounds to me like personal preference, I’d probably be in favour of the S__CUSTOMER__SYSTEM_B approach because it more accurately describes where you got the data from, The data may have originated from SYS_A but the source of the data is SYS_B.

Doesn’t really matter at the end of the day. Just make sure you’re consistent and it shouldn’t come back to bite you later.

All the best on your project,
Frankie

2 Likes
3
  • why would you say “System A”? What if tomorrow you no longer use System B and somehow point Sys A to RDV?
  • RDV’s data source is where it got its data from, in your scenario it’s System B
1 Like
4

Hey @Rupa,
If you’re absorbing from System B only, it’s correct, as @patrickcuba said. The Data comes from B, so B is the source and the name. We don’t know or have control over whether process A to B is going right.
Maybe it’s a good idea to absorb System A, too. It’s QAing the process, and yes, I know, we don’t delete data in Raw Vault, but if it’s about checking the process, we can delete A it if A and B are in synch and not, if not, to have a proper quality report and to fix it later.

2 Likes