A company is migrating to Snowflake. Production and non-production data must not reside in the same account.
Which account design and lifecycle-management plan satisfies this requirement?
Separate Production and Non-Production Snowflake accounts meet the required environment isolation. Development and testing can occur within the Non-Production account, using a cloned database to create an independent writable test copy; version-controlled code can then be promoted to the separate Production account. Snowflake cloning creates an independent writable clone, while cross-account data movement is handled by replication rather than direct cloning.
Community Discussion