Performance Monitoring and Tuning · Topic 11 of 16

Organization Costs and the Usage Views

Manage Snowflake costs across an organization: ACCOUNT_USAGE against ORGANIZATION_USAGE, who can query them, key views, latency and how to monitor usage.

  • 4 min
In a nutshell
  • ACCOUNT_USAGE: one account, latency 45 minutes to 3 hours, 1 year retention, includes dropped objects.
  • ORGANIZATION_USAGE: all accounts, in the organization account or an ORGADMIN enabled account.
  • In the organization account, GLOBALORGADMIN queries it by default; other roles get application or database roles.

What it is

Cost management starts with knowing where to look. Snowflake exposes usage data in the shared SNOWFLAKE database, in two schemas that answer different questions.

ACCOUNT_USAGE describes one account: its warehouses, queries, storage and logins. ORGANIZATION_USAGE describes every account in the organization, which is what you need for chargeback, contract balance and cross account comparison.

An administrator is asked "which view, which role, and how fresh is the data". The facts below settle most of those questions.

Questionone account or the whole organizationone accountACCOUNT_USAGESNOWFLAKE databasemany accountsORGANIZATION_USAGEorganization account or ORGADMIN account

How it works

ACCOUNT_USAGE against ORGANIZATION_USAGE

PointACCOUNT_USAGEORGANIZATION_USAGE
ScopeThe current accountAll accounts of the organization
Where it livesThe SNOWFLAKE database of every accountThe organization account, and any regular account where the ORGADMIN role is enabled
Typical useWarehouse credits, query history, storage, grants, loginsCredits and storage per account, currency amounts, contract balance, data transfer across accounts
Latency45 minutes to 3 hours depending on the viewPer view; from about 2 hours up to 72 hours
Retention1 year for historical views1 year for historical views

Latency numbers are maximums, so the data can show up sooner. Neither schema is real time. For an up to the minute view of one warehouse use INFORMATION_SCHEMA table functions, covered on a later page.

Who can query ORGANIZATION_USAGE

In the organization account, only the GLOBALORGADMIN role can query the schema by default. Other roles get the SNOWFLAKE.ORG_USAGE_ADMIN application role for full access, or a narrower viewer role.

In a regular account with ORGADMIN enabled, anyone with access to the shared SNOWFLAKE database can query the schema. By default only ACCOUNTADMIN has that, so ORGADMIN needs the privileges granted. Non admins use one of the database roles ORGANIZATION_USAGE_VIEWER, ORGANIZATION_BILLING_VIEWER or ORGANIZATION_ACCOUNTS_VIEWER.

Watch out

Granting IMPORTED PRIVILEGES on the SNOWFLAKE database can expose organization level data. Granting database roles is the narrower way and avoids that accident.

The schema is not available in US SnowGov regions.

Key ORGANIZATION_USAGE views

ViewUseLatencyRole needed
METERING_DAILY_HISTORYDaily credits per account and service type2 hoursORGANIZATION_USAGE_VIEWER
WAREHOUSE_METERING_HISTORYWarehouse credits per account24 hoursORGANIZATION_USAGE_VIEWER
STORAGE_DAILY_HISTORYDaily storage per account2 hoursORGANIZATION_USAGE_VIEWER
DATA_TRANSFER_HISTORYData transfer between regions and clouds24 hoursORGANIZATION_USAGE_VIEWER
REPLICATION_USAGE_HISTORYReplication credits and bytes24 hoursORGANIZATION_USAGE_VIEWER
USAGE_IN_CURRENCY_DAILYUsage converted to currency72 hoursORGANIZATION_BILLING_VIEWER
REMAINING_BALANCE_DAILYRemaining contract capacity72 hoursORGANIZATION_BILLING_VIEWER

USAGE_IN_CURRENCY_DAILY and REMAINING_BALANCE_DAILY do not show final amounts, because some adjustments happen at month end. Customers who signed through a Snowflake reseller cannot use these two views.

Some views are marked premium, such as METERING_HISTORY with latency under 15 minutes. USER_AI_USAGE_HISTORY is a premium view available only in the organization account.

Managing organization costs

Typical administrator work at organization level:

  • List accounts and their spend from ORGANIZATION_USAGE instead of logging in to each account.
  • Convert credits to currency with USAGE_IN_CURRENCY_DAILY, and watch the contract balance in REMAINING_BALANCE_DAILY.
  • Compare accounts and find the one whose warehouse, storage or transfer cost grows fastest.
  • Attribute cost inside an account with tags or query tags, then group by them in ACCOUNT_USAGE.

If you reconcile ACCOUNT_USAGE cost views against ORGANIZATION_USAGE, set the session time zone to UTC first. Both report by UTC days, and a local time zone shifts rows across day borders.

Monitoring accounts and usage

Inside one account, three tools cover most questions:

ToolBest for
Snowsight Cost Management (Admin, Cost management)Visual consumption by type, service, resource or tag
ACCOUNT_USAGE views such as METERING_HISTORY, WAREHOUSE_METERING_HISTORY, STORAGE_USAGE, QUERY_HISTORYCustom queries, joins and alerts
INFORMATION_SCHEMA table functionsFresh data with no latency, short history

Snowflake suggests an XS warehouse for the Cost Management pages, because the queries behind them are small.

Spend questionwhich account?ORGANIZATION_USAGEMETERING_DAILY_HISTORYwhich warehouse or service?ACCOUNT_USAGEWAREHOUSE_METERING_HISTORYwhich query or user?QUERY_HISTORYtags and query tags

Common mistakes

Using ACCOUNT_USAGE to compare all accounts. It sees only the current account. Use ORGANIZATION_USAGE.

Expecting current minute data. Account usage views lag by up to 3 hours, and some organization views by up to 72 hours.

Granting IMPORTED PRIVILEGES to give a team cost access. That can expose organization level data; use database roles.

Treating currency views as final invoices. Month end adjustments are not yet included.

What to remember for the exam

  • ACCOUNT_USAGE: one account, latency 45 minutes to 3 hours, 1 year retention, includes dropped objects.
  • ORGANIZATION_USAGE: all accounts, in the organization account or an ORGADMIN enabled account.
  • In the organization account, GLOBALORGADMIN queries it by default; other roles get application or database roles.
  • Currency and balance views (USAGE_IN_CURRENCY_DAILY, REMAINING_BALANCE_DAILY) have 72 hours latency and are not final.
  • Set the session time zone to UTC when reconciling the two schemas.

Check yourself

  • Which schema shows credits for every account of the organization?

    ORGANIZATION_USAGE, available in the organization account or an account with ORGADMIN enabled.

  • How can a finance analyst read billing views without seeing everything in the SNOWFLAKE database?

    Grant the ORGANIZATION_BILLING_VIEWER database role instead of IMPORTED PRIVILEGES.

  • Why do totals from the two schemas sometimes not match?

    Different latency, month end adjustments and time zones; set the session to UTC when comparing.

Topic 11 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.