Schema:: ORGANIZATION_USAGE

AUTOMATIC_CLUSTERING_HISTORY view¶

The AUTOMATIC_CLUSTERING_HISTORY view in the ORGANIZATION_USAGE schema is used for querying the Automatic Clustering history for your organization’s tables within a specified date range. The information returned by the function includes the credits consumed, bytes updated, and rows updated each time a table is reclustered.

Columns¶

Column Name	Data Type	Description
ORGANIZATION_NAME	VARCHAR	Name of the organization in which the usage took place.
ACCOUNT_NAME	VARCHAR	Name of the account where the usage took place.
ACCOUNT_LOCATOR	VARCHAR	Name of the account locator.
REGION	VARCHAR	Name of the region where the account is located.
USAGE_DATE	DATE	Date when automatic clustering usage occurred.
CREDITS_USED	NUMBER	Number of credits billed for automatic clustering during the day specified by the USAGE_DATE value.
NUM_BYTES_RECLUSTERED	NUMBER	Number of bytes reclustered during the day specified by the USAGE_DATE value.
NUM_ROWS_RECLUSTERED	NUMBER	Number of rows reclustered during the day specified by the USAGE_DATE value.
TABLE_ID	NUMBER	Internal/system-generated identifier for the table.
TABLE_NAME	VARCHAR	Name of the table.
SCHEMA_ID	NUMBER	Internal/system-generated identifier for the schema that contains the table.
SCHEMA_NAME	VARCHAR	Name of the schema that contains the table.
DATABASE_ID	NUMBER	Internal/system-generated identifier for the database that contains the table.
DATABASE_NAME	VARCHAR	Name of the database that contains the table.

Usage notes¶

Latency for the view may be up to 24 hours (1 day).
The data is retained for 365 days (1 year).
A row might be clustered multiple times, depending on data skew, clustering key distribution, and reordering required for micro-partitions. A large table with poor initial clustering might need multiple passes to reach an optimally clustered state. Therefore, the NUM_ROWS_RECLUSTERED value for a table could be as high as the total number of rows in the table or even higher.