USE
Syntax
USE [DATABASE | ORGANIZATION | ROLE | SCHEMA | STORE] entity_name;Description
This switches the current session’s database, organization, role, schema, or store.
Arguments
entity_name
The name of an existing entity to set as the user’s current for the active session. Use SET DEFAULT to persist the change for new sessions. if tshe name is case sensitive you must wrap it in double quotes; otherwise the system uses the lowercase name.
When using a new schema, a fully-qualified schema name can optionally be used to set the current database and schema.
Examples
Use a new organization
In the following example, we have access to different organizations, and we switch to the demo2 organization in the current sessions from the test organization:
<no-db>/<no-store># LIST ORGANIZATIONS;
+--------------------------------------+------------+-------------+-------------+--------------+--------------------+-------------------------------+
| ID | Name | Is Current | Is Default | Description | Profile Image Uri | Created At |
+======================================+============+=============+=============+==============+====================+===============================+
| a2ab163c-a166-49b0-8282-10679479cd58 | test | true | true | <null> | <null> | 2024-05-07 18:43:48 +0000 UTC |
+--------------------------------------+------------+-------------+-------------+--------------+--------------------+-------------------------------+
| 3736b067-e006-456d-96bf-3fb35b17bf91 | demo2 | false | false | <null> | <null> | 2024-05-07 18:43:58 +0000 UTC |
+--------------------------------------+------------+-------------+-------------+--------------+--------------------+-------------------------------+
<no-db>/<no-store># USE ORGANIZATION demo2;
+--------------+------------+------------+--------------------------+
| Type | Name | Command | Summary |
+==============+============+============+==========================+
| organization | demo2 | USE | using organization demo2 |
+--------------+------------+------------+--------------------------+
<no-db>/<no-store># LIST ORGANIZATIONS;
+--------------------------------------+------------+-------------+-------------+--------------+--------------------+-------------------------------+
| ID | Name | Is Current | Is Default | Description | Profile Image Uri | Created At |
+======================================+============+=============+=============+==============+====================+===============================+
| a2ab163c-a166-49b0-8282-10679479cd58 | test | false | true | <null> | <null> | 2024-05-07 18:43:48 +0000 UTC |
+--------------------------------------+------------+-------------+-------------+--------------+--------------------+-------------------------------+
| 3736b067-e006-456d-96bf-3fb35b17bf91 | demo2 | true | false | <null> | <null> | 2024-05-07 18:43:58 +0000 UTC |
+--------------------------------------+------------+-------------+-------------+--------------+--------------------+-------------------------------+Use a new database
In the following example, we are creating a new database called demodb2 and using it. Note the database in the command line prompt changing from demodb to demodb2:
Use a new schema
In the following example, we switch from the current public schema to use a new schema called newschema. Note how after the command is issued, the session's schema changes from public to newschema:
Use a new store
The following shows how msk store is set as the current store for the session to use:
Use a new role
The following example shows how you can update the current role to useradmin to allow managing users and roles in the current session:
Last updated