Using Account Identifiers for Connecting to Your Accounts¶

This topic provides information about connecting to accounts in your organization. For information about account identifiers, see Account Identifiers.

In this Topic:

Supported Methods for Connecting to Snowflake
- Connecting via URL
- Drivers
Backwards Compatibility

Supported Methods for Connecting to Snowflake¶

Connecting via URL¶

Feature	Account Name	Account Locator
Standard URL	`https://<orgname>-<account_name>.snowflakecomputing.com`	`https://<account_locator>.<region>.<cloud>.snowflakecomputing.com`
Private Connectivity URL ^{[2], [3]}	`https://<orgname>-<account_name>.privatelink.snowflakecomputing.com`	`https://<account_locator>.<region>.privatelink.snowflakecomputing.com`
SSO setup ^[1]	`https://<orgname>-<account_name>.snowflakecomputing.com`	`https://<account_locator>.<region>.<cloud>.snowflakecomputing.com`
SSO ^[1]	See below.

[1] For more information, see:

How to Set up SSO Using OKTA with Snowflake New URL Format

How to Set up SSO with AZURE AD and the Snowflake New URL Format

[2] For more information, see How to Set up SSO for PrivateLink URL Using SAML2 Integration

[3] Using private connectivity requires updating DNS records to include the private connectivity URL. For more information, see

AWS PrivateLink CNAME Records.

Azure Private Link DNS setup in Option 1 and Option 2.

Google Cloud Private Service Connect DNS setup in Step 8.

Use SYSTEM$GET_PRIVATELINK_CONFIG to verify the URL format to connect to Snowflake.

Drivers¶

Driver	Account Name	Account Locator
SnowSQL	snowsql -a <orgname>-<account_name>	snowsql -a <account_locator>
JDBC	jdbc:snowflake://<orgname>-<account_name>.snowflakecomputing.com/?<connection_params>	jdbc:snowflake://<account_locator>.snowflakecomputing.com/?<connection_params>
ODBC	Server: <orgname>-<account_name>.snowflakecomputing.com	Server: <account_locator>.snowflakecomputing.com
Python	ACCOUNT param: <orgname>-<account_name>	ACCOUNT param: <account_locator>.<region_id>.<cloud>
.Net	ACCOUNT param: <orgname>-<account_name> HOST param: use default (.snowflakecomputing.com)	ACCOUNT param: <account_locator> HOST param: .snowflakecomputing.com by default, specify for non us-west deployment
Golang	db, err := sql.Open(“snowflake”, “jsmith:mypassword@<orgname>-<account_name>/mydb/testschema?warehouse=mywh”)	sql.Open(“snowflake”, “jsmith:mypassword@<account_locator>/mydb/testschema?warehouse=mywh”)
node.js	ACCOUNT param: <orgname>-<account_name>	ACCOUNT param: <account_locator>.<region_id>.<cloud>
Spark (connector)	Same as JDBC	Same as JDBC
Spark (Databricks)	<Account URL for Snowflake account>	<Account Locator URL for Snowflake account>
Spark (Qubole)	Host address: <orgname>-<account_name>.snowflakecomputing.com	Host address: <account_locator>.snowflakecomputing.com
PHP	ACCOUNT param: <orgname>-<account_name> REGION param: leave blank for all regions	ACCOUNT param: <account_locator> REGION param: specify for non us-west deployment
SQLAchemy	snowflake://<user_login_name>:<password>@<orgname>-<account_name>	snowflake://<user_login_name>:<password>@<account_locator>.<region_id>.<cloud>

Backwards Compatibility¶

The account locator and account locator URL will continue to work for all features and nothing will break.
The new account name and URL will also work in parallel to the account locator/URL and be the basis for new URL features going forward (for example client failover redirect URLs).
There are no near term plans to deprecate the account locator and account locator URL.