Watch the Video
In our ongoing Data Vault Friday series, our CEO Michael Olschimke engages with a thoughtful inquiry from our audience.
“Dear Scalefree team, we receive data from the source for multiple company forms (like HoldingCompany, JointVenture), and we want to know if it’s recommended to save them in different entities (e.g., HoldingCompany_h/s, JointVenture_h/s) or one big entity (Company_h/s).
If we split them, we will have for each company form (e.g., Holding Company) about 10 links; If we store everything in one Company entity, we may face the situation that different company forms have different master data in the future, besides, it violates the Data Vault 2.0 rule that we should save the data as delivered by the source.”
In this insightful video, Michael delves into the strategic considerations of applying sub-setting and super-setting in the context of Data Vault 2.0. The question prompts a discussion on where to employ these techniques and the potential exceptions that might arise from the default strategy.
Michael provides practical insights and recommendations for effectively handling diverse company forms within the Data Vault framework, ensuring compliance with Data Vault 2.0 principles while addressing the complexities of master data variations.
Meet the Speaker
Michael Olschimke
Michael has more than 15 years of experience in Information Technology. During the last eight years he has specialized in Business Intelligence topics such as OLAP, Dimensional Modelling, and Data Mining. Challenge him with your questions!
