Lists instances of a service.
The command output offers visibility into auto-scaling and rolling upgrades by displaying the status of each individual service instance.
Snowpark Container Services overview, CREATE SERVICE, SHOW SERVICES, SHOW SERVICE CONTAINERS IN SERVICE
SHOW SERVICE INSTANCES IN SERVICE <name>
Copy
Parameters¶name
Specifies the identifier for the service whose instances to list.
Quoted names for special characters or case-sensitive names are not supported.
The command output provides properties and metadata of the service instances in the following columns:
Column
Description
database_name
Database in which the service is created.
schema_name
Schema in which the service is created.
service_name
Name of the service.
service_status
One of the following values, which indicates the current status of the service:
PENDING
RUNNING
FAILED
DONE
SUSPENDING
SUSPENDED
DELETING
DELETED
INTERNAL_ERROR
Note that the value in this column is the same as the status column in the output of the DESCRIBE SERVICE.
instance_id
ID of the service instance (this is the index of the service instance starting from 0).
status
One of the following values, which indicates the current status of the service instance:
PENDING: The service instance is currently being deployed and is not yet ready to serve requests.
READY: All containers in the service instance are ready; the service instance is ready to serve requests.
FAILED: At least one container in the service instance has exited with a failure.
TERMINATING: The service instance is in the process of termination and will be removed after the process is complete.
SUCCEEDED: The service is a job service and all containers in the service instance have terminated successfully.
spec_digest
The unique and immutable identifier that represents the service specification content.
creation_time
The time when Snowflake started creating the service instance.
start_time
The time when Snowflake acknowledged the service instance is running on a node.
ip_address
IP address of the service instance. Other instances of the same service (or other services) can use this IP address to connect to a specific service instance.
When you’re running multiple service instances, you can implement leader election among the instances of a service by electing the instance with instance_id 0 as the leader.
A role used to execute this operation must have the following privileges at a minimum:
Privilege
Object
Notes
Any one of these privileges: OWNERSHIP or MONITOR
Service
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 following example lists instances of the echo_service service in the current database and schema for the session:
SHOW SERVICE INSTANCES IN SERVICE echo_service;
Copy
Sample output:
+---------------+-------------+--------------+----------------+-------------+--------+------------------------------------------------------------------+----------------------+----------------------+------------+ | database_name | schema_name | service_name | service_status | instance_id | status | spec_digest | creation_time | start_time | ip_address | |---------------+-------------+--------------+----------------+-------------+--------+------------------------------------------------------------------+----------------------+----------------------+------------| | TUTORIAL_DB | DATA_SCHEMA | ECHO_SERVICE | RUNNING | 0 | READY | 2831c241b8d64104fbc562d60764d7abd28602c70b6a8357341e8c8210b79da4 | 2025-04-25T06:01:32Z | 2025-04-25T06:01:32Z | 10.244.0.9 | +---------------+-------------+--------------+----------------+-------------+--------+------------------------------------------------------------------+----------------------+----------------------+------------+
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