settingsLogin | Registersettings
Scalefree
Show Menu

Example of the LSAT Entity

0 votes
Good Morning,

I am interested in gaining a better understanding off the LINK-SAT and how it fits within the DV model.

I have done a reasonable amount of research on the matter (having read Dan's books and many other documents online - I am yet to attend the formal training), but have been unable to locate an article that shows the input data, the logical and physical models as well as the output data.  I am more or a data consumer than a modeler, so I would like to have a picture of what the data looks like on the way in and on the way out, but am definitely interested in how the LSAT entity fits within the DV model itself.

I have spoken to a few people that have attended training through various organisations, who have been told that the LSAT isn't a valid entity type in DV and that context should only exist within a SAT, whilst others contradict this assertion.

Is anyone aware of a resource containing this level of detail?

Thank you very much for your help and suggestions.

Regards,
Scott
asked May 19, 2016 in Modelling by scott (120 points)

2 Answers

0 votes
Hi, Scott. I have several satellites to links. If that's what LINK-SAT means, than it is just a regular satellite which instead of having a hub driving it has a link table to drive it. Usefull when you need to capture, say, which links are valid as of now, or context to links, like orders.
answered Jun 21, 2016 by fabio (410 points)
0 votes
Hi Scott,

LINK-SAT is a Link Satellite, which is connected to the Link primary key, just as a Hub Satelite (HUB-SAT) is connected to a Hub.

This is a valid entity in Data Vault and contains attributes which describe the relationship.

The discussion about validity that I know of is about using attributes within (Transactional) Link tables, but I never heard about the fact a Link Satellite would be inappropriate in general.

For example you could have a relationship between a product and a store where it is sold.

The link would be L_Product_Store.

If you like to store contextual data about this relationship you need to create a satellite related to the link. Some attributes specific for this relationship, and therefore stored in the LINK-SAT could be :
- stock on hand
- local article price
- article classification
- assortment start date
- assortment expiry date

Another example could be, Employee and Function.

Given the link L_Employee_Function contains all relationships that ever have existed between those 2 entities,  there must be a place that can tell when the Function assignment was valid.
This due to the fact that Function assignments within a company can change over time.

That would be the link satellite, containing the Assignment_Start_Date and Assignment_End_Date attributes for example.

I hope this helps,
Greets,

Jacob Siemaszko
answered Oct 22, 2017 by simco_admin (660 points)
Scalefree Scalefree

Upcoming Trainings

  • July 01 to 03 - Amsterdam (English) Data Vault 2.0 Boot Camp and Certification

  • August 05 to 07 - Berlin (German) Data Vault 2.0 Boot Camp and Certification

  • September 9 to 13 - Hanover WWDVC EU

  • September 16 to 18 - Brussels (English) Data Vault 2.0 Boot Camp and Certification

  • October 21 to 23 - Hanover (German) Data Vault 2.0 Boot Camp and Certification

  • November 18 to 20 - Amsterdam (English) Data Vault 2.0 Boot Camp and Certification

  • December 02 to 04 - Dusseldorf (German) Data Vault 2.0 Boot Camp and Certification

  • December 16 to 18 - Zurich (English) Data Vault 2.0 Boot Camp and Certification

  • Contact us for inhouse training engagements.
    Visual Data Vault: Logical Modelling for Data Vault - Free Download!
    Scalefree
    DataVault.guru is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License.
    Permissions beyond the scope of this license are available in our license.

    DataVault.guru | DWH Wiki | Recent questions RSS feed | Imprint | Provided by Michael Olschimke
    ...