Parameters¶

Snowflake provides parameters that let you control the behavior of your account, individual user sessions, and objects. All parameters have default values. You can set these parameters and override them at different levels, depending on the parameter type (account, session, or object).

Parameter hierarchy and types¶

This section describes the different types of parameters and the levels at which each type can be set. There are three types of parameters:

• Account parameters
• Session parameters
• Object parameters

The following diagram illustrates the hierarchical relationship between the different parameter types and how individual parameters can be overridden at each level:

Account parameters¶

You can only set account parameters at the account level, if you are using a role that has been granted the privilege to set the parameter. To set an account parameter, you run the ALTER ACCOUNT command.

Snowflake provides the following account parameters:

Session parameters¶

Most parameters are session parameters, which you can set at the following levels:

Account:

Account administrators can run the ALTER ACCOUNT command to set session parameters for the account.

The values that you set at this level become the default values for individual users and their sessions.

User:

Administrators with the appropriate privileges (typically, a user who has been granted the SECURITYADMIN role) can run the ALTER USER command to override session parameters for individual users. In addition, individual users can run the ALTER USER command to override default session parameters for themselves.

The values that you set for a user become the default values in any session started by that user.

Session:

Users can run the ALTER SESSION command to override session parameters for the current session.

Object parameters¶

You can set object parameters at the following levels:

Account:

Account administrators can run the ALTER ACCOUNT command to set object parameters for objects in the account.

The values that you set at this level become the default values for individual objects created in the account.

Object:

Users with the appropriate privileges can run the CREATE <object> or ALTER <object> commands to override object parameters for an individual object.

Snowflake provides the following object parameters:

Viewing the parameters and their values¶

To view the parameters that are set and their default values, run the SHOW PARAMETERS command. You can run the command with different command parameters to display different types of parameter:

• Viewing session parameters
• Viewing object parameters
• Viewing all parameters (including account and object parameters)
• Limiting the list of parameters by name

Viewing session parameters¶

By default, the command displays only session parameters:

SHOW PARAMETERS;

Viewing object parameters¶

To display the object parameters for a specific object, include the IN clause with the object type and name. For example:

SHOW PARAMETERS IN DATABASE mydb;

SHOW PARAMETERS IN WAREHOUSE mywh;

Viewing all parameters (including account and object parameters)¶

To display all parameters, including account and object parameters, include the IN ACCOUNT clause:

SHOW PARAMETERS IN ACCOUNT;

Limiting the list of parameters by name¶

You can specify the LIKE clause to limit the list of parameters by name. For example:

• To display the session parameters with names containing “time”:

  Copy code

  SHOW PARAMETERS LIKE '%time%';
  

• To display all the parameters with names starting with “time”:

  Copy code

  SHOW PARAMETERS LIKE 'time%' IN ACCOUNT;
  

ABORT_DETACHED_QUERY¶

Type:

Session — Can be set for Account » User » Session

Data Type:

Boolean

Description:

Specifies the action that Snowflake performs for in-progress queries if connectivity is lost due to abrupt termination of a session (e.g. network outage, browser termination, service interruption).

Values:

TRUE: In-progress queries are aborted 5 minutes after connectivity is lost.

FALSE: In-progress queries are completed.

Default:

FALSE

ACTIVE_PYTHON_PROFILER¶

Type:

Session — Can be set for Account » User » Session

Data Type:

String (Constant)

Description:

Sets the profiler to use for the session when profiling Python handler code.

Values:

'LINE': To have the profile focus on line use activity.

'MEMORY': To have the profile focus on memory use activity.

Default:

None.

ACCOUNT_LEVEL_FILE_EXTENSIONS_ALLOW_LIST_FOR_PRIVATE_WORKSPACES¶

Type:

Account — Can be set only for Account

Data Type:

String

Description:

Specifies the file extensions that are allowed in private workspaces for the account. The value is a comma-separated list of extensions, for example: .ipynb,.sql,.txt. If the parameter is empty (default), all file extensions are allowed.

When the allow list is non-empty:

• Only the listed extensions are permitted; all others are blocked.
• Files uploaded through Workspaces with a non-allowed extension will immediately fail to upload.
• If a file is renamed to use a non-allowed extension, the file becomes inaccessible within the workspace.
• Pre-existing files with disallowed extensions will not appear in Workspaces.
• Users can still use the Snowflake CLI PUT command to upload files with non-allowed extensions to a workspace’s virtual stage or a Notebook Project Object’s virtual stage. However, these files are inaccessible and cannot be used, viewed, downloaded (via GET), or listed (via LIST) from within the workspace or Code Bundle environment.
• To maintain core workspace functionality, include .ipynb and .sql in the allow list.
• Files without an extension (for example, Makefile) are not allowed once the list is non-empty.
• Dotfiles (for example, .gitignore or .venv) must be explicitly added to the list.
• Extension matching is case-sensitive. For example, if .txt is in the list, .TXT is not allowed.

Default:

Empty string (all extensions allowed)

ACCOUNT_LEVEL_FILE_EXTENSIONS_ALLOW_LIST_FOR_SHARED_WORKSPACES¶

Type:

Account — Can be set only for Account

Data Type:

String

Description:

Specifies the file extensions that are allowed in shared workspaces for the account. The value is a comma-separated list of extensions, for example: .ipynb,.sql,.txt. If the parameter is empty (default), all file extensions are allowed.

When the allow list is non-empty:

• Only the listed extensions are permitted; all others are blocked.
• Files uploaded through Workspaces with a non-allowed extension will immediately fail to upload.
• If a file is renamed to use a non-allowed extension, the file becomes inaccessible within the workspace.
• Pre-existing files with disallowed extensions will not appear in Workspaces.
• Users can still use the Snowflake CLI PUT command to upload files with non-allowed extensions to a workspace’s virtual stage or a Notebook Project Object’s virtual stage. However, these files are inaccessible and cannot be used, viewed, downloaded (via GET), or listed (via LIST) from within the workspace or Code Bundle environment.
• To maintain core workspace functionality, include .ipynb and .sql in the allow list.
• Files without an extension (for example, Makefile) are not allowed once the list is non-empty.
• Dotfiles (for example, .gitignore or .venv) must be explicitly added to the list.
• Extension matching is case-sensitive. For example, if .txt is in the list, .TXT is not allowed.
• Files with disallowed extensions that originate from a connected Git repository are visible to the user but remain inaccessible within the workspace.

Default:

Empty string (all extensions allowed)

ALLOW_BIND_VALUES_ACCESS¶

Type:

Account — Can only be set for Account

Data Type:

Boolean

Description:

Specifies whether clients can access bind variable values by using the BIND_VALUES table function, the QUERY_HISTORY Account Usage view, the QUERY_HISTORY Organization Usage view, or the QUERY_HISTORY function. For more information, see Retrieve bind variable values.

Values:

TRUE: Allows the retrieval of bind variable values.

FALSE: Doesn’t allow retrieval of bind variable values.

Default:

TRUE

ALLOW_CLIENT_MFA_CACHING¶

Type:

Account — Can only be set for Account

Data Type:

Boolean

Description:

Specifies whether an MFA token can be saved in the client-side operating system keystore to promote continuous, secure connectivity without users needing to respond to an MFA prompt at the start of each connection attempt to Snowflake. For details and the list of supported Snowflake-provided clients, see Using MFA token caching to minimize the number of prompts during authentication — *optional*.

Values:

TRUE: Stores an MFA token in the client-side operating system keystore to enable the client application to use the MFA token whenever a new connection is established. While true, users are not prompted to respond to additional MFA prompts.

FALSE: Does not store an MFA token. Users must respond to an MFA prompt whenever the client application establishes a new connection with Snowflake.

Default:

FALSE

ALLOW_ID_TOKEN¶

Type:

Account — Can be set only for Account

Data Type:

Boolean

Description:

Specifies whether a connection token can be saved in the client-side operating system keystore to promote continuous, secure connectivity without users needing to enter login credentials at the start of each connection attempt to Snowflake. For details and the list of supported Snowflake-provided clients, see Using connection caching to minimize the number of prompts for authentication — *Optional*.

Values:

TRUE: Stores a connection token in the client-side operating system keystore to enable the client application to perform browser-based SSO without prompting users to authenticate whenever a new connection is established.

FALSE: Does not store a connection token. Users are prompted to authenticate whenever the client application establishes a new connection with Snowflake. SSO to Snowflake is still possible if this parameter is set to false.

Default:

FALSE

ALLOWED_SPCS_WORKLOAD_TYPES¶

Type:

Account — Can be set only for Account

Data Type:

String

Description:

Specifies the workload types that are allowed in your account to deploy to Snowpark Container Services. Also see DISALLOWED_SPCS_WORKLOAD_TYPES.

Values:

The value is a comma-separated list of the following supported workload types:

• USER: Any workloads directly deployed by users.
• NOTEBOOK: Snowflake Notebooks.
• STREAMLIT: Streamlit in Snowflake.
• MODEL_SERVING: ML Model Serving.
• ML_JOB: Snowflake ML Jobs.
• ALL: All workloads.

Default:

ALL

AUTO_EVENT_LOGGING¶

Type:

Object (for Snowflake Scripting stored procedures)

Data Type:

String (Constant)

Description:

Controls whether Snowflake Scripting log messages and trace events are ingested automatically into the event table. To set this parameter, run the ALTER PROCEDURE command.

Values:

• LOGGING: Automatically adds the following additional logging information to the event table when a procedure is executed:

  • BEGIN/END of a Snowflake Scripting block.
  • BEGIN/END of a child job request.

  This information is added to the event table only if the effective LOG_LEVEL is set to TRACE for the stored procedure.

• TRACING: Automatically adds the following additional trace information to the event table when a stored procedure is executed:

  • Exception catching.
  • Information about child job execution.
  • Child job statistics.
  • Stored procedure statistics, including execution time and input values.

  This information is added to the event table only if the effective TRACE_LEVEL is set to ALWAYS or ON_EVENT for the stored procedure.

• ALL: Automatically adds both the logging information added for the LOGGING value and the trace information added for the TRACING value.

• OFF: Does not automatically add logging information or trace information to the event table.

Default:

OFF

For more information about using this parameter, see Setting levels for logging, metrics, and tracing, Automatically add log messages about blocks and child jobs, and Automatically emit trace events for child jobs and exceptions.

AUTOCOMMIT¶

Type:

Session — Can be set for Account » User » Session

Data Type:

Boolean

Description:

Specifies whether autocommit is enabled for the session. Autocommit determines whether a DML statement, when executed without an active transaction, is automatically committed after the statement successfully completes. For more information, see Transactions.

Note

Setting this parameter to FALSE stops usage data from being saved to the ORGANIZATION_USAGE schema of an organization account.

Values:

TRUE: Autocommit is enabled.

FALSE: Autocommit is disabled, meaning DML statements must be explicitly committed or rolled back.

Default:

TRUE

AUTOCOMMIT_API_SUPPORTED (view-only)¶

Type:

N/A

Data Type:

Boolean

Description:

For Snowflake internal use only. View-only parameter that indicates whether API support for autocommit is enabled for your account. If the value is TRUE, you can enable or disable autocommit through the APIs for the following drivers/connectors:

• JDBC driver
• ODBC driver
• Snowflake Connector for Python

BASE_LOCATION_PREFIX¶

Type:

Object (for databases and schemas) — Can be set for Account » Database » Schema

Data Type:

String

Description:

Specifies a prefix for Snowflake to use in the write path for Snowflake-managed Apache Iceberg™ tables. For more information, see data and metadata directories for Iceberg tables.

Values:

Any valid string prefix that complies with the storage naming conventions of your cloud provider.

Default:

None

BINARY_INPUT_FORMAT¶

Type:

Session — Can be set for Account » User » Session

Data Type:

String (Constant)

Description:

The format of VARCHAR values passed as input to VARCHAR-to-BINARY conversion functions. For more information, see Binary input and output.

Values:

HEX , BASE64 , or UTF8 / UTF-8

Default:

HEX

BINARY_OUTPUT_FORMAT¶

Type:

Session — Can be set for Account » User » Session

Data Type:

String (Constant)

Description:

The format for VARCHAR values returned as output by BINARY-to-VARCHAR conversion functions. For more information, see Binary input and output.

Values:

HEX or BASE64

Default:

HEX

CATALOG¶

Type:

Object (for databases, schemas, and Apache Iceberg™ tables) — Can be set for Account » Database » Schema » Iceberg table

Data Type:

String

Description:

Specifies the catalog for Apache Iceberg™ tables. For more information, see the Iceberg table documentation.

Values:

SNOWFLAKE or any valid catalog integration identifier.

Default:

None

CATALOG_SYNC¶

Type:

Object (for databases, schemas, and Iceberg tables) — Can be set for Account » Database » Schema » Iceberg Table

Data Type:

String

Description:

Specifies the name of your catalog integration for Snowflake Open Catalog. Snowflake syncs tables that use the specified catalog integration with your Snowflake Open Catalog account. For more information, see Sync a Snowflake-managed table with Snowflake Open Catalog.

Values:

The name of any existing catalog integration for Open Catalog.

Default:

None

CLIENT_ENABLE_LOG_INFO_STATEMENT_PARAMETERS¶

Type:

Session — Can be set for Account » User » Session

Data Type:

Boolean

Clients:

JDBC

Description:

Enables users to log the data values bound to PreparedStatements.

To see the values, you must not only set this session-level parameter to TRUE, but also set the connection parameter named TRACING to either INFO or ALL.

• Set TRACING to ALL to see all debugging information and all binding information.
• Set TRACING to INFO to see the binding parameter values and less other debug information.

Caution

If you bind confidential information, such as medical diagnoses or passwords, that information is logged. Snowflake recommends making sure that the log file is secure, or only using test data, when you set this parameter to TRUE.

Values:

TRUE or FALSE.

Default:

FALSE

CLIENT_ENCRYPTION_KEY_SIZE¶

Type:

Account — Can be set only for Account

Data Type:

Integer

Clients:

Any

Description:

Specifies the AES encryption key size, in bits, used by Snowflake to encrypt/decrypt files stored on internal stages (for loading/unloading data) when you use the SNOWFLAKE_FULL encryption type.

Values:

128 or 256

Default:

128

CLIENT_MEMORY_LIMIT¶

Type:

Session — Can be set for Account » User » Session

Data Type:

Integer

Clients:

JDBC, ODBC

Description:

Parameter that specifies the maximum amount of memory the JDBC driver or ODBC driver should use for the result set from queries (in MB).

For the JDBC driver:

• To simplify JVM memory management, the parameter sets a global maximum memory usage limit for all queries.
• CLIENT_RESULT_CHUNK_SIZE specifies the maximum size of each set (or chunk) of query results to download (in MB). The driver might require additional memory to process a chunk; if so, it will adjust memory usage during runtime to process at least one thread/query. Verify that CLIENT_MEMORY_LIMIT is set significantly higher than CLIENT_RESULT_CHUNK_SIZE to ensure sufficient memory is available.

For the ODBC driver:

• This parameter is supported in version 2.22.0 and higher.
• CLIENT_RESULT_CHUNK_SIZE is not supported.

Values:

Any valid number of megabytes.

Default:

1536 (effectively 1.5 GB)

Most users should not need to set this parameter. If this parameter is not set by the user, the driver starts with the default specified above.

In addition, the JDBC driver actively manages its memory conservatively to avoid using up all available memory.

CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX¶

Type:

Session — Can be set for Account » User » Session

Data Type:

Boolean

Clients:

JDBC, ODBC

Description:

For specific ODBC functions and JDBC methods, this parameter can change the default search scope from all databases/schemas to the current database/schema. The narrower search typically returns fewer rows and executes more quickly.

For example, the getTables() JDBC method accepts a database name and schema name as arguments, and returns the names of the tables in the database and schema. If the database and schema arguments are null, then by default, the method searches all databases and all schemas in the account. Setting CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX to TRUE narrows the search to the current database and schema specified by the connection context.

In essence, setting this parameter to TRUE creates the following precedence for database and schema:

1. Values passed as arguments to the functions/methods.
2. Values specified in the connection context (if any).
3. Default (all databases and all schemas).

For more details, see the information below.

This parameter applies to the following:

• JDBC driver methods (for the DatabaseMetaData class):

  • getColumns
  • getCrossReference
  • getExportedKeys
  • getForeignKeys
  • getFunctions
  • getImportedKeys
  • getPrimaryKeys
  • getSchemas
  • getTables

• ODBC driver functions:

  • SQLTables
  • SQLColumns
  • SQLPrimaryKeys
  • SQLForeignKeys
  • SQLGetFunctions
  • SQLProcedures

Values:

TRUE: If the database and schema arguments are null, then the driver retrieves metadata for only the database and schema specified by the connection context.

The interaction is described in more detail in the table below.

FALSE: If the database and schema arguments are null, then the driver retrieves metadata for all databases and schemas in the account.

Default:

FALSE

Additional Notes:

The connection context refers to the current database and schema for the session, which can be set using any of the following options:

1. Specify the default namespace for the user who connects to Snowflake (and initiates the session). This can be set for the user through the CREATE USER or ALTER USER command, but must be set before the user connects.
2. Specify the database and schema when connecting to Snowflake through the driver.
3. Issue a USE DATABASE or USE SCHEMA command within the session.

If the database or schema was specified by more than one of these, then the most recent one applies.

When CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX is set to TRUE:

If you want to search only the connection context database, but want to search all schemas within that database, see CLIENT_METADATA_USE_SESSION_DATABASE.

CLIENT_METADATA_USE_SESSION_DATABASE¶

Type:

Session — Can be set for Account » User » Session

Data Type:

Boolean

Clients:

JDBC

Description:

This parameter applies to only the methods affected by CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX.

This parameter applies only when both of the following conditions are met:

• CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX is FALSE or unset.
• No database or schema is passed to the relevant ODBC function or JDBC method.

For specific ODBC functions and JDBC methods, this parameter can change the default search scope from all databases to the current database. The narrower search typically returns fewer rows and executes more quickly.

For more details, see the information below.

Values:

TRUE:

The driver searches all schemas in the connection context’s database. (For more details about the connection context, see the documentation for CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX.)

FALSE:

The driver searches all schemas in all databases.

Default:

FALSE

Additional Notes:

When the database is null and the schema is null and CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX is FALSE:

CLIENT_METADATA_USE_SESSION_DATABASE	Behavior
FALSE	All schemas in all databases are searched.
TRUE	All schemas in the current database are searched.

Expand

Show lessSee more

CLIENT_PREFETCH_THREADS¶

Type:

Session — Can be set for Account » User » Session

Data Type:

Integer

Clients:

JDBC, ODBC, Python, .NET

Description:

Parameter that specifies the number of threads used by the client to pre-fetch large result sets. The driver will attempt to honor the parameter value, but defines the minimum and maximum values (depending on your system’s resources) to improve performance.

Values:

1 to 10

Default:

4

Most users should not need to set this parameter. If this parameter is not set by the user, the driver starts with the default specified above, but also actively manages its thread count conservatively to avoid using up all available memory.

CLIENT_RESULT_CHUNK_SIZE¶

Type:

Session — Can be set for Account » User » Session

Data Type:

Integer

Clients:

JDBC, Node.js, SQL API, Go

Description:

Parameter that specifies the maximum size of each set (or chunk) of query results to download (in MB). The JDBC driver downloads query results in chunks.

Also see CLIENT_MEMORY_LIMIT.

Values:

16 to 160

Default:

160

Most users should not need to set this parameter. If this parameter is not set by the user, the driver starts with the default specified above, but also actively manages its memory conservatively to avoid using up all available memory.

CLIENT_RESULT_COLUMN_CASE_INSENSITIVE¶

Type:

Session — Can be set for Account » User » Session

Data Type:

Boolean

Clients:

JDBC

Description:

Parameter that indicates whether to match column name case-insensitively in ResultSet.get* methods in JDBC.

Values:

TRUE: matches column names case-insensitively.

FALSE: matches column names case-sensitively.

Default:

FALSE

CLIENT_SESSION_KEEP_ALIVE¶

Type:

Session — Can be set for Account » User » Session

Data Type:

Boolean

Clients:

.NET, Golang, JDBC, Node.js, ODBC, Python,

Description:

Parameter that indicates whether to force a user to log in again after a period of inactivity in the session.

Values:

TRUE: Snowflake keeps the session active indefinitely as long as the connection is active, even if there is no activity from the user.

FALSE: The user must log in again after four hours of inactivity.

Default:

FALSE

CLIENT_SESSION_KEEP_ALIVE_HEARTBEAT_FREQUENCY¶

Type:

Session — Can be set for Account » User » Session

Data Type:

Integer

Clients:

SnowSQL, JDBC, ODBC, Python, Node.js

Description:

Number of seconds in-between client attempts to update the token for the session.

Values:

900 to 3600

Default:

3600

CLIENT_TIMESTAMP_TYPE_MAPPING¶

Type:

Session — Can be set for Account » User » Session

Data Type:

String (Constant)

Clients:

Any

Description:

Specifies the TIMESTAMP_* variation to use when binding timestamp variables for JDBC or ODBC applications that use the bind API to load data.

Values:

TIMESTAMP_LTZ or TIMESTAMP_NTZ

Default:

TIMESTAMP_LTZ

CORTEX_CODE_CLI_DAILY_EST_CREDIT_LIMIT_PER_USER¶

Type:

User — Can be set for Account » User

Data Type:

Number

Description:

Sets a daily estimated credit usage limit per user for Cortex Code CLI. Snowflake tracks the user’s estimated credit usage over a rolling 24-hour window and blocks access to the Cortex Code CLI when usage reaches the configured limit. Only users with the ACCOUNTADMIN role, or a role with sufficient privileges to modify the account or user object, can set this parameter. For more information, see Daily credit usage limits for CoCo.

Values:

• -1: No limit. The user has unlimited access.
• 0: Access is blocked entirely for the user.
• Positive number: Access is blocked when the user’s estimated credit usage in the past 24 hours exceeds this value.

Default:

-1 (no limit)

CORTEX_CODE_DESKTOP_DAILY_EST_CREDIT_LIMIT_PER_USER¶

Type:

User — Can be set for Account » User

Data Type:

Number

Description:

Sets a daily estimated credit usage limit per user for Cortex Code Desktop. Snowflake tracks the user’s estimated credit usage over a rolling 24-hour window and blocks access to Cortex Code Desktop when usage reaches the configured limit. Only users with the ACCOUNTADMIN role, or a role with sufficient privileges to modify the account or user object, can set this parameter. For more information, see Daily credit usage limits for CoCo.

Values:

• -1: No limit. The user has unlimited access.
• 0: Access is blocked entirely for the user.
• Positive number: Access is blocked when the user’s estimated credit usage in the past 24 hours exceeds this value.

Default:

-1 (no limit)

COCO_CLOUD_AGENTS_NON_SNOWFLAKE_EGRESS_DISABLED¶

Type:

Account — Can be set only for Account

Data Type:

Boolean

Description:

Controls whether the Cortex Code Cloud Agents sandbox in Snowflake can make outbound network connections to hosts outside Snowflake. For more information, see Cloud Agents.

Values:

TRUE: Non-Snowflake network egress from the Cloud Agents sandbox is disabled.

FALSE: Non-Snowflake network egress to platform-configured package registries and build tooling is allowed.

Default:

FALSE

Example:

ALTER ACCOUNT SET COCO_CLOUD_AGENTS_NON_SNOWFLAKE_EGRESS_DISABLED = TRUE;

COCO_SNOWSIGHT_ALLOW_ALL_PERMISSION_OPTIONS_DISABLED¶

Type:

Account — Can be set only for Account

Data Type:

Boolean

Description:

Controls whether users in Cortex Code in Snowsight can approve tool calls in bulk. When Cortex Code requests permission to run a tool call (for example, SQL execution or Bash), users are normally offered two allow-all options: Allow <tool> in this chat and Always allow <tool>. The CoCo side panel also includes a Bypass approvals mode that runs tool calls without individual prompts.

Setting this parameter to TRUE disables both allow-all options for all tool types, hides the approval-mode selector, and keeps the composer on Default approvals. Users must approve each tool call individually.

Values:

TRUE: Allow-all permission options (Allow <tool> in this chat and Always allow <tool>) are disabled, Bypass approvals is unavailable, and the composer stays on Default approvals. Users must approve each tool call individually.

FALSE: Allow-all permission options and Bypass approvals are available to users.

Default:

FALSE

Example:

ALTER ACCOUNT SET COCO_SNOWSIGHT_ALLOW_ALL_PERMISSION_OPTIONS_DISABLED = TRUE;

CORTEX_CODE_SNOWSIGHT_DAILY_EST_CREDIT_LIMIT_PER_USER¶

Type:

User — Can be set for Account » User

Data Type:

Number

Description:

Sets a daily estimated credit usage limit per user for Cortex Code in the Snowsight web interface. Snowflake tracks the user’s estimated credit usage over a rolling 24-hour window and blocks access to Cortex Code in Snowsight when usage reaches the configured limit. Only users with the ACCOUNTADMIN role, or a role with sufficient privileges to modify the account or user object, can set this parameter. For more information, see Daily credit usage limits for CoCo.

Values:

• -1: No limit. The user has unlimited access.
• 0: Access is blocked entirely for the user.
• Positive number: Access is blocked when the user’s estimated credit usage in the past 24 hours exceeds this value.

Default:

-1 (no limit)

CORTEX_MODELS_ALLOWLIST¶

Type:

Account — Can be set only for Account

Data Type:

String

Description:

Specifies the models that users in the account can access. Use this parameter to allowlist models for all users in the account. If you need to provide specific users with access beyond what you’ve specified in the allowlist, use role-based access control instead. For more information, see Account-level allowlist parameter.

When users make a request, Snowflake Cortex evaluates the parameter to determine whether the user can access the model.

Values:

• 'All': Provides access to all models, including fine-tuned models.

  Example:

  Copy code

  ALTER ACCOUNT SET CORTEX_MODELS_ALLOWLIST = 'All';
  

• 'model1,model2,...': Provides access to the models specified in a comma-separated list.

  Model names are case-sensitive and must be specified in lowercase.

  Example:

  Copy code

  ALTER ACCOUNT SET CORTEX_MODELS_ALLOWLIST = 'mistral-large2,llama3.1-70b';
  

• 'None': Prevents access to any model.

  Example:

  Copy code

  ALTER ACCOUNT SET CORTEX_MODELS_ALLOWLIST = 'None';
  

Default:

'All'

CORTEX_ENABLED_CROSS_REGION¶

Type:

Account — Can be set only for Account

Data Type:

String

Description:

Specifies the regions where an inference request may be processed in case the request cannot be processed in the region where request is originally placed. Specifying DISABLED disables cross-region inferencing. For examples and details, see Cross-region inference.

Values:

This parameter can be set to one of the following:

• DISABLED
• ANY_REGION
• Comma-separated list including one or more of the following values:
  • AWS_JP
  • AWS_APJ
  • AWS_AU
  • AWS_EU
  • AWS_US
  • AWS_GLOBAL
  • AZURE_EU
  • AZURE_US
  • AZURE_GLOBAL
  • GCP_US
  • GCP_GLOBAL

Explanation of each parameter value

Value	Behavior
DISABLED	Inference requests will be handled in: The region where the request is placed.
ANY_REGION	Inference requests may be routed to: Any region that supports cross-region inference (listed in this table) and that has availability, including the region where the request is placed.
AWS_JP	Inference requests will be handled in the region where the request is placed and in the following AWS regions AWS Asia Pacific (Tokyo) ap-northeast-1 AWS Asia Pacific (Osaka) ap-northeast-3
AWS_APJ	Inference requests will be handled in the region where the request is placed and in the following AWS regions AWS Asia Pacific (Tokyo) ap-northeast-1 AWS Asia Pacific (Seoul) ap-northeast-2 AWS Asia Pacific (Osaka) ap-northeast-3 AWS Asia Pacific (Mumbai) ap-south-1 AWS Asia Pacific (Hyderabad) ap-south-2 AWS Asia Pacific (Singapore) ap-southeast-1 AWS Asia Pacific (Sydney) ap-southeast-2 AWS Asia Pacific (Melbourne) ap-southeast-4
AWS_AU	Inference requests will be handled in the region where the request is placed and in the following AWS regions AWS Asia Pacific (Sydney) ap-southeast-2 AWS Asia Pacific (Melbourne) ap-southeast-4
AWS_EU	Inference requests will be handled in the region where the request is placed and in the following AWS regions, which are (and will be) located within the European Union: AWS Europe (Frankfurt) eu-central-1 AWS Europe (Stockholm) eu-north-1 AWS Europe (Milan) eu-south-1 AWS Europe (Spain) eu-south-2 AWS Europe (Ireland) eu-west-1 AWS Europe (Paris) eu-west-3
AWS_US	Inference requests will be handled in the region where the request is placed and in the following AWS regions, which are (and will be) located within the United States: AWS US East (N. Virginia) us-east-1 AWS US East (Ohio) us-east-2 AWS US West (Oregon) us-west-2
AWS_GLOBAL	Inference requests will be handled in the region where the request is placed and in any AWS commercial region.
AZURE_EU	Inference requests will be handled in the region where the request is placed and in the following Azure regions, which are (and will be) located within the European Union: Azure Europe (Netherlands) westeurope Azure Europe (France) francecentral Azure Europe (Germany) germanywestcentral Azure Europe (Italy) italynorth Azure Europe (Poland) polandcentral Azure Europe (Spain) spaincentral Azure Europe (Sweden) swedencentral
AZURE_US	Inference requests will be handled in the region where the request is placed and in the following Azure regions, which are (and will be) located within the United States: Azure US (Virginia) eastus2 Azure US (Virginia) eastus Azure US (California) westus Azure US (Phoenix) westus3 Azure US (Illinois) northcentralus Azure US (Texas) southcentralus
AZURE_GLOBAL	Inference requests will be handled in the region where the request is placed and in any Azure commercial region.
GCP_US	Inference requests will be handled in the region where the request is placed and in the following GCP regions, which are (and will be) located within the United States: GCP US (Iowa) us-central1 GCP US (Oregon) us-west1 GCP US (Las Vegas) us-west4 GCP US (N. Virginia) us-east4
GCP_GLOBAL	Inference requests will be handled in the region where the request is placed and in any GCP commercial region.

Expand

Show lessSee more

Default:

The default value depends on when the account was created and where it is located:

• ANY_REGION for new accounts in new organizations within commercial regions created after March 9, 2026.
• A same-cloud geography value for commercial accounts that have not set this parameter, as shown in the following table. Requests stay within that cloud provider.
• DISABLED for government, FedRAMP, and VPS accounts, and for commercial regions with no same-cloud geography value.

An explicit account-level value, including DISABLED, is unchanged.

Account cloud and geography	Default
AWS in the United States or Canada	AWS_US
AWS in Ireland, Frankfurt, London, Paris, Stockholm, or Zurich	AWS_EU
AWS in Japan	AWS_JP
AWS in Australia	AWS_AU
AWS in Seoul, Mumbai, Singapore, Jakarta, Malaysia, New Zealand, or Thailand	AWS_APJ
Azure in the United States, Canada, or Mexico	AZURE_US
Azure in Ireland, the Netherlands, the United Kingdom, Switzerland, or Sweden	AZURE_EU
Google Cloud in the United States	GCP_US
All other commercial regions	DISABLED

Expand

Show lessSee more

For the value assigned to each cloud region, see the 2026_06 behavior change.

To see the value in effect for your account: