Snowpipe Streaming Costs

With Snowpipe Streaming’s serverless compute model, users can stream any data volume without managing a virtual warehouse. Instead, Snowflake provides and manages the compute resources, automatically growing or shrinking capacity based on the current Snowpipe Streaming load.

Accounts are charged based on compute for their Snowpipe Streaming migration compute costs and per-second client ingestion time. Note the following:

  • File migration sometimes may be pre-empted by clustering or other DML operations.

  • Migration may not always occur and therefore compute costs may be reduced.

For more information, see the “Serverless Feature Credit Table” in the Snowflake service consumption table.

Estimating Snowpipe Streaming Charges

Given the number of factors that can differentiate Snowpipe Streaming loads, it is very difficult for Snowflake to provide sample costs. Size of records, number of records, data types, etc. can affect the compute resource consumption for file migration. Client charges are dictated only by how many clients are actively writing data to Snowflake on a per second basis.

We suggest that you experiment by performing a typical streaming ingestion load to estimate future charges.

Viewing the Data Load History for Your Account

Account administrators (users with the ACCOUNTADMIN role) or users with a role granted the MONITOR USAGE global privilege can use SQL commands to view the credits billed to your Snowflake account within a specified date range.

To query the history of data migrated into Snowflake tables, the amount of time spent loading data into Snowflake tables using Snowpipe Streaming and the credits consumed, query the following views:

For more information about querying the total Snowpipe Streaming costs, including both compute and client costs, see a SQL example.