SHOW TAGS¶
Lists the tag information.
- See also:
Syntax¶
SHOW TAGS [ LIKE '<pattern>' ]
[ IN
{
ACCOUNT |
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.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 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).
Access control requirements¶
A role used to execute this SQL command must have at least one of the following privileges at a minimum:
Privilege |
Object |
Notes |
---|---|---|
USAGE |
Schema |
This privilege must match the schema containing the tag. |
APPLY TAG |
Account |
Note that operating on any object in a schema also requires the USAGE privilege on the parent database and schema.
For instructions on creating a custom role with a specified set of privileges, see Creating custom roles.
For general information about roles and privilege grants for performing SQL actions on securable objects, see Overview of Access Control.
For additional details on tag DDL and privileges, see Managing tags.
Usage notes¶
The command does not require a running warehouse to execute.
The value for
LIMIT rows
cannot exceed10000
. IfLIMIT 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.
The ALLOWED_VALUES column specifies the possible string values that can be assigned to the tag when the tag is set on an object or NULL if the tag does not have any specified allowed values. For details, see Specify tag values.
Examples¶
Show tags in a given schema:
SHOW TAGS IN SCHEMA my_db.my_schema;Copy------------------------------+----------------+---------------+-------------+--------------+--------------------+----------------+-----------------+ created_on | name | database_name | schema_name | owner | comment | allowed_values | owner_role_type | ------------------------------+----------------+---------------+-------------+--------------+--------------------+----------------+-----------------+ 2021-03-20 21:09:38.317 +0000 | CLASSIFICATION | MY_DB | MY_SCHEMA | ACCOUNTADMIN | secure information | [NULL] | ROLE | 2021-03-20 21:08:59.000 +0000 | COST_CENTER | MY_DB | MY_SCHEMA | ACCOUNTADMIN | cost_center tag | [NULL] | ROLE | ------------------------------+----------------+---------------+-------------+--------------+--------------------+----------------+-----------------+