Is Replica Of Best Practices

Guidelines for getting reliable signal from Is Replica Of checks while keeping the noise (and the maintenance) low.

Migrate to Data Diff

This is the only best practice that matters for new work. Data Diff takes the same fields, the same Row Identifiers, the same Passthrough Fields, and the same Comparators, so recreating the check is mechanical. You gain change-type filtering and the maintained code path.

Keep Row Identifiers on the checks you still run

Without them an existing check can only tell you that the two sides differ, with no way to see which rows. Adding identifiers to a legacy check costs nothing and makes its anomalies actionable while you plan the migration.

Do not build new dependencies on this rule

Templates, automations, and runbooks that create Is Replica Of checks will keep working, but every new one is future migration work. Point them at Data Diff now.

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