TABLES View¶

This Information Schema view displays a row for each table and view in the specified (or current) database, including the views in the INFORMATION_SCHEMA schema itself.

See also:: COLUMNS View , VIEWS View

Columns¶

Column Name	Data Type	Description
TABLE_CATALOG	TEXT	Database that the table belongs to.
TABLE_SCHEMA	TEXT	Schema that the table belongs to.
TABLE_NAME	TEXT	Name of the table.
TABLE_OWNER	TEXT	Name of the role that owns the table.
TABLE_TYPE	TEXT	Indicates the table type. Valid values are `BASE TABLE`, `TEMPORARY TABLE`, `EXTERNAL TABLE`, `EVENT TABLE`, `VIEW`, or `MATERIALIZED VIEW`.
IS_TRANSIENT	TEXT	Indicates whether this is a transient table.
CLUSTERING_KEY	TEXT	Clustering key for the table.
ROW_COUNT	NUMBER	Number of rows in the table.
BYTES	NUMBER	Number of bytes accessed by a scan of the table.
RETENTION_TIME	NUMBER	Number of days that historical data is retained for Time Travel.
SELF_REFERENCING_COLUMN_NAME	TEXT	Not applicable for Snowflake.
REFERENCE_GENERATION	TEXT	Not applicable for Snowflake.
USER_DEFINED_TYPE_CATALOG	TEXT	Not applicable for Snowflake.
USER_DEFINED_TYPE_SCHEMA	TEXT	Not applicable for Snowflake.
USER_DEFINED_TYPE_NAME	TEXT	Not applicable for Snowflake.
IS_INSERTABLE_INTO	TEXT	Not applicable for Snowflake.
IS_TYPED	TEXT	Not applicable for Snowflake.
COMMIT_ACTION	TEXT	Not applicable for Snowflake.
CREATED	TIMESTAMP_LTZ	Creation time of the table.
LAST_ALTERED	TIMESTAMP_LTZ	Date and time the object was last altered. See Usage Notes.
LAST_DDL	TIMESTAMP_LTZ	Timestamp of the last DDL operation performed on the table or view. All supported table/view DDL operations update this field: { CREATE \| ALTER \| DROP \| UNDROP } TABLE { CREATE \| ALTER \| DROP } VIEW All ALTER TABLE operations update this field, including setting or unsetting a table parameter (for example, COMMENT, DATA_RETENTION_TIME, etc.) and changes to table columns (ADD / MODIFY / RENAME / DROP). For more information, see the Usage Notes.
LAST_DDL_BY	TEXT	The current username for the user who executed the last DDL operation. If the user has been dropped, shows `DROPPED_USER(<id>)`. For dropped users, you can join the `<id>` with the USER_ID column in the USERS View.
AUTO_CLUSTERING_ON	BOOLEAN	Indicates whether automatic clustering is enabled for the table.
COMMENT	TEXT	Comment for this table.
IS_TEMPORARY	TEXT	Indicates whether this is a temporary table. Valid values are `YES` and `NO`.

Usage Notes¶

The view only displays objects for which the current role for the session has been granted access privileges. The view does not honor the MANAGE GRANTS privilege and consequently may show less information compared to a SHOW command when both are executed with a role that was granted the MANAGE GRANTS privilege.

This behavior also applies to other account-level privileges and Information Schema views for which there is a corresponding SHOW command.
Querying the sum(bytes) for a table does not represent the total storage usage, because the amount does not include Time Travel and Fail-safe usage.
The view does not include tables that have been dropped. To view dropped tables, use SHOW TABLES instead.
To view only tables in your queries, filter using a WHERE clause, e.g.:

... WHERE table_schema != 'INFORMATION_SCHEMA'
The LAST_ALTERED column is updated when the following operations are performed on an object:
- DDL operations.
- DML operations (for tables only).
- Background maintenance operations on metadata performed by Snowflake.
For views and tables, use the LAST_DDL column for the last modification time for an object.
The value in the LAST_DDL column is updated as follows:
- When a table or view is created, the LAST_DDL timestamp is the same as the CREATED timestamp.
- When a table or view is dropped, the LAST_DDL timestamp is the same as the DELETED timestamp.
- Last DDL data is not available for operations that occurred before the columns were added. The new DDL fields contain null until a DDL operation is executed.
- For replicated databases, the LAST_DDL and LAST_DDL_BY fields are only updated for objects in the primary database. After failover, the LAST_DDL and LAST_DDL_BY fields are updated for DDL operations for the tables and views in the newly promoted primary database. These fields will remain unchanged for objects in the now secondary database.
- For objects in secondary databases that are newly created during a refresh operation, these fields are null.

Examples¶

Retrieve the size (in bytes) of all tables in all schemas in the mydatabase database:

SELECT TABLE_SCHEMA,SUM(BYTES)
    FROM mydatabase.information_schema.tables
    GROUP BY TABLE_SCHEMA;

Copy