Disaster Recovery, Backup and Data Replication · Topic 3 of 9
Replication and Editions, Lower Edition Targets and Key Considerations
Know what account replication needs per Snowflake edition, how IGNORE EDITION CHECK works for lower edition targets and the key points to check first.
- 5 min
- Database and share replication: all editions. Other account objects and failover: Business Critical or higher.
- Failover groups only exist in Business Critical or higher accounts, so targets must be too.
- Business Critical source to lower edition target errors unless
IGNORE EDITION CHECKis added.
What it is
Edition decides which replication features you can use and where you may send data. The same scenario can have a different answer on Standard, Enterprise and Business Critical, and the exam tests exactly that.
The second half of the page lists what else to check before replicating: cost, references between objects, read only targets and the order in which groups refresh.
How it works
Replication by edition
| Capability | Standard | Enterprise | Business Critical and higher |
|---|---|---|---|
| Database replication | Yes | Yes | Yes |
| Share replication | Yes | Yes | Yes |
| Replicating other account objects (users, roles, warehouses, integrations and so on) | No | No | Yes |
| Failover groups, failover and failback | No | No | Yes |
A failover group can only be created in a Business Critical or higher account. That means every account in a failover design, source and targets, must be Business Critical or higher.
Edition rules in practice:
- A Standard account can replicate a database to another account, but cannot replicate its users and roles, and cannot fail over.
- Enterprise adds longer Time Travel and other features, but it does not change the replication rules above.
- Disaster recovery for the whole account, with users, roles and warehouses present in the target, needs Business Critical in both accounts.
"Which edition is the minimum to fail over an account to another region?" The answer is Business Critical, not Enterprise.
Replicating to a lower edition
Business Critical is meant for regulated data, so Snowflake guards against sending that data to a lower edition by accident. If a primary group in a Business Critical or higher account would replicate to a lower edition target, the statement returns an error. The error applies when:
- the group has only databases or shares, or
- the group includes object types and a HIPAA or PHI agreement is in place without a matching agreement on the target accounts.
To go ahead on purpose, add IGNORE EDITION CHECK to the CREATE or ALTER statement. ACCOUNTADMIN or a role with CREATE REPLICATION GROUP, CREATE FAILOVER GROUP or OWNERSHIP can use it.
CREATE REPLICATION GROUP rg_reporting
OBJECT_TYPES = DATABASES
ALLOWED_DATABASES = reporting
ALLOWED_ACCOUNTS = myorg.acct_standard
REPLICATION_SCHEDULE = '60 MINUTE'
IGNORE EDITION CHECK;
The override moves the responsibility to you. Before using it, confirm that the data does not need Business Critical controls, and that regulatory agreements allow the target account.
| Direction | Result |
|---|---|
| Standard or Enterprise source to Business Critical target | Allowed for databases and shares; more features available in the target |
| Business Critical source to lower edition target | Error unless IGNORE EDITION CHECK is used |
| Failover group to lower edition target | Not possible; failover groups need Business Critical or higher |
Key considerations before replicating
Scope and relationships
- Accounts must belong to the same organization.
- Replicate only what you need. Every object type and database adds transfer, storage and refresh work.
- References between objects must stay valid. If a view, stream, policy or sequence refers to an object in another database that is not replicated, the refresh can fail. Put objects that depend on each other in the same group.
- A group that holds a policy must be refreshed before a group whose objects use that policy, or the references dangle.
Cost
- Cross region and cross cloud replication is billed for data transfer. Same region replication is not.
- Refresh work uses serverless compute and is billed as credits; the target stores its own copy.
- A tighter schedule means more refreshes, so more cost.
Behavior of the secondary
- Secondary objects are read only until promotion.
- Time Travel and Fail-safe data are kept independently in each account, and the retention period in the secondary starts at its refresh.
- Historical usage data does not replicate.
Operations
- Grant
REPLICATE,FAILOVERand the other group privileges in both accounts. - Test failover on a schedule, and test that applications can reach the target account.
- Configure target side items before failover: trust relationships for storage integrations, notification setup for auto ingest pipes, and directory table refresh for stages.
- Suspend scheduled refresh before a planned failover.
| Question to ask | Why |
|---|---|
| Which objects must exist in the target? | Decides database replication against a group |
| Which edition are source and target? | Decides what is possible |
| What RPO and RTO? | Decides schedule, cost and failover plan |
| Which regions and clouds? | Decides transfer cost |
| Which objects reference each other? | Decides group membership and order |
Common mistakes
Planning failover on Enterprise. Failover groups need Business Critical or higher.
Using IGNORE EDITION CHECK as a habit. It removes a safety check for regulated data.
Splitting dependent objects across groups. References can dangle and refreshes can fail.
Forgetting that the secondary is billed storage. The target pays for its copy.
What to remember for the exam
- Database and share replication: all editions. Other account objects and failover: Business Critical or higher.
- Failover groups only exist in Business Critical or higher accounts, so targets must be too.
- Business Critical source to lower edition target errors unless
IGNORE EDITION CHECKis added. - Keep related objects in one group and refresh policy groups first.
- Transfer is billed across regions and clouds; each target stores its own copy.
Check yourself
Which edition is the minimum for replicating users and roles?
Business Critical.
A Business Critical account wants to replicate a database to a Standard account. What is needed?
IGNORE EDITION CHECKon the statement, used by ACCOUNTADMIN or a role with the right group privileges.Why group a view and the table it reads in the same replication group?
So references stay valid and the refresh does not fail on dangling objects.
Topic 3 of 9 in Disaster Recovery, Backup and Data Replication
Test yourself on Disaster Recovery, Backup and Data Replication
The full Snowflake ADA-C02 question bank has 814 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.