Accounts and Security · Topic 1 of 17

Account and Database Strategy - One Account or Many

Decide between one Snowflake account and many: benefits, limits, isolation, cross-account features, constraints and the use cases that justify a split.

  • 5 min
In a nutshell
  • An account is one cloud and one region; the organization groups accounts and ORGADMIN manages them.
  • Split accounts for residency, edition, hard isolation or cloud choice; otherwise stay with one.
  • Cloning is single account; sharing is same region and cloud; cross region needs replication or auto fulfillment.

What it is

An account is the top boundary in Snowflake. It holds its own users, roles, warehouses, databases, network policies, integrations and resource monitors, and it lives in exactly one cloud platform and region. Accounts that belong to the same company are grouped under an organization, managed by the ORGADMIN role.

The exam asks an Architect to turn business requirements into a layout: how many accounts, in which regions and editions, and how databases are arranged inside each one. The right answer is almost always the simplest layout that still meets the isolation, residency and governance requirement.

Business requirementsresidency, isolation, editiondriveAccount countone or manythenDatabase layoutper domain or environmentthenCross account featuressharing, replication

How it works

One account or several

AspectOne accountMultiple accounts
Data sharingEverything is already visible to granted rolesNeeds Secure Data Sharing, listings or replication
AdministrationOne set of users, roles, policiesEach account has its own, so provisioning is repeated
IsolationLogical only (roles, policies)Hard boundary: separate users, network rules and encryption keys
Region and cloudOne region, one cloudEach account can sit in a different region or cloud
EditionOne edition for everythingSensitive data can sit in a higher edition only
Cost visibilityOne bill, split by warehouse and tagsPer account usage, rolled up in the organization

A single account is easier to govern and cheaper to run. Splitting is justified by a hard requirement, not by taste.

Reasons to isolate or segment accounts

  • Data residency or regulation. Data that must stay in a country or region needs an account in that region.
  • Different editions. Put regulated workloads in a Business Critical account and keep the rest on a cheaper edition.
  • Strong separation of duties. A subsidiary, a customer or a business unit that must never share users, roles or administrators.
  • Cloud choice. A business unit that runs on a different cloud platform.
  • Blast radius. A mistake or compromise in one account cannot touch another.
  • Provider and consumer split. One account publishes data; others consume it.
Exam tip

"Separate dev, test and prod" does not by itself require separate accounts. Separate databases (or schemas) plus role design cover it, and zero copy cloning only works inside one account. Choose separate accounts only when the scenario asks for hard isolation, different regions or different editions.

Database strategy inside an account

Databases and schemas are the unit of organization, access and replication. Common layouts are one database per environment (DEV, TEST, PROD), one per business domain, or one per data layer such as raw and curated. Whatever the layout, design it so that grants, replication and sharing line up with the boundary: a database is what you replicate, a share exposes objects from a database, and database roles are scoped to a database.

OrganizationORGADMINcontainsAccount Aregion 1, Business Criticalshare or replicateAccount Bregion 2, EnterpriseAccount AholdsDatabasesper domain or environmentholdSchemas and objects

Features that work across accounts

FeatureWhat it does
Secure Data SharingRead only access to live data without copying it, to accounts in the same region and cloud
Listings and Snowflake MarketplacePublish data products; Cross-Cloud Auto-Fulfillment replicates the data to other regions and clouds for consumers
Database replicationCopies a database to another account in the organization
Replication and failover groupsReplicate several object types (databases, users, roles, warehouses, integrations) and fail over; failover groups need Business Critical
Client Redirect (connections)A connection URL that moves clients to another account during failover
Organization usage viewsUsage and cost across all accounts in the organization

Sharing across regions or clouds is not direct: the data must be replicated first, or fulfilled through a listing.

Considerations and constraints

  • Account objects are not shared. Users, roles, warehouses, resource monitors and network policies are per account, so each new account needs its own provisioning. Replication groups can copy some of them.
  • Cloning stays in the account. You cannot clone a database into another account.
  • Sharing needs the same region. Direct shares work only inside one region of one cloud.
  • Replication has cost. Storage in each copy, plus compute and data transfer for refreshes.
  • Identity. Each account needs its own SSO integration and SCIM or provisioning setup.
  • Edition for features. Replication of some objects and failover need the right edition.

Use cases that fit each strategy

ScenarioStrategy
Small team, single region, shared analyticsOne account, several databases
Subsidiaries in the EU and the US with residency rulesOne account per region, grouped in one organization
PCI or PHI workload next to ordinary analyticsSeparate Business Critical account for the regulated data
Selling data to customers on other cloudsProvider account with a listing and Cross-Cloud Auto-Fulfillment
Disaster recovery in a second regionReplication and failover groups with Client Redirect

Common mistakes

Creating an account per environment by habit. Databases and roles already separate environments, and extra accounts multiply administration.

Expecting to share directly across regions. Replicate first or use a listing with auto fulfillment.

Forgetting account level objects. Users, roles and policies do not follow a database replica unless a replication group includes them.

What to remember for the exam

  • An account is one cloud and one region; the organization groups accounts and ORGADMIN manages them.
  • Split accounts for residency, edition, hard isolation or cloud choice; otherwise stay with one.
  • Cloning is single account; sharing is same region and cloud; cross region needs replication or auto fulfillment.
  • Account level objects (users, roles, warehouses, network policies) are per account.
  • Failover groups, Client Redirect and organization usage views serve multi account designs.

Check yourself

  • A company needs dev, test and prod with no special regulation. Do they need three accounts?

    No. Separate databases and roles are enough, and cloning only works inside one account.

  • A provider wants to share data with a consumer on another cloud. What is needed?

    The data must be replicated to the consumer's region, typically through a listing with Cross-Cloud Auto-Fulfillment, because direct shares work only within one region and cloud.

  • Why might PHI data live in its own account?

    To use Business Critical only for the regulated workload and to get a hard boundary of users, roles and keys.

Topic 1 of 17 in Accounts and Security

Test yourself on Accounts and Security

The full Snowflake ARA-C01 question bank has 687 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.