What You'll Build

By the end of this notebook, you will have a working SchemaFlow pipeline that produces:

• A parsed database change request:

  • title
  • domain
  • target schema
  • target table
  • normalized operations
  • notes

• An impact-analysis report:

  • impacted tables, columns, indexes, views, or relationships
  • risks
  • assumptions
  • optional File Search evidence summaries

• A rollout plan:

  • implementation steps
  • prechecks
  • postchecks
  • rollback actions

• A draft SQL script with four required sections:

  • LANDING (ODS)
  • STAGING (STG)
  • CORE (DIM/FACT/VIEW)
  • MARTS (SERVING)

• A validation result:

  • expected table checks
  • expected column checks
  • required keyword checks such as ALTER TABLE, UPDATE, or CREATE INDEX

• A saved JSON artifact:

  • change request
  • impact analysis
  • plan
  • SQL
  • validation
  • optional RAG metadata

• A Promptfoo eval harness:

  • Python provider
  • Python assertion file
  • generated Promptfoo config
  • parse-only eval case
  • full-flow eval case
  • timestamped JSON and HTML eval reports