profiling-table

Table profiling for database migration recomputes current catalog metadata to capture a fresh, migration-ready profile. It analyzes the target object to capture keys, watermarks, and PII handling signals for downstream migration decisions.

A migration-ready data profile is a validated payload containing inferred keys, watermarks, PII actions, rationale, signals, and diagnostics. It provides essential metadata to guide dbt and migration tooling decisions for a specific table, view, or materialized view.

Yes, you can profile views and materialized views alongside physical tables. The profiling workflow targets any single catalog object to capture primary and foreign keys, watermarks, and PII actions regardless of object type.

Catalog metadata determines PII handling and watermarks by providing the raw signals that the profiling workflow infers from the current state. It recomputes these signals to generate diagnostics and PII actions for the target object.

A data quality profile payload includes inferred primary and foreign keys, watermark data, PII handling actions, rationale, diagnostics, and profiling signals. This complete payload supports downstream migration decisions and dbt tooling integration.

Single table profiling is limited to evaluating one target object at a time rather than analyzing entire database schemas simultaneously. It relies entirely on current catalog metadata accuracy to infer keys, watermarks, and PII actions for migration readiness.