Categories:

Table, View, & Sequence DDL

SHOW SEQUENCES

Lists all the sequences for which you have access privileges. This command can be used to list the sequences for a specified schema or database (or the current schema/database for the session), or your entire account.

See also:

SEQUENCES View (Information Schema) , CREATE SEQUENCE , ALTER SEQUENCE , DROP SEQUENCE , DESCRIBE SEQUENCE

Syntax

SHOW SEQUENCES [ LIKE '<pattern>' ]
               [ IN
                    {
                      ACCOUNT                  |

                      DATABASE                 |
                      DATABASE <database_name> |

                      SCHEMA                   |
                      SCHEMA <schema_name>     |
                      <schema_name>
                    }
               ]

Parameters

LIKE 'pattern'

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%' ...
[ IN ... ]

Optionally specifies the scope of the command. Specify one of the following:

ACCOUNT

Returns records for the entire account.

DATABASE, . DATABASE db_name

Returns records for the current database in use or a specified database (db_name).

If you specify DATABASE without db_name and no database is in use, the keyword has no effect on the output.

SCHEMA, . SCHEMA schema_name, . schema_name

Returns records for the current schema in use or a specified schema (schema_name).

SCHEMA is optional if a database is in use or if you specify the fully-qualified schema_name (e.g. db.schema).

If no database is in use, specifying SCHEMA has no effect on the output.

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

  • Database: DATABASE is the default (i.e. the command returns the objects you have privileges to view in the database).

  • No database: ACCOUNT is the default (i.e. the command returns the objects you have privileges to view in your account).

Usage Notes

  • The command does not require a running warehouse to execute.

  • The command returns a maximum of 10K records for the specified object type, as dictated by the access privileges for the role used to execute the command; any records above the 10K limit are not returned, even with a filter applied.

    To view results for which more than 10K records exist, query the corresponding view (if one exists) 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.

Back to top