Data Validation Best Practice Guide
Quality data is critical for identifying performance gaps, key industry trends, and revenue opportunities. Since the data wave, businesses have shifted toward unstructured and semi-structured data, increasing the need for BI processing and validation. Validating your data provides access to reliable data on demand, minimizes effort, cost, and errors, and increases competitive edge with more accurate insights. Our exclusive data validation framework can be implemented in any BI project with 100% accuracy for descriptive, prescriptive, and other insights.
Seven-step validation framework
Ensure upstream data is accessible. Record the number of data records to identify if data is lost or duplicated during the next steps.
Identify data with a unique combination of attributes. Perform a trend analysis of key attributes — examples include the rate of attribute changes or the rate of data changes period over period.
If using Databricks (ADB), process notebooks in parallel (versus sequentially) to reduce refresh time and identify platform run failures. If using tabular models, cross-check the data consistency between data mart and tabular models. For non-cloud environments using SSIS or other ETL tools, implement similar checks for staging against data mart publish — for example, data profiling in SSIS.
Perform build verification testing (BVT), table-level BVT, and BVT for multiple sources.
Validate that no data was lost or duplicated while being pulled from databases — for example, by tracking Azure Data Warehouse (ADW) dump failures. Check for data loss when changing the schema from temporary format to the end-user-agreed schema. Track downstream user data usage and remove unused tables/views to improve report performance.
Track measure execution time to detect time lags. Remove unused reporting measures. Check all tabular/multidimensional columns to prevent failures while processing data. Compare previous tabular/multidimensional refreshes with the current refresh for sudden drops or increases in record counts beyond a predefined threshold.
Use an Import vs. tabular model validator to compare datapoint consistency rendered in the BI report through import model and tabular. Track BI report usage to understand visitor counts across pages, active users, and historical usage patterns.
References
Want help building a data validation framework for your BI estate? MAQ Software's data team can help.
Talk to our team
Dynamics 365 Development Best Practices
Optimize your Dynamics 365 environment with our 32 best practices on developing fields, views, and more.
Read More