Data Profiling vs Data Quality Check
People think profiling data is the same as testing it. A profile only counts what is there: blanks, values and ranges. It passes no judgment. A quality check tests a rule, like no blank emails, and fails when the rule breaks. You profile first to learn the data. Then you write checks for the problems you found.
Data Profiling
Counting what is really in a table: blanks, values and ranges. It comes before checks.
Data profiling means looking at data to learn what is really in it. A profile counts the rows, the empty cells and the different values in each column. It shows the smallest, the largest and the most common values. You do it before you trust a new table or write checks for it. A profile describes the data. It does not judge it.
Data Quality Check
A rule data must pass. The pipeline tests it each time.
A data quality check is a rule that data must pass, run automatically in the pipeline. It might say a column has no blanks, or a key has no copies. It might say a value sits in a range, or a table is not empty. Checks usually run right after a load or a transform. A failed check can stop the next step, or just warn. Most data tools let you write checks in a few lines.
In one line
- Data Profiling
- Counting what is really in a table: blanks, values and ranges. It comes before checks.
- Data Quality Check
- A rule data must pass. The pipeline tests it each time.