Once again, another question – and another answer. This time we are discussing the metadata layer as compared to a traditional approach for reporting. If you have comments, thoughts, or other experiences I encourage you to add your COMMENT to the end of this posting.
As you know, I’ve launched one-on-one coaching, this is the kind of knowledge you get within the walls of one-on-one coaching. But for TODAY – I’m giving you the answers FREE to show you the kind of value you get when you sign up for my coaching sessions. Contact me today: email@example.com for more information.
What does a the metadata layer look like for reporting compared to a traditional approach?
There really is no difference. A metadata layer is a metadata layer – and remains separate from the data warehouse. Now, there is a rule here that can’t be ignored: the Data Vault carries raw data – that is: the good, the bad, and the ugly data. It is not cleansed, it is not fixed, it is not massaged – so in this regard, it should “never” be released to the business users this way. BUT if you really want to release this data, I would recommend you build VIEWS that look like dimensions and facts – and have the reporting tools hit those. When performance takes a dive, then you physically build data marts (turn the views into real tables).
BUT: what you really should do is either a) build a BUSINESS DATA VAULT or b) build star schemas with BUSINESS LOGIC in the ETL going from the raw data vault to the data marts.