SHOW HYBRID TABLES¶

Lists the hybrid tables for which you have access privileges.

The command can be used to list hybrid tables for the current/specified database or schema, or across your entire account.

This command returns different output columns than SHOW TABLES.

The output returns hybrid table metadata and properties, ordered lexicographically by database, schema, and the name of the hybrid table (see Output in this topic for descriptions of the output columns). This is important to note if you wish to filter the results using the provided filters.

Note that this topic refers to hybrid tables as simply “tables” except where specifying hybrid tables avoids confusion.

See also:: CREATE INDEX, DROP INDEX , SHOW INDEXES , CREATE HYBRID TABLE , DROP TABLE , DESCRIBE TABLE

Syntax¶

SHOW [ TERSE ] [ HYBRID ] TABLES [ LIKE '<pattern>' ]
                                 [ IN { ACCOUNT | DATABASE [ <db_name> ] | SCHEMA [ <schema_name> ] } ]
                                 [ STARTS WITH '<name_string>' ]
                                 [ LIMIT <rows> [ FROM '<name_string>' ] ]

Copy

Parameters¶

TERSE

Optionally returns only a subset of the output columns:

created_on
name
kind

The kind column value is always HYBRID TABLE.
database_name
schema_name

Default: No value (all columns are included in the output)

HYBRID

Returns hybrid tables only.

LIKE 'pattern'

Optionally filters the command output by object name. The filter uses case-insensitive pattern matching, with support for SQL wildcard characters (% and _).

For example, the following patterns return the same results:

... LIKE '%testing%' ...

... LIKE '%TESTING%' ...

. Default: No value (no filtering is applied to the output).

IN ACCOUNT | DATABASE [ db_name ] | SCHEMA [ schema_name ]

Optionally specifies the scope of the command, which determines whether the command lists records only for the current/specified database or schema, or across your entire account.

If you specify the keyword ACCOUNT, then the command retrieves records for all schemas in all databases of the current account.

If you specify the keyword DATABASE, then:

If you specify a db_name, then the command retrieves records for all schemas of the specified database.
If you do not specify a db_name, then:
- If there is a current database, then the command retrieves records for all schemas in the current database.
- If there is no current database, then the command retrieves records for all databases and schemas in the account.

If you specify the keyword SCHEMA, then:

If you specify a qualified schema name (e.g. my_database.my_schema), then the command retrieves records for the specified database and schema.
If you specify an unqualified schema_name, then:
- If there is a current database, then the command retrieves records for the specified schema in the current database.
- If there is no current database, then the command displays the error SQL compilation error: Object does not exist, or operation cannot be performed.
If you do not specify a schema_name, then:
- If there is a current database, then:
  - If there is a current schema, then the command retrieves records for the current schema in the current database.
  - If there is no current schema, then the command retrieves records for all schemas in the current database.
- If there is no current database, then the command retrieves records for all databases and all schemas in the account.

Default: Depends on whether the session currently has a database in use:

Database: DATABASE is the default. The command returns the objects you have privileges to view in the current database.
No database: ACCOUNT is the default. The command returns the objects you have privileges to view in your account.

STARTS WITH 'name_string'

Optionally filters the command output based on the characters that appear at the beginning of the object name. The string must be enclosed in single quotes and is case-sensitive.

For example, the following strings return different results:

... STARTS WITH 'B' ...

... STARTS WITH 'b' ...

. Default: No value (no filtering is applied to the output)

LIMIT rows [ FROM 'name_string' ]

Optionally limits the maximum number of rows returned, while also enabling “pagination” of the results. The actual number of rows returned might be less than the specified limit. For example, the number of existing objects is less than the specified limit.

The optional FROM 'name_string' subclause effectively serves as a “cursor” for the results. This enables fetching the specified number of rows following the first row whose object name matches the specified string:

The string must be enclosed in single quotes and is case-sensitive.
The string does not have to include the full object name; partial names are supported.

Default: No value (no limit is applied to the output)

Note

For SHOW commands that support both the FROM 'name_string' and STARTS WITH 'name_string' clauses, you can combine both of these clauses in the same statement. However, both conditions must be met or they cancel out each other and no results are returned.

In addition, objects are returned in lexicographic order by name, so FROM 'name_string' only returns rows with a higher lexicographic value than the rows returned by STARTS WITH 'name_string'.

For example:

... STARTS WITH 'A' LIMIT ... FROM 'B' would return no results.
... STARTS WITH 'B' LIMIT ... FROM 'A' would return no results.
... STARTS WITH 'A' LIMIT ... FROM 'AB' would return results (if any rows match the input strings).

Usage notes¶

If an account (or database or schema) has a large number of hybrid tables, then searching the entire account (or database or schema) can consume a significant amount of compute resources.

The command does not require a running warehouse to execute.
The value for LIMIT rows cannot exceed 10000. If LIMIT rows is omitted, the command results in an error if the result set is larger than 10K rows.

To view results for which more than 10K records exist, either include LIMIT rows or query the corresponding view in the Snowflake Information Schema.

To post-process the output of this command, you can use the RESULT_SCAN function, which treats the output as a table that can be queried.

Output¶

Note

The following output schema is for the SHOW HYBRID TABLES command. For information about the output of SHOW TABLES, see Identifying hybrid tables with SHOW TABLES (in this topic).

The command output provides table properties and metadata in the following columns:

Column	Description
`created_on`	Date and time when the table was created.
`name`	Name of the table.
`database_name`	Database in which the table is stored.
`schema_name`	Schema in which the table is stored.
`owner`	Role that owns the table.
`rows`	Number of rows in the table.
`bytes`	Number of bytes that will be scanned if the entire table is scanned in a query. Note that this number may be different than the number of actual physical bytes (i.e. bytes stored on-disk) for the table.
`comment`	Comment for the table.
`owner_role_type`	The type of role that owns the object, either `ROLE` or `DATABASE_ROLE`. . If a Snowflake Native App owns the object, the value is `APPLICATION`. . Snowflake returns NULL if you delete the object because a deleted object does not have an owner role.

Note

Numbers in the rows and bytes columns may not appear accurate if data is changing on a constant basis. For example, such change may take place if new data is being continuously inserted into the hybrid table.

Examples¶

Show all the hybrid tables whose name starts with product_ that you have privileges to view in the mydb.myschema schema:

SHOW HYBRID TABLES LIKE 'product_%' IN mydb.myschema;

Copy

Identifying hybrid tables with SHOW TABLES¶

The SHOW TABLES command output has a column that indicates whether a table is a hybrid table.

This column appears in addition to the regular SHOW TABLES output columns.

The column has the following name and possible values:

Column Name	Values
is_hybrid	`Y` if the table is a hybrid table `N` otherwise.