SHOW USERS¶
Lists all users in the system.
- See also:
Syntax¶
SHOW [ TERSE ] USERS
[ LIKE '<pattern>' ]
[ STARTS WITH '<name_string>' ]
[ LIMIT <rows> ]
[ FROM '<name_string>' ]
Parameters¶
TERSE
Optionally returns only a subset of the output columns:
| name | created_on | display_name | first_name | last_name | email | org_identity | comment | has_password | has_rsa_public_key | type | has_mfa
Default: No value (all columns are included in the output).
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).
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 [ 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'
andSTARTS 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 bySTARTS 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).
Usage notes¶
Any user can execute the SHOW USERS command. Snowflake filters the output based upon the privileges granted to the active role that the user uses to run the command. The user that runs the command can always see the username in the results, which is recorded in the
name
column. To see the full output, the active role must have either:The OWNERSHIP privilege on the user object.
The MANAGE GRANTS privilege on the account.
If the account has more than 10,000 users, you can use either of the following options:
SHOW USERS;
SHOW USERS LIMIT 10000 FROM 'JOE';
Returns users after 10,000. In this example,
JOE
is the username of the last row from the command.
The command does not require a running warehouse to execute.
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.