63-character limit for account identifiers (Pending)¶
Attention
This behavior change is in the 2026_03 bundle.
For the current status of the bundle, refer to Bundle history.
- Before the change:
Snowflake doesn’t enforce a maximum length or trailing-underscore restriction on Format 1 of the account identifier (the account name prefixed by its organization name, for example
myorg-myaccount). Account creation and renaming succeed regardless of identifier length.- After the change:
When the 2026_03 behavior change bundle is enabled in your account, Snowflake enforces the following restrictions on Format 1 of the account identifier:
The combined
<orgname>-<account_name>identifier can’t exceed 63 characters.The account name can’t end with an underscore (
_).
If an
ALTER ACCOUNT ... RENAME TOorCREATE ACCOUNTstatement violates either restriction, the statement fails with one of the following error codes:ORG_ACCOUNT_NAME_EXCEEDS_DNS_LIMITif the identifier exceeds 63 characters.ACCOUNT_NAME_INVALID_FOR_DNSif the account name ends with an underscore.
These restrictions ensure that the account identifier complies with the limits for a DNS label defined in RFC 1035 and the LDH label defined in the CA/Browser Forum Baseline Requirements, preventing possible DNS lookup and account reachability failures.
Existing accounts that don’t comply with these limits continue to function. However, Snowflake recommends renaming them to ensure smooth operation with current and future features. Once you rename an account to a compliant name, you can’t rename it back to a non-compliant name.
To find non-compliant accounts, run the following queries:
For more information about account identifiers, see Account identifiers. For more information about renaming accounts, see Renaming an account.
Ref: 2215