What problem does it solve?
When migrating databases, refactoring queries, or validating ETL pipelines, you need to prove that two tables contain the same data — or pinpoint exactly where they diverge. Manual diff SQL is error-prone, and naive comparisons produce false positives from auto-generated timestamps or silently miss value differences.
Core Features & Use Cases
- Guided diff workflow: Discovers schemas, identifies primary key candidates via cardinality checks, detects auto-timestamp columns, and confirms assumptions with the user before running comparisons.
- Multi-algorithm comparison: Uses the
data_diff tool with profile (column statistics), joindiff (same-database FULL OUTER JOIN), hashdiff (cross-database checksum bisection), and cascade modes, with partitioning for large tables.
- Regulated data safeguards: Defaults to profile-only comparison for tables likely containing PII/PHI/PCI and requires explicit approval before sending sample diff rows to the LLM.
- Use Case: After migrating
orders from PostgreSQL to Snowflake, run a profile comparison to find that amount has rounding drift and status has 47 unexpected NULLs, then run a targeted hashdiff on only those columns to identify the affected rows.
Quick Start
Ask the assistant to verify that the orders table in the production Postgres database matches the migrated copy in Snowflake using the data-parity workflow.