Storage Mapping

A Storage Mapping connects a Storage Location to a concrete database and schema in your warehouse for a given Workspace or Environment.

Mappings let the same pipeline code target different physical schemas in development, QA, and production. Incorrect mappings are a common cause of "missing" tables after deploy or refresh.

Best practice: map development Workspaces to scratch schemas separate from Environment schemas. Avoid sharing the same schemas between an active Workspace and an Environment unless the Workspace is read-only.

See Storage Locations and Storage Mappings for configuration steps.