Data Loading / Unloading DDL


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

See also:



SHOW PIPES [ LIKE '<pattern>' ]
           [ IN { ACCOUNT | [ DATABASE ] <db_name> | [ SCHEMA ] <schema_name> } ]


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 ACCOUNT | [ DATABASE ] db_name | [ SCHEMA ] schema_name

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:

The DATABASE or SCHEMA keyword is not required; you can set the scope by specifying only the database or schema name. Likewise, the database or schema name is not required if the session currently has a database in use:

  • If DATABASE or SCHEMA is specified without a name and the session does not currently have a database in use, the parameter has no effect on the output.

  • If SCHEMA is specified with a name and the session does not currently have a database in use, the schema name must be fully qualified with the database name (e.g. testdb.testschema).

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

  • Returns results only for the pipe owner (i.e. the role with the OWNERSHIP privilege on the pipe), a role with the MONITOR or OPERATE privilege on the pipe, or a role with the global MONITOR EXECUTION privilege.

  • To determine the current status of a pipe, query the SYSTEM$PIPE_STATUS function.

  • 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.


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

| created_on | name | database_name | schema_name | definition | owner | notification_channel | comment | integration | pattern | error_integration |




Date and time when the pipe was created.


Name of the pipe.


Database in which the pipe is stored.


Schema in which the pipe is stored.


COPY statement used to load data from queued files into a Snowflake table.


Name of the role that owns the pipe (i.e. that has the OWNERSHIP privilege on the pipe).


Amazon Resource Name of the Amazon SQS queue for the stage named in the DEFINITION column.


Comment for this pipe.


Name of the notification integration for pipes that rely on notification events to trigger data loads from Google Cloud Storage or Microsoft Azure cloud storage.


PATTERN copy option value in the COPY INTO <table> statement in the pipe definition, if the copy option was specified.


Notification integration name for pipes that rely on error events in Amazon S3 cloud storage to trigger notifications.


Show all the pipes that you have privileges to view in the public schema in the mydb database:

use database mydb;

show pipes;
Back to top