Each Environment/Workspace has a set of Storage Mappings, which define the physical locations (databases and schemas) of the Storage Locations that were previously configured. These can be accessed via Build Settings by editing each individual environment/workspace.
As each Environment/Workspace can implement Storage Locations that map to different physical locations, this allows granular control over where data is stored for each Environment/Workspace.
For example, in a development workspace, you can map each of your Storage Locations to the same physical location, effectively placing all database objects in a single schema used as a scratch working area.
Meanwhile in production, you can map each Storage Location to a different physical location for each storage location, allowing for the use of Snowflake roles on specific schemas to control access to objects.
To input database and schema objects manually, instead of choosing them from the dropdown menu, activate the Override Mapping Values option. This step may be necessary when mapping to a database or schema for which you lack access permissions.
Updated about 21 hours ago