Performance Monitoring and Tuning · Topic 12 of 16
Data Transfer, Replication, Storage and Credit Costs
Calculate Snowflake data transfer, replication, storage and credit costs: which views to query, what drives each bill and the techniques that reduce it.
- 5 min
- Transfer is billed when data leaves for another region or cloud; same region is free.
- Replication cost = transfer plus refresh compute plus storage in the target.
- Storage views:
STORAGE_USAGE,DATABASE_STORAGE_USAGE_HISTORY,TABLE_STORAGE_METRICS.
What it is
A Snowflake bill has three main parts: compute (credits), storage, and data transfer. An administrator should be able to say which part grew, which view proves it and which lever lowers it.
Replication touches all three. It moves data between accounts (transfer), stores a copy (storage) and runs refreshes on serverless compute (credits).
How it works
Data transfer costs
Snowflake bills data transfer when data leaves your account to a different region on the same cloud, or to a different cloud. Data moved inside the same region is free, and ingress is not billed by Snowflake, although your cloud storage provider may charge egress fees on its side.
| Activity that can cause transfer cost | Notes |
|---|---|
COPY INTO <location> unloading to storage in another region or cloud | Unload close to the account when possible |
| Replicating databases or groups to another region or cloud | Charged on the bytes replicated |
| External functions and external network access calls | Leaves the account |
| Cross-Cloud Auto-Fulfillment of listings | Replication to another cloud or region |
| Output stage in another region or cloud | Files copied across regions |
Snowflake does not bill egress when a client retrieves query results across regions or clouds.
Views for transfer:
SNOWFLAKE.ACCOUNT_USAGE.DATA_TRANSFER_HISTORY: bytes transferred by source and target cloud and region.SNOWFLAKE.ORGANIZATION_USAGE.DATA_TRANSFER_HISTORY: the same across accounts, with 24 hours latency.
Replication costs
Replication cost has two parts: data transfer for the bytes sent to a region or cloud different from the source, and compute for the refresh work. Both are billed to the target account, the one that holds the secondary. Each secondary also keeps its own copy of the data, and its storage is billed in the target account too.
| View | Shows |
|---|---|
ACCOUNT_USAGE.REPLICATION_GROUP_USAGE_HISTORY | Credits and bytes for replication and failover groups |
ACCOUNT_USAGE.REPLICATION_USAGE_HISTORY | Credits and bytes for database replication |
ORGANIZATION_USAGE.REPLICATION_USAGE_HISTORY | Replication across accounts of the organization |
Cost levers: replicate only the databases and object types you need, lengthen the refresh interval, and avoid very frequent refreshes of large, high churn tables.
A scenario that says "replication costs went up after we shortened the schedule" is a refresh frequency question. More frequent refreshes mean more compute and more bytes moved.
Storage usage
Storage is billed per terabyte per month on the average daily compressed bytes. It includes table data, Time Travel and Fail-safe bytes, stage files and data kept alive for clones.
| View | Use |
|---|---|
ACCOUNT_USAGE.STORAGE_USAGE | Daily total storage for the account |
ACCOUNT_USAGE.DATABASE_STORAGE_USAGE_HISTORY | Daily storage per database |
ACCOUNT_USAGE.TABLE_STORAGE_METRICS | Per table bytes, including TIME_TRAVEL_BYTES, FAILSAFE_BYTES and RETAINED_FOR_CLONE_BYTES |
ACCOUNT_USAGE.STAGE_STORAGE_USAGE_HISTORY | Storage used by stages |
A table with a large TIME_TRAVEL_BYTES or FAILSAFE_BYTES value is a high churn table; shorter retention or a transient table cuts that cost. A large RETAINED_FOR_CLONE_BYTES value means a clone still references data the source has already dropped.
Credit consumption
Credits come from three places:
| Source | How billed | View |
|---|---|---|
| Virtual warehouses | Credits per hour by size, billed per second with a 60 second minimum each time the warehouse starts | WAREHOUSE_METERING_HISTORY |
| Serverless features | Credits for compute Snowflake runs for you | Feature views such as AUTOMATIC_CLUSTERING_HISTORY and PIPE_USAGE_HISTORY |
| Cloud services | Billed only if daily cloud services use exceeds 10 percent of daily warehouse credits | METERING_DAILY_HISTORY |
METERING_HISTORY gives hourly credits for warehouses, cloud services and serverless features. METERING_DAILY_HISTORY gives daily credits and applies the cloud services adjustment through the columns CREDITS_USED_CLOUD_SERVICES and CREDITS_ADJUSTMENT_CLOUD_SERVICES. Snowsight and most other views do not apply that adjustment.
To calculate what you were billed for in a day, use:
CREDITS_BILLED = CREDITS_USED_COMPUTE + CREDITS_USED_CLOUD_SERVICES + CREDITS_ADJUSTMENT_CLOUD_SERVICES
The adjustment is a negative number, so the cloud services credits that fall under the 10 percent threshold are not charged.
Cost optimization techniques
| Technique | Effect |
|---|---|
Set AUTO_SUSPEND low and AUTO_RESUME on | Stops idle compute credits |
| Right size warehouses and use multi cluster only when queues appear | Avoids paying for unused capacity |
| Resource monitors and Budgets | Alerts and suspension before overspend |
| Transient tables and short retention for rebuildable data | Less Time Travel and Fail-safe storage |
| Tags and query tags | Chargeback by team or project |
Filter on clustering columns, avoid SELECT * | Less data scanned, shorter runtime |
| Limit replication scope and frequency | Lower transfer and refresh cost |
Common mistakes
Assuming same region replication is billed as transfer. Transfer is billed only across regions or clouds.
Looking only at table size for storage cost. Time Travel, Fail-safe and clone retained bytes count.
Using Snowsight totals as the invoice for cloud services. The 10 percent adjustment is not applied there.
Blaming ingress. Snowflake does not bill ingress.
What to remember for the exam
- Transfer is billed when data leaves for another region or cloud; same region is free.
- Replication cost = transfer plus refresh compute plus storage in the target.
- Storage views:
STORAGE_USAGE,DATABASE_STORAGE_USAGE_HISTORY,TABLE_STORAGE_METRICS. - Warehouses bill per second with a 60 second minimum on each start.
METERING_DAILY_HISTORYshows billed cloud services after the 10 percent adjustment.
Check yourself
Which view tells you how many bytes were sent to another region?
DATA_TRANSFER_HISTORYinACCOUNT_USAGE(orORGANIZATION_USAGEfor all accounts).Where do you see Time Travel and Fail-safe bytes per table?
TABLE_STORAGE_METRICS, inTIME_TRAVEL_BYTESandFAILSAFE_BYTES.Which view shows cloud services credits actually billed?
METERING_DAILY_HISTORY, using the adjustment column.
Topic 12 of 16 in Performance Monitoring and Tuning
Test yourself on Performance Monitoring and Tuning
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.