Drift compare across environments fractures into separate catalogs.
Environment FQN Mapping
One logical table identity spans every environment — promotion, drift compare, and lineage stay continuous.
Operate
Most warehouses use different database names per environment. Without a mapping, dev and prod look like unrelated tables to drift, lineage, and the catalog. BoltPipeline collapses them into one logical identity on ingest and expands back to the physical name when the agent runs SQL.
What it solves
Common problems this capability removes from your engineering workflow.
Lineage breaks because the same logical table has different physical names.
Promotion can't find the target table after a dev-to-prod copy.
Setting up env mapping forces a giant migration before anything works.
How it works
The flow this capability runs end-to-end inside the platform.
- 1Define a logical alias per database and per environment, once.
- 2Inbound metadata is rewritten to the logical name on every ingest.
- 3Outbound queries expand back to the physical name your agent needs.
- 4Tenants with no mapping configured fall back to identity — zero setup.
Related capabilities
Other capabilities in the BoltPipeline platform that work alongside this one.
1Intelligent Pipeline
Pipeline Promotion
Move a certified pipeline from dev to prod through a request-approve-execute workflow with separation of duties.
2Validation &Schema Drift Detection
Catch schema changes the moment they land — classified by impact, tied to lineage, and shown across environments.
3Lineage &Column-Level Lineage
One unified DAG covers pipelines, views, MVs, dynamic tables, and procedures — at column grain, before data moves.
See it on your data.
Try BoltPipeline against your live database — your data never leaves your environment.