Current mapping generation improvement points
I’ve demo-ed the posted processes for mapping generation and Data Vault a couple of times for varying audiences and (lucky me) no one has noticed the existing flaws 🙂 So it’s time to make a list of them to keep me from not forgetting to fix them. And it’s a heads up for the few people I know who are using the scripts.
- There is currently no way to keep the ‘transactional’ attributes out of the regular satellite. In this demo it happens when you create a hub entity out of the table COUNTRYLANGUAGE. This table contains attributes which say something about the relationship between country and language (is official and official language). These attributes will still be automatically created in the satellite of the language hub! These attributes will later also (correctly) be created in the link satellite 🙂
- The satellite mappings have not been tested if they actually run. I figured having the staging, history and hubs providing the correct data would be enough for the demo, but there are probably some typos here and there.
- The comparison script for the SCD2 mechanism still has to be implemented in the scripts which create the satellite mappings 🙂 It works in the history mappings so it will work in the satellite mappings as well, only has to be added though.
I’ll look into it soon.