- Schemas:
WAREHOUSE_METERING_HISTORY View¶
This Account Usage view can be used to return the hourly credit usage for a single warehouse (or all the warehouses in your account) within the last 365 days (1 year).
Columns¶
Column Name |
Data Type |
Description |
---|---|---|
READER_ACCOUNT_NAME |
TEXT |
Name of the reader account where the warehouse usage took place. Column only included in view in READER_ACCOUNT_USAGE schema. |
START_TIME |
TIMESTAMP_LTZ |
The date and beginning of the hour (in the local time zone) in which the warehouse usage took place. |
END_TIME |
TIMESTAMP_LTZ |
The date and end of the hour (in the local time zone) in which the warehouse usage took place. |
WAREHOUSE_ID |
NUMBER |
Internal/system-generated identifier for the warehouse. |
WAREHOUSE_NAME |
TEXT |
Name of the warehouse. |
CREDITS_USED |
NUMBER |
Total number of credits used for the warehouse in the hour. This is a sum of CREDITS_USED_COMPUTE and CREDITS_USED_CLOUD_SERVICES. This value does not take into account the adjustment for cloud services, and may therefore be greater than your actual credit consumption. |
CREDITS_USED_COMPUTE |
NUMBER |
Number of credits used for the warehouse in the hour. |
CREDITS_USED_CLOUD_SERVICES |
NUMBER |
Number of credits used for cloud services in the hour. |
Usage Notes¶
Latency for the view may be up to 180 minutes (3 hours), except for the CREDITS_USED_CLOUD_SERVICES column. Latency for CREDITS_USED_CLOUD_SERVICES may be up to 6 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;