Each Environment has a set of Storage Location Mappings, which define the physical locations (databases and schemas) of the Storage Locations that were previously configured. These can be accessed via Build Settings Storage and Environments Edit Environment Storage Mappings.
As each Environment can implement Storage Locations that map to different physical locations, this allows granular control over where data is stored for each Environment.
For example, in development, 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.
Updated 4 months ago