- Schema:
For guidance on query performance when using organization-wide usage views, see Performance (Organization Usage).
TABLE_
Important
This view is only available in the organization account. For more information, see Premium views in the organization account.
Organization Usage performance
When you query a specific view in the SNOWFLAKE.ORGANIZATION_USAGE schema, follow the organization-wide guidance in
Performance (Organization Usage): bound every scan on history views, list
columns explicitly, and use the time filter column table plus worked SQL and anti-patterns there.
This Organization Usage view can be used to determine the magnitude and effects of the DML operations performed on a table. Note that these DML operations include ones initiated by Snowpipe but exclude operations initiated by background maintenance services (for example, Automatic Clustering, maintenance for materialized views and search optimization).
You can query this view with the QUERY_HISTORY view and the LOAD_HISTORY view to identify the DML operations that have a significant impact. This can help you to identify opportunities for optimization.
In addition, you can query this view with the AUTOMATIC_CLUSTERING_HISTORY view and the SEARCH_OPTIMIZATION_HISTORY view to visualize the relationship between these DML operations and the credits charged for Automatic Clustering and the search optimization service. (These services can be triggered by DML operations.)
Columns¶
Organization-level columns
| Column Name | Data Type | Description |
|---|---|---|
| ORGANIZATION_NAME | VARCHAR | Name of the organization. |
| ACCOUNT_LOCATOR | VARCHAR | System-generated identifier for the account. |
| ACCOUNT_NAME | VARCHAR | User-defined identifier for the account. |
Additional columns
| Column Name | Data Type | Description |
|---|---|---|
| START_TIME | TIMESTAMP_LTZ | Start of the time range (on the hour mark) during which the DML operations were performed. |
| END_TIME | TIMESTAMP_LTZ | End of the time range (on the hour mark) during which the DML operations were performed. |
| TABLE_ID | NUMBER | Internal/system-generated identifier for the table modified by the DML operations. |
| TABLE_NAME | VARCHAR | Name of the table modified by the DML operations. |
| SCHEMA_ID | NUMBER | Internal/system-generated identifier for the schema that contains the table modified by the DML operations. |
| SCHEMA_NAME | VARCHAR | Name of the schema that contains the table modified by the DML operations. |
| DATABASE_ID | NUMBER | Internal/system-generated identifier for the database that contains the table modified by the DML operations. |
| DATABASE_NAME | VARCHAR | Name of the database that contains the table modified by the DML operations. |
| ROWS_ADDED | NUMBER | Number of rows added by DML operations performed by users on the table during the START_TIME and END_TIME window. |
| ROWS_REMOVED | NUMBER | Number of rows removed by DML operations performed by users on the table during the START_TIME and END_TIME window. |
| ROWS_UPDATED | NUMBER | Number of rows updated by DML operations performed by users on the table during the START_TIME and END_TIME window. |
Usage notes¶
- Latency for the view may be up to 8 hours.
- This view does not include DML operations on hybrid tables.