Account Management and Data Governance · Topic 4 of 9

Account Parameters and Enabling Cortex AI

Set and check account parameters with ALTER ACCOUNT, know the override order, and enable Snowflake Cortex AI features and cross region inference.

  • 5 min
In a nutshell
  • Account parameters: ALTER ACCOUNT SET, ACCOUNTADMIN; session and object parameters are defaults that lower levels override.
  • SHOW PARAMETERS ... IN ACCOUNT shows value, default and level.
  • Defaults to know: Time Travel 1 day, statement timeout 172800 seconds.

What it is

Parameters control how Snowflake behaves. Some can only be set for the whole account. Others are set at the account level as a default and can be overridden lower down. An administrator needs to know which kind a parameter is, who may change it, and where a lower setting beats a higher one.

Cortex AI features (AI functions, models and related services) are controlled partly by parameters and partly by privileges and roles. The administrator task is to make them available to the right users, in the right regions, safely.

ACCOUNTADMINALTER ACCOUNT SETAccount parameterwhole accountdefault forSession and object parametersuser, warehouse, tableoverridden byLower level setting

How it works

Parameter types

TypeWhere it can be setExample
Account parameterAccount level onlyPERIODIC_DATA_REKEYING, MIN_DATA_RETENTION_TIME_IN_DAYS, PREVENT_UNLOAD_TO_INLINE_URL
Session parameterAccount, user or sessionTIMEZONE, STATEMENT_TIMEOUT_IN_SECONDS
Object parameterAccount, or the object itselfDATA_RETENTION_TIME_IN_DAYS on a database, schema or table

Rules that matter:

  • Account parameters are set with ALTER ACCOUNT SET, and other users cannot change them.
  • A session or object parameter set at account level is a default. A user, session or object can override it at its own level, and the most specific level usually wins. Exceptions exist: when a warehouse and a session both set STATEMENT_TIMEOUT_IN_SECONDS, the lower non-zero value applies.
  • UNSET returns a parameter to its default. Give only the name; including a value is an error.
  • Several parameters can be set in one statement, separated by spaces, commas or new lines.
ALTER ACCOUNT SET STATEMENT_TIMEOUT_IN_SECONDS = 7200
                  PERIODIC_DATA_REKEYING = TRUE;
SHOW PARAMETERS LIKE 'STATEMENT_TIMEOUT%' IN ACCOUNT;
SHOW PARAMETERS IN ACCOUNT;
ALTER ACCOUNT UNSET STATEMENT_TIMEOUT_IN_SECONDS;

SHOW PARAMETERS returns the value, the default and the level at which the value was set, so use it to find out why a session behaves unexpectedly.

Exam tip

A question that says "a team needs a different value than the account default" is about overriding at a lower level (user, warehouse or object). A question that says "no one may change it" points to an account parameter or a policy at account level.

Parameters an administrator is expected to know

ParameterPurpose
DATA_RETENTION_TIME_IN_DAYSDefault Time Travel retention; the default is 1 day
MIN_DATA_RETENTION_TIME_IN_DAYSAccount level floor for retention on objects
STATEMENT_TIMEOUT_IN_SECONDSStops statements that run too long; the default is 172800 seconds (2 days)
NETWORK_POLICYActivates a network policy
PERIODIC_DATA_REKEYINGRekeys old data yearly (Enterprise or higher)
PREVENT_UNLOAD_TO_INLINE_URLBlocks unloads to inline URLs
REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_CREATIONForces storage integrations for new external stages
ENABLE_INTERNAL_STAGES_PRIVATELINKExposes the private internal stage endpoint
CORTEX_ENABLED_CROSS_REGIONWhere Cortex requests may be processed

Changing account parameters is an ACCOUNTADMIN task. Keep a record, because a single parameter can change behavior for every user.

Enable Cortex AI features for users

Three questions decide whether a user can use a Cortex feature.

1. Does the user hold the privileges? Calling Cortex AI functions needs the USE AI FUNCTIONS account privilege (or a per function privilege such as USE AI FUNCTION AI_COMPLETE) and a database role such as SNOWFLAKE.CORTEX_USER or SNOWFLAKE.AI_FUNCTIONS_USER. USE AI FUNCTIONS and CORTEX_USER are granted to PUBLIC by default, so every user has access until you revoke it. ACCOUNTADMIN manages the privilege.

2. May the user use the model? Models are controlled by application roles such as CORTEX-MODEL-ROLE-ALL, granted to account roles. New accounts and accounts with CORTEX_MODELS_ALLOWLIST = 'All' have that role granted to SNOWFLAKE.PUBLIC, so all users can use all models by default. To restrict, remove the broad grant with the stored procedure SNOWFLAKE.LOCAL.REVOKE_FROM_PUBLIC_APPLICATION_ROLE (a plain REVOKE does not remove it) and grant the roles you want.

3. Can the request run in the account's region? Not every model runs in every region. CORTEX_ENABLED_CROSS_REGION sets where a request may be processed when it cannot run in the account's own region.

ValueMeaning
DISABLEDRequests stay in the account's region
ANY_REGIONAny region may process the request
A list such as AWS_US or AZURE_EUOnly those region groups

The default depends on the account: ANY_REGION for new accounts in new organizations in commercial regions created after March 9, 2026, a same cloud geography value for other commercial accounts, and DISABLED for government, FedRAMP and Virtual Private Snowflake accounts. Use SHOW CORTEX BASE MODELS to see what is available.

ALTER ACCOUNT SET CORTEX_ENABLED_CROSS_REGION = 'AWS_US';
GRANT DATABASE ROLE SNOWFLAKE.CORTEX_USER TO ROLE analyst;
GRANT APPLICATION ROLE SNOWFLAKE."CORTEX-MODEL-ROLE-ALL" TO ROLE analyst;
UserroleneedsUSE AI FUNCTIONSand database roleplusModel application roleplusRegion accessCORTEX_ENABLED_CROSS_REGION

Common mistakes

Setting a session parameter at account level and expecting it to be final. A lower level can override it.

Passing a value to UNSET. UNSET takes only names.

Thinking CORTEX_MODELS_ALLOWLIST is the recommended control. It is being deprecated; role based model access is the recommended method.

Enabling cross region inference for data that must stay in one region. Cross region processing sends the request to another region; review compliance first. Government, FedRAMP and VPS accounts default to DISABLED.

Assuming revoking from PUBLIC is the end. Check SHOW GRANTS, and remember that ACCOUNTADMIN always has access to all models.

What to remember for the exam

  • Account parameters: ALTER ACCOUNT SET, ACCOUNTADMIN; session and object parameters are defaults that lower levels override.
  • SHOW PARAMETERS ... IN ACCOUNT shows value, default and level.
  • Defaults to know: Time Travel 1 day, statement timeout 172800 seconds.
  • Cortex AI: USE AI FUNCTIONS plus CORTEX_USER (both on PUBLIC by default), model application roles, and CORTEX_ENABLED_CROSS_REGION.
  • CORTEX_MODELS_ALLOWLIST is deprecated in favor of role based model access.

Check yourself

  • How do you see where a parameter value was set?

    SHOW PARAMETERS ... IN ACCOUNT (or IN USER or IN SESSION) lists the value and the level.

  • Which parameter lets Cortex process a request in another region?

    CORTEX_ENABLED_CROSS_REGION, with ANY_REGION, DISABLED or a region group list.

  • Why can every user call Cortex functions in a fresh account?

    USE AI FUNCTIONS and the CORTEX_USER database role are granted to PUBLIC by default.

Topic 4 of 9 in Account Management and Data Governance

Test yourself on Account Management and Data Governance

The full Snowflake ADA-C02 question bank has 814 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.