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 NameData TypeDescription
ORGANIZATION_NAMEVARCHARName of the organization in which the usage took place.
ACCOUNT_NAMEVARCHARName of the account where the usage took place.
ACCOUNT_LOCATORVARCHARName of the account locator.
REGIONVARCHARName of the region where the account is located.
USAGE_DATEDATEDate when automatic clustering usage occurred.
CREDITS_USEDNUMBERNumber of credits billed for automatic clustering during the day specified by the USAGE_DATE value.
NUM_BYTES_RECLUSTEREDNUMBERNumber of bytes reclustered during the day specified by the USAGE_DATE value.
NUM_ROWS_RECLUSTEREDNUMBERNumber of rows reclustered during the day specified by the USAGE_DATE value.
TABLE_IDNUMBERInternal/system-generated identifier for the table.
TABLE_NAMEVARCHARName of the table.
SCHEMA_IDNUMBERInternal/system-generated identifier for the schema that contains the table.
SCHEMA_NAMEVARCHARName of the schema that contains the table.
DATABASE_IDNUMBERInternal/system-generated identifier for the database that contains the table.
DATABASE_NAMEVARCHARName 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.