analyzing-table

Scoping a single table for migration requires analyzing the target object's writer context and SQL structure from catalog-backed DDL. This process identifies the writer, extracts the dependency call tree, and validates results against guardrails to prepare for downstream transformation steps.

A table writer is the process or mechanism that populates a target table during database migration. You identify writer candidates by analyzing catalog-backed DDL to evaluate SQL structure and determine the best path for table writes before resolving dependencies.

Build a dependency call tree by analyzing the target table's SQL structure from catalog-backed DDL. The analysis extracts SQL elements, maps dependency relationships, and uses catalog evidence as the source of truth to resolve dependencies and generate context for downstream validation steps.

You can analyze views and materialized views alongside physical tables. The scoping workflow applies to any single target object, identifying writer context, SQL structure, and dependency call tree from catalog-backed DDL to prepare the object for migration.

To start analyzing a table for migration, you need the fully-qualified table name of the target object. The workflow uses this name to retrieve catalog-backed DDL, identify writer candidates, build the call tree, and persist the analysis results to the catalog for downstream steps.