Schema:: ACCOUNT_USAGE

AUTOMATIC_CLUSTERING_HISTORY view¶

This Account Usage view can be used to query the Automatic Clustering history. The information returned by the view includes the credits consumed, bytes updated, and rows updated each time a table is reclustered.

Columns¶

Column Name	Data Type	Description
START_TIME	TIMESTAMP_LTZ	Start of the specified time range.
END_TIME	TIMESTAMP_LTZ	End of the specified time range.
CREDITS_USED	NUMBER	Number of credits billed for automatic clustering during the START_TIME and END_TIME window.
NUM_BYTES_RECLUSTERED	NUMBER	Number of bytes reclustered during the START_TIME and END_TIME window.
NUM_ROWS_RECLUSTERED	NUMBER	Number of rows reclustered during the START_TIME and END_TIME window.
TABLE_ID	NUMBER	Internal/system-generated identifier for the table.
TABLE_NAME	TEXT	Name of the table.
SCHEMA_ID	NUMBER	Internal/system-generated identifier for the schema that contains the table.
SCHEMA_NAME	TEXT	Name of the schema that contains the table.
DATABASE_ID	NUMBER	Internal/system-generated identifier for the database that contains the table.
DATABASE_NAME	TEXT	Name of the database that contains the table.
INSTANCE_ID	NUMBER	Internal/system-generated identifier for the instance that the object belongs to.

Usage notes¶

Latency for the view may be up to 180 minutes (3 hours).
If you want to reconcile the data in this view with a corresponding view in the ORGANIZATION USAGE schema, you must first set the timezone of the session to UTC. Before querying the Account Usage view, execute:
ALTER SESSION SET TIMEZONE = UTC;
Copy
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.