Managing Accounts in Your Organization

All organization tasks can be performed from the Snowflake classic web interface or using the DDL commands for organizations.

In this Topic:

Creating an Account

An account can be created by an ORGADMIN through the web interface or using SQL:

Snowsight

Click Admin » Accounts » Create New Account.

SQL

Execute a CREATE ACCOUNT command.

When creating an account, you can specify a cloud platform, a region, and a Snowflake edition. You can optionally specify a region group if you have, or want to have, accounts in multiple region groups. For more details see Region Groups.

If you are having trouble creating or accessing a new account, consider:

  • By default, the maximum number of accounts in an organization cannot exceed 25. Contact Snowflake Support to have this limit raised.

  • You can only create an account in a region that is enabled for your organization. For a list of available regions, see Viewing a List of Regions Available for Your Organization (In this topic). To request access to additional regions, contact Snowflake Support.

  • It takes about 30 seconds for the DNS changes to propagate before you can access a newly created account. If the account is not accessible immediately, wait for approximately 30 seconds and try again.

Each account in your organization can have its own set of users, roles, databases, and warehouses.

You will be billed for usage in all of your accounts on a single bill. To monitor usage for your organization accounts, see Organization Usage views.

Viewing a List of Organization Accounts

A user with the ORGADMIN role can view a list of all accounts created in your organization through the web interface or using SQL:

Snowsight

Click Admin » Accounts.

SQL

Execute a SHOW ORGANIZATION ACCOUNTS command.

Changing Account Name

An organization administrator (i.e. a user granted the ORGADMIN role) can use the ALTER ACCOUNT command to rename an account. For example, the following command renames an account called original_acctname to new_acctname:

use role orgadmin;
alter account original_acctname rename to new_acctname;

Organization administrators cannot rename an account while they are logged into it, so they must log into a different account before executing the renaming command. If your organization consists of a single account that needs to be renamed, contact Snowflake Support.

By default, Snowflake allows you to access the renamed account with either the original URL or the URL that contains the new account name. To prevent access using the old URL, set the optional SAVE_OLD_URL parameter to FALSE when renaming the account. If the account has already been renamed without this parameter, you can still block the old URL by executing the ALTER ACCOUNT new_acctname DROP OLD URL command.

Deleting an Account

To delete an account, contact Snowflake Support and provide a unique identifier for your account, which can be one of the following:

Once you contact Snowflake Support, it may take up to six weeks for the account to be fully deleted. This delay allows you to recover the account within 30 days of the request. Snowflake usually deducts the account from the number of accounts allowed for your organization within a few days of the initial request.

Viewing a List of Regions Available for Your Organization

A user with the ORGADMIN role can view a list of regions available for your organization through the web interface or using SQL:

Snowsight

Click Admin » Accounts » Create New Account » Choose Your Region.

SQL

Execute a SHOW REGIONS command.

Enabling Accounts for Replication

A user with the ORGADMIN role can enable an account for replication by setting the ENABLE_ACCOUNT_DATABASE_REPLICATION parameter to true from the ORGADMIN account.

Note

If you have more than one account with the same account locator in different regions, to enable replication, contact Snowflake Support.

Example 1: Enabling Replication for a Single Account

-- Assume the ORGADMIN role
use role orgadmin;

-- View the list of the accounts
show organization accounts;

-- Enable replication for an account
select system$global_account_set_parameter('<account1_locator>',
'ENABLE_ACCOUNT_DATABASE_REPLICATION', 'true');

Example 2: Enabling Replication for Multiple Accounts

-- Assume the ORGADMIN role
use role orgadmin;

-- View the list of the accounts
show organization accounts;

-- Enable replication for the first account
select system$global_account_set_parameter('<account1_locator>',
'ENABLE_ACCOUNT_DATABASE_REPLICATION', 'true');

-- Enable replication for the second account
select system$global_account_set_parameter('<account2_locator>',
'ENABLE_ACCOUNT_DATABASE_REPLICATION', 'true');
Back to top