Skip to content

Equal To Best Practices

Guidelines for getting reliable signal from Equal To checks while keeping the noise (and the maintenance) low.

Set a tolerance whenever the value is computed

This is the difference between a check that works and one people mute. An absolute margin suits money and counts; a relative margin suits ratios and values whose magnitude varies. Pick a number you can justify, small enough that a real regression still fails.

Pin constants that a configuration guarantees, not values that happen to be stable

A column that is currently always 1 is not necessarily supposed to be. Pin the constant when something enforces it (a schema default, a business rule, a contract), and record that reason in the description.

Split multi-field checks that do not share an owner

One check across several columns is compact, but every anomaly lands in the same stream. When different teams fix different columns, separate checks make triage clearer.

Consider Equal To Field when the reference is another column

If the constant is really "whatever the other column says", Equal To Field keeps the rule correct as the data moves, instead of going stale the moment the value changes.

Keep coverage at 100% unless a known backlog exists

At 100% coverage every failing row is reported as a Record Anomaly, which tells you exactly which rows break the rule. Below 100% the check reports a single Shape Anomaly only when the failing fraction crosses the tolerance, and no per-row detail is produced. Lower coverage only while a known set of legacy rows is being cleaned up.

Scope with a filter instead of loosening coverage

When the rule only applies to part of the table (one segment, one channel, one period), express that with a filter clause rather than by lowering coverage. The filter removes the out-of-scope rows from evaluation entirely, and the expression is echoed in every anomaly message.

Route the anomalies to the right people

A failure usually points at the system that produced the value, not at the warehouse. Set an Anomaly Assignee from the team that owns that producer, and tag the check so related checks are easy to find.

See Also