Lists the dbt project objects for which you have access privileges.
You can use this command to list objects in the current database and schema for the session, a specified database or schema, or your entire account.
The output includes the metadata and properties for each object. The objects are sorted lexicographically by database, schema, and object name (see Output in this topic for descriptions of the output columns). The order is important to note if you want to filter the results.
CREATE DBT PROJECT, ALTER DBT PROJECT, EXECUTE DBT PROJECT, DROP DBT PROJECT, SHOW DBT PROJECTS
SHOW DBT PROJECTS [ LIKE '<pattern>' ]
[ IN
{
ACCOUNT |
DATABASE |
DATABASE <database_name> |
SCHEMA |
SCHEMA <schema_name> |
<schema_name>
}
]
[ STARTS WITH '<name_string>' ]
[ LIMIT <rows> ]
[ LIMIT <rows> [ FROM '<name_string>' ] ]
Copy
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 without db_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 table t1 in schema1 and table t1 in schema2, and they are both in scope of the database context you’ve specified (that is, the database you’ve selected is the parent of schema1 and schema2), then SHOW TABLES only displays one of the t1 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 qualified schema_name (for example, 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 (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).
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
Optionally limits the maximum number of rows returned. 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.
Default: No value (no limit 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).
The output of the command includes the following columns, which describe the properties and metadata of the object:
Column
Description
name
The identifier of the dbt project object.
database_name
The name of the database in which the dbt project object is defined.
schema_name
The name of the schema in which the dbt project object is defined.
created_on
Date and time when the dbt project object was created.
updated_on
Date and time when the dbt project object was last updated.
owner
The name of the role that owns the dbt project object.
comment
The comment associated with the dbt project object.
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
USAGE
dbt project
MONITOR
dbt project
The USAGE privilege on the parent database and schema are required to perform operations on any object in a 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.
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 pipe operator (->>) or the RESULT_SCAN function. Both constructs treat the output as a result set that you can query.
The output column names for this command are generated in lowercase. If you consume a result set from this command with the pipe operator or the RESULT_SCAN function, use double-quoted identifiers for the column names in the query to ensure that they match the column names in the output that was scanned. For example, if the name of an output column is type, then specify "type" for the identifier.
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.
The value for LIMIT rows can’t exceed 10000. If LIMIT rows is omitted, the command results in an error if the result set is larger than ten thousand rows.
To view results for which more than ten thousand records exist, either include LIMIT rows or query the corresponding view in the Snowflake Information Schema.
The following example lists the dbt project objects that you have privileges to view in the PUBLIC schema of the MY_DB database:
SHOW DBT PROJECTS IN DATABASE my_db;
Copy
+---------------------+---------------+-------------+-------------------------------+-------------------------------+--------------+---------+--------------+ | name | database_name | schema_name | created_on | updated_on | owner | comment | default_args | +---------------------+---------------+-------------+-------------------------------+-------------------------------+--------------+---------+--------------+ | COSMOS | MY_DB | PUBLIC | 2025-04-29 17:21:25.413 -0700 | 2025-04-29 17:21:29.462 -0700 | ACCOUNTADMIN | | | | COSMOS2 | MY_DB | PUBLIC | 2025-05-19 14:30:55.204 -0700 | 2025-05-19 14:30:57.106 -0700 | ACCOUNTADMIN | | | | JAFFLE_SHOP2 | MY_DB | PUBLIC | 2025-05-02 16:10:49.577 -0700 | 2025-05-02 16:10:51.844 -0700 | ACCOUNTADMIN | | | | Jaffle_shop | MY_DB | PUBLIC | 2025-03-25 12:36:16.574 -0700 | 2025-03-25 12:36:17.833 -0700 | ACCOUNTADMIN | | | | MY_DB_PROJECT | MY_DB | PUBLIC | 2025-05-02 13:42:36.306 -0700 | 2025-05-02 13:42:38.584 -0700 | ACCOUNTADMIN | | | | MY_SHOP | MY_DB | PUBLIC | 2025-04-29 17:15:27.295 -0700 | 2025-04-29 17:15:28.709 -0700 | ACCOUNTADMIN | | | | jaffle2 | MY_DB | PUBLIC | 2025-04-18 09:34:54.804 -0700 | 2025-04-18 09:34:57.416 -0700 | ACCOUNTADMIN | | | | task_query_analysis | MY_DB | PUBLIC | 2025-04-21 20:50:37.579 -0700 | 2025-04-21 20:50:39.239 -0700 | ACCOUNTADMIN | | | +---------------------+---------------+-------------+-------------------------------+-------------------------------+--------------+---------+--------------+
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4