SHOW NODES IN COMPUTE POOL

Lists the nodes currently provisioned in a specified compute pool, including the instance family backing each node. Use this command to see which primary or backup instance families are actually in use when backup instance types are configured for a pool.

See also:

CREATE COMPUTE POOL , ALTER COMPUTE POOL, SHOW COMPUTE POOLS , SHOW COMPUTE POOL INSTANCE FAMILIES

Syntax

SHOW NODES IN COMPUTE POOL <name>
             [ LIKE '<pattern>' ]
             [ LIMIT <rows> ]

Parameters

name

Name of the compute pool whose nodes you want to list. The name must identify an existing compute pool in the current account.

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

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

Access control requirements

A role used to execute this operation must have the following privileges at a minimum:

PrivilegeObjectNotes
USAGECompute poolNone

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.

Output

The command returns one row for each node currently provisioned in the compute pool. The output includes the following columns:

ColumnDescription
node_idUnique identifier for the node in the compute pool.
instance_family

The actual instance family allocated for the node (for example, GEN_X64_G2_4, GEN_X64_G2_8). When backup instance types are configured and a fallback is active, this value may differ from the pool’s primary INSTANCE_FAMILY.

created_onDate and time when the node was provisioned.
placement_groupThe availability zone in which the node is provisioned.
vcpuNumber of vCPUs available to services on this node.
memory_gibMemory in GiB available to services on this node.
storage_gibStorage in GiB available to services on this node.
gpu

Name of the GPU on this node, if applicable. Otherwise, an empty string.

gpu_countNumber of GPUs on this node, if applicable. Otherwise, 0.
gpu_memory_gibTotal GPU memory available per instance in GiB, if applicable. Otherwise, 0.

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.

    For example, you can use the pipe operator or RESULT_SCAN function to select specific columns from the SHOW command output or filter the rows.

    When you refer to the output columns, use double-quoted identifiers for the column names. For example, to select the output column type, specify SELECT "type".

    You must use double-quoted identifiers because the output column names for SHOW commands are in lowercase. The double quotes ensure that the column names in the SELECT list or WHERE clause match the column names in the SHOW command output that was scanned.

  • 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 the compute pool is suspended, the command returns 0 rows.
  • The output is a real-time snapshot of currently provisioned nodes. It does not include historical node data.

Examples

The following command lists all nodes in a compute pool:

SHOW NODES IN COMPUTE POOL my_compute_pool;

The following command lists up to 10 nodes:

SHOW NODES IN COMPUTE POOL my_compute_pool LIMIT 10;

Sample output for a compute pool whose primary instance family is GEN_X64_G2_4 and that has GEN_X64_G2_8 configured as a backup. The third node (node-11-07-198-03) is running on the backup family because GEN_X64_G2_4 was capacity-constrained when that node was provisioned:

+--------------------+-----------------+-------------------------------+-----------------+------+------------+-------------+-----+-----------+----------------+
| node_id            | instance_family | created_on                    | placement_group | vcpu | memory_gib | storage_gib | gpu | gpu_count | gpu_memory_gib |
|--------------------+-----------------+-------------------------------+-----------------+------+------------+-------------+-----+-----------+----------------|
| node-11-07-198-01  | GEN_X64_G2_4    | 2026-06-16 09:12:04.000 -0700 | us-west-2a      |    3 |         13 |       93.13 |     |         0 |              0 |
| node-11-07-198-02  | GEN_X64_G2_4    | 2026-06-16 09:12:04.000 -0700 | us-west-2a      |    3 |         13 |       93.13 |     |         0 |              0 |
| node-11-07-198-03  | GEN_X64_G2_8    | 2026-06-16 10:48:31.000 -0700 | us-west-2b      |    6 |         28 |      186.26 |     |         0 |              0 |
+--------------------+-----------------+-------------------------------+-----------------+------+------------+-------------+-----+-----------+----------------+