Mandatory DV_tenantid in satellite tables

Hi @patrickcuba

Given I’m implementing DV for multiple entities of the financial group, I’ve added dv_tenantid to all DV structures to logically segregate business keys of Offers, Contracts, etc.
However, till now I have not used DV_tenantid attribute from regular satellties. I wonder in which scenarios would this attribute be used from a satellite? If I need tenant information in the business logic or Information Mart I always SELECT it from the Hub or Link.

Regards,
Marcin

here you go, Data Vault Techniques: Row Access Policies + Multi-Tenancy

Good explanation, thank you!
Since I’m virtualizing dims and exposing them in infomarts to end users, it sufficient to apply row level security for hubs and bridges (facts) as of know.
We are not thinking yet to provide direct access for Analysts to the Raw Vault structures, but maybe in the future it could become useful.
Thanks again for making it clear.

Regards,
Marcin

1 Like