Schema:: ORGANIZATION_USAGE

METERING_DAILY_HISTORY view¶

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

Note

As of March 1, 2026, Snowflake no longer bills customers for hybrid table requests; however, you can still query this view to see historical consumption data. Any new data in the view as of March 1, 2026, will not be billed to customers.

Columns¶


Column Name	Data Type	Description
SERVICE_TYPE	VARCHAR	Type of service that is consuming credits. The following list includes many, but not all, of the possible service types: `AI_SERVICES`: See Snowflake Cortex AI Functions (including LLM functions), Cortex Analyst, and Document AI. `ARCHIVE_STORAGE_RETRIEVAL_FILE_PROCESSING`: See Billing for storage lifecycle policies. `ARCHIVE_STORAGE_WRITE`: See Billing for storage lifecycle policies. `AUTO_CLUSTERING`: See Automatic Clustering. `BACKUP`: See Backups for disaster recovery and immutable storage. `COPY_FILES`: See COPY FILES. `DATA_QUALITY_MONITORING`: See Introduction to data quality checks. `FAILSAFE_RECOVERY`: See Understanding and viewing Fail-safe. `HYBRID_TABLE_REQUESTS`: See Hybrid tables. `MATERIALIZED_VIEW`: See Working with Materialized Views. `OPENFLOW_COMPUTE_BYOC`: See Openflow BYOC cost and scaling considerations. `OPENFLOW_COMPUTE_SNOWFLAKE`: See Openflow Snowflake Deployment cost and scaling considerations. `PIPE`: See Snowpipe. `POSTGRES_COMPUTE`: See Snowflake Postgres. `POSTGRES_COMPUTE_HA`: See Snowflake Postgres. `QUERY_ACCELERATION`: See Using the Query Acceleration Service (QAS). `REPLICATION`: See Introduction to replication and failover across multiple accounts. `SEARCH_OPTIMIZATION`: See Search optimization service. `SENSITIVE_DATA_CLASSIFICATION`: See Introduction to sensitive data classification. `SERVERLESS_ALERTS`: See Setting up alerts based on data in Snowflake. `SERVERLESS_TASK`: See Introduction to tasks. `SNOWPARK_CONTAINER_SERVICES`: See Snowpark Container Services. `SNOWPIPE_STREAMING`: See Snowpipe Streaming. `STORAGE_LIFECYCLE_POLICY_EXECUTION`: Compute cost to apply a policy on a target table and expire or archive rows (policy execution). See Storage lifecycle policies. `TELEMETRY_DATA_INGEST`: See Event table overview. `TRUST_CENTER`: See Trust Center. `WAREHOUSE_METERING`: See Overview of warehouses. `WAREHOUSE_METERING_READER`: See Manage reader accounts.
ORGANIZATION_NAME	VARCHAR	Name of the organization where the usage took place.
ACCOUNT_NAME	VARCHAR	Name of the account where the usage took place.
USAGE_DATE	DATE	The date (in the UTC time zone) in which the usage took place.
CREDITS_USED_COMPUTE	NUMBER	Number of credits used for warehouses and serverless compute resources during the USAGE_DATE.
CREDITS_USED_CLOUD_SERVICES	NUMBER	Number of credits used for cloud services during the USAGE_DATE.
CREDITS_USED	NUMBER	Total of CREDITS_USED_COMPUTE plus CREDITS_USED_CLOUD_SERVICES.
CREDITS_ADJUSTMENT_CLOUD_SERVICES	NUMBER	Number of credits adjusted for 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.
REGION	VARCHAR	ID of the Snowflake Region where the account is located.
ACCOUNT_LOCATOR	VARCHAR	Locator for the account where the usage took place.

Usage notes¶

Latency for the view may be up to 120 minutes (2 hours).
The data is retained for 365 days (1 year).

Example¶

Usage for cloud services is billed only if the daily consumption of cloud services exceeds 10% of the daily usage of virtual warehouses. This query returns how much of cloud services consumption was actually billed for a particular day, ordered by the highest billed amount.

SELECT
    usage_date,
    credits_used_cloud_services,
    credits_adjustment_cloud_services,
    credits_used_cloud_services + credits_adjustment_cloud_services AS billed_cloud_services
FROM snowflake.organization_usage.metering_daily_history
WHERE usage_date >= DATEADD(month,-1,CURRENT_TIMESTAMP())
    AND credits_used_cloud_services > 0
ORDER BY 4 DESC;