SHOW PROCEDURES¶
Lists all stored procedures that you have privileges to access, including built-in and user-defined procedures.
For a command that lists only user-defined procedures, see SHOW USER PROCEDURES.
- See also:
ALTER PROCEDURE , CREATE PROCEDURE , DROP PROCEDURE , DESCRIBE PROCEDURE
Syntax¶
SHOW PROCEDURES [ LIKE '<pattern>' ]
[ IN
{
ACCOUNT |
CLASS <class_name> |
DATABASE |
DATABASE <database_name> |
SCHEMA |
SCHEMA <schema_name> |
<schema_name>
APPLICATION <application_name> |
APPLICATION PACKAGE <application_package_name> |
}
]
Parameters¶
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 ... ]
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 for a specified database (
db_name
).If you specify
DATABASE
withoutdb_name
and no database is in use, the keyword has no effect on the output.Note
Using SHOW commands without an
IN
clause in a database context can result in fewer than expected results.Objects with the same name are only displayed once if no
IN
clause is used. For example, if you have tablet1
inschema1
and tablet1
inschema2
, and they are both in scope of the database context you’ve specified (that is, the database you’ve selected is the parent ofschema1
andschema2
), then SHOW TABLES only displays one of thet1
tables.SCHEMA
, .SCHEMA 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 qualifiedschema_name
(for example,db.schema
).If no database is in use, specifying
SCHEMA
has no effect on the output.
APPLICATION application_name
, .APPLICATION PACKAGE application_package_name
Returns records for the named Snowflake Native App or application package.
Default: Depends on whether the session currently has a database in use:
Database:
DATABASE
is the default (that is, the command returns the objects you have privileges to view in the database).No database:
ACCOUNT
is the default (that is, the command returns the objects you have privileges to view in your account).
Usage notes¶
The command doesn’t require a running warehouse to execute.
The command only returns objects for which the current user’s current role has been granted at least one access privilege.
The MANAGE GRANTS access privilege implicitly allows its holder to see every object in the account. By default, only the account administrator (users with the ACCOUNTADMIN role) and security administrator (users with the SECURITYADMIN role) have the MANAGE GRANTS privilege.
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 returns a maximum of ten thousand records for the specified object type, as dictated by the access privileges for the role used to execute the command. Any records above the ten thousand records limit aren’t returned, even with a filter applied.
To view results for which more than ten thousand records exist, query the corresponding view (if one exists) in the Snowflake Information Schema.
If you specify
CLASS
, the command only returns the following columns:| name | min_num_arguments | max_num_arguments | arguments | descriptions | language |
Output¶
The command output provides procedure properties and metadata in the following columns:
Column |
Description |
---|---|
|
Timestamp at which the stored procedure was created. |
|
Name of the stored procedure. |
|
Name of the schema in which the stored procedure exists. |
|
|
|
Not applicable currently. |
|
|
|
Minimum number of arguments. |
|
Maximum number of arguments. |
|
Data types of the arguments and of the return types. Optional arguments are displayed with the |
|
Description of the stored procedure. |
|
Name of the database in which the stored procedure exists. |
|
|
|
Not applicable currently. |
|
|
Examples¶
Show all procedures:
SHOW PROCEDURES;
This example shows how to use SHOW PROCEDURE
on a stored procedure that has a parameter. This also shows how to limit the list of
procedures to those that match the specified regular expression.
SHOW PROCEDURES LIKE 'area_of_%';
+-------------------------------+----------------+--------------------+------------+--------------+---------+-------------------+-------------------+------------------------------------+------------------------+-----------------------+-------------------+----------------------+-----------+
| created_on | name | schema_name | is_builtin | is_aggregate | is_ansi | min_num_arguments | max_num_arguments | arguments | description | catalog_name | is_table_function | valid_for_clustering | is_secure |
|-------------------------------+----------------+--------------------+------------+--------------+---------+-------------------+-------------------+------------------------------------+------------------------+-----------------------+-------------------+----------------------+-----------|
| 1967-06-23 00:00:00.123 -0700 | AREA_OF_CIRCLE | TEMPORARY_DOC_TEST | N | N | N | 1 | 1 | AREA_OF_CIRCLE(FLOAT) RETURN FLOAT | user-defined procedure | TEMPORARY_DOC_TEST_DB | N | N | N |
+-------------------------------+----------------+--------------------+------------+--------------+---------+-------------------+-------------------+------------------------------------+------------------------+-----------------------+-------------------+----------------------+-----------+
The output columns are similar to the output columns for SHOW FUNCTIONS and
SHOW USER FUNCTIONS. For stored procedures, some of these columns are not currently meaningful
(e.g. is_aggregate
, valid_for_clustering
), but are reserved for future use.