.net - How do you implement Data Quality & Validation rules in a data warehouse? -
I am developing a debt warehouse to be part of my company's enterprise application suite. So I'm learning a lot about DW concepts but rule engine is difficult and I can not find more information about different methods of implementation Focus of rules is to validate the quality of the data, and this is also a warning when something Business Metrics (for example, $ xx.xx for sale) has reached
Our app needs to be optimized for each customer, so I What are valid rules to make me some ways to apply the rules engine?
- Tools created?
- Framework / API
- Design Patents to Make Your Own
- Other Thoughts
Thanks.
It can help to see it as something different, together with a working system - The opposition of a "big engine" which is responsible for everything.
When it comes to "business metrics", see (major performance indicators). Analytical engines (, , etc ...) allow for the KPI's simple definition and presentation (dashboard). If you are developing yourself, you can still get the idea of concept.
The quality of the data is mostly the responsibility of "operating systems", where the data is collected. If the garbage reaches DW, then it's too late. Use to get some information about how source data looks - the quality of the data is to be applied to the source.
During the DW loading process, you move the ECCD (Extract, Clean, Conform, Distribute) approach to the step-by-step implementation of some "data standards" ETL tools ( , , , etc.) are designed to help with it.
Regarding the Rule Engine, look at , , , , etc. " Independent system ", and can be used to implement business rules when operating with operating systems. Applying business rules usually increases the quality of the data. You can download Dorlos and start flirting quite quickly, other vendors are allowed to download some freebies too.
Comments
Post a Comment