Premium views in the organization account

The ORGANIZATION_USAGE schema contains views that provide organization-level data. The ORGANIZATION_USAGE schema in the organization account contains views that are not available in the ORGANIZATION_USAGE schema of a regular account. These views are considered premium views because they aggregate usage and object data from all accounts into a single view that is not otherwise available, and therefore incur additional costs.

Premium views correspond to views in the ACCOUNT_USAGE schema, but provide organization-level data rather than account-level data. For example, someone could query the TAG_REFERENCES view in the ACCOUNT_USAGE schema to learn about how tags are used in a specific account, but someone could query the TAG_REFERENCES view in the ORGANIZATION_USAGE schema of the organization account to learn how tags are used throughout the organization.

Note

It can take two weeks from the time the organization account is created until premium views are fully populated with 365 days of historical data from accounts.

Costs associated with premium views

Premium views incur the following costs:

  • Storage costs associated with storing the data in the views.

  • Compute costs associated with the serverless tasks that populate the views with data. When you create the organization account, premium views are backfilled with one year of historical data, which results in a temporary spike in compute costs. After the initial backfill, you pay for the compute resources used to update the views with new data.

Views found in the ORGANIZATION_USAGE schema of a regular account (that is, non-premium views) do not incur cost in the organization account.

Note

If you want to lower costs by removing premium views, contact Snowflake Support.

You can use the following queries to return the historical costs associated with the ORGANIZATION_USAGE schema in the organization account.

Compute costs

If you can access the METERING_DAILY_HISTORY view in the ORGANIZATION_USAGE schema, you can execute the following query to determine the cost of populating the views. You must execute the query in the organization account.

SELECT * FROM snowflake.organization_usage.metering_daily_history
  WHERE service_type = 'ORGANIZATION_USAGE';
Copy

If you prefer to see the costs in currency rather than credits, run the query against the USAGE_IN_CURRENCY_DAILY view. Filter the service_type column to focus on ORGANIZATION_USAGE.

Storage costs

If you have access to the TABLE_STORAGE_METRICS view in the ORGANIZATION_USAGE schema, you can execute the following query to determine the approximate amount of storage in TBs. You must execute the query in the organization account.

SELECT
  SUM(active_bytes + time_travel_bytes + failsafe_bytes + retained_for_clone_bytes) / pow(1000, 4)
    AS org_usage_approx_storage_tb
  FROM snowflake.organization_usage.table_storage_metrics
  WHERE 1=1
    AND table_schema = 'ORGANIZATION_USAGE_LOCAL';
Copy

Grant access to the premium views

For information about granting access to premium views, see Access schema in the organization account.

Effect on views in the ACCOUNT_USAGE schema

Snowflake uses the hidden schema snowflake.organization_usage_local to store internal objects used in conjunction with premium views. These objects might be visible in the ACCOUNT_USAGE views in the organization account. Because these objects are internal, they might change without notice in the future.

Language: English