Schemas

Schemas is the index of what's actually inside your connected databases — tables, columns and types. It exists so the Analyst can ground its SQL in your real structure instead of guessing at column names.

Schemas

Where it comes from

Two ways to populate it:

  • Ingest from Connector — point at a connection and Data Conductor reads its structure directly.
  • Paste a schema — at Schemas → New, paste a schema payload. Useful when a database isn't reachable from Data Conductor but you still want the Analyst to know its shape.

Browsing

The list shows one row per table, not per connection, so a warehouse with two hundred tables reads as two hundred rows rather than one. Clicking a table opens its columns.

Descriptions matter

Column descriptions are editable inline. They're worth filling in for anything non-obvious — status, type, coded integers — because they're what the Analyst reads when deciding which column answers a question. Saving a description re-indexes that column immediately; there's no separate rebuild step.

Keeping it current

Schema drifts. Re-index a connection after a migration, or after adding tables, so the Analyst isn't reasoning about a shape that no longer exists.