Organization Usage¶
Snowflake provides historical usage data for all accounts in your organization via the ORGANIZATION_USAGE schema in a shared database named SNOWFLAKE.
Note
This topic discusses the ORGANIZATION_USAGE schema in a regular account. If you are working with the ORGANIZATION_USAGE schema in an organization account, including accessing premium views that aren’t available in a regular account, see Organization accounts.
ORGANIZATION_USAGE views¶
The ORGANIZATION_USAGE schema contains the following views:
View |
Type |
Latency [1] |
Notes |
---|---|---|---|
Object |
24 hours |
||
Historical |
24 hours |
Data retained for 1 year. |
|
CONTRACT_ITEMS [2] |
Historical |
24 hours |
|
Historical |
2 hours |
Data retained for 1 year. |
|
Historical |
24 hours |
Data retained for 1 year. |
|
Historical |
24 hours |
Data retained for 1 year. |
|
Historical |
72 hours |
Data retained for 1 year. |
|
Historical |
24 hours |
Data retained for 1 year. |
|
Historical |
24 hours |
Data retained for 1 year. |
|
Historical |
24 hours |
Data retained for 1 year. |
|
Historical |
2 hours |
Data retained for 1 year. |
|
Historical |
24 hours |
Data retained for 1 year. |
|
Historical |
24 hours |
Data retained for 1 year. |
|
Historical |
24 hours |
Data retained for 1 year. |
|
RATE_SHEET_DAILY [2] |
Historical |
24 hours |
|
Historical |
72 hours |
||
Historical |
24 hours |
Data retained for 1 year. |
|
Historical |
24 hours |
Data retained for 1 year. |
|
Historical |
24 hours |
Data retained for 1 year. |
|
Historical |
24 hours |
Data retained for 1 year. |
|
Historical |
2 hours |
Data retained for 1 year. |
|
Historical |
72 hours |
||
Historical |
24 hours |
Data retained for 1 year. |
[1] All latency times are approximate; in some instances, the actual latency may be lower.
[2] The organization billing views do not display the actual, final amount because some adjustments are made at the end of the month. Customers who signed a contract through a Snowflake reseller cannot access data in these views.
Accessing the ORGANIZATION_USAGE schema¶
To view data in the ORGANIZATION_USAGE schema, you can do either of the following:
Access the data from the organization account.
Access the data from a regular, ORGADMIN-enabled account. Within the ORGADMIN-enabled account, anyone who has access to the shared SNOWFLAKE database has access to the ORGANIZATION_USAGE schema. By default, only the ACCOUNTADMIN role has privileges to this database, which means the ORGADMIN role does not have the necessary privileges. To grant these privileges to the ORGADMIN role, see Enabling other roles to use schemas in the SNOWFLAKE database.
Note
The views in the ORGANIZATION_USAGE schema are currently not available in US SnowGov Regions on AWS GovCloud and Microsoft Azure Government.
Grant access to non-administrators¶
How you grant access to non-administrators depends on whether they are accessing ORGANIZATION_USAGE views in the organization account or a regular account.
In the organization account, an administrator uses application roles to grant access to non-administrators. For information, see Grant access to the Organization Usage views.
In a regular, ORGADMIN-enabled account, an administrator uses SNOWFLAKE database roles to grant access to non-administrators.
SNOWFLAKE database roles¶
The ORGANIZATION_USAGE_VIEWER, ORGANIZATION_BILLING_VIEWER, and ORGANIZATION_ACCOUNTS_VIEWER SNOWFLAKE database roles are granted the SELECT privilege on Organization Usage views in the shared SNOWFLAKE database.
View |
ORGANIZATION_BILLING_VIEWER Role |
ORGANIZATION_USAGE_VIEWER Role |
ORGANIZATION_ACCOUNTS_VIEWER Role |
---|---|---|---|
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
|||
✔ |
For more information, refer to GRANT DATABASE ROLE.
General usage notes¶
The Snowflake-specific views are subject to change. Avoid selecting all columns from these views. Instead, select the columns that you want.
For example, if you want the name
column, use SELECT name
, rather than SELECT *
.