Schema:: ACCOUNT_USAGE

METERING_DAILY_HISTORY View¶

The METERING_DAILY_HISTORY view in the ACCOUNT_USAGE schema can be used to return the daily credit usage and a cloud services rebate for an account within the last 365 days (1 year).

Columns¶

Column Name	Data Type	Description
SERVICE_TYPE	TEXT	Type of service that is consuming credits, which can be one of the following: `AUTO_CLUSTERING` — See Automatic Clustering. `MATERIALIZED_VIEW` — See Working with Materialized Views. `PIPE` — See Snowpipe. `QUERY_ACCELERATION` — See Using the Query Acceleration Service. `REPLICATION` — See Introduction to replication and failover. `SEARCH_OPTIMIZATION` — See Search Optimization Service. `SERVERLESS_TASK` — See Introduction to Tasks. `SNOWPIPE_STREAMING` — See Snowpipe Streaming. `WAREHOUSE_METERING` — See Overview of Warehouses. `WAREHOUSE_METERING_READER` — See Managing reader accounts.
USAGE_DATE	TIMESTAMP_LTZ	The date (in the local time zone) in which the usage took place.
CREDITS_USED_COMPUTE	NUMBER	Number of credits billed for warehouses and serverless compute resources in the day.
CREDITS_USED_CLOUD_SERVICES	NUMBER	Number of credits billed for cloud services in the day.
CREDITS_USED	NUMBER	Sum of CREDITS_USED_COMPUTE and CREDITS_USED_CLOUD_SERVICES.
CREDITS_ADJUSTMENT_CLOUD_SERVICES	NUMBER	Number of credits adjusted for included cloud services. This is a negative value (e.g. `-9`).
CREDITS_BILLED	NUMBER	Total number of credits billed for the account in the day. This is a sum of CREDITS_USED_COMPUTE, CREDITS_USED_CLOUD_SERVICES, and CREDITS_ADJUSTMENT_CLOUD_SERVICES.

Usage Notes¶

Latency for the view may be up to 180 minutes (3 hours).
If you want to reconcile the data in this view with a corresponding view in the ORGANIZATION USAGE schema, you must first set the timezone of the session to UTC. Before querying the Account Usage view, execute:
ALTER SESSION SET TIMEZONE = UTC;
Copy