ALTER EXPERIMENT¶

Syntax¶

ALTER EXPERIMENT <experiment_name> ADD RUN <run_name>

ALTER EXPERIMENT <experiment_name> COMMIT RUN <run_name>

ALTER EXPERIMENT <experiment_name> DROP RUN <run_name>

Parameters¶

experiment_name

Specifies the identifier for the experiment to alter.

If the identifier contains spaces or special characters, the entire string must be enclosed in double quotes. Identifiers enclosed in double quotes are also case-sensitive.

For more information, see Identifier requirements.

ADD RUN run_name

Adds a new run with the identifier run_name; must be unique for the runs in experiment experiment_name.

For information on how to manually conduct an experiment run in SQL, see Start an experiment run.

If the identifier contains spaces or special characters, the entire string must be enclosed in double quotes. Identifiers enclosed in double quotes are also case-sensitive.

For more information, see Identifier requirements.

COMMIT RUN run_name

Completes the run with the identifier run_name for experiment experiment_name. Committed runs can’t be altered.

If the identifier contains spaces or special characters, the entire string must be enclosed in double quotes. Identifiers enclosed in double quotes are also case-sensitive.

For more information, see Identifier requirements.

For information on how to retrieve the results and artifacts of an experiment run, see Complete a run.

DROP RUN run_name

Deletes the run with the identifier run_name.

Access control requirements¶

A role used to execute this operation must have the following privileges at a minimum:

The USAGE privilege on the parent database and schema are required to perform operations on any object in a schema. Note that a role granted any privilege on a schema allows that role to resolve the schema. For example, a role granted CREATE privilege on a schema can create objects on that schema without also having USAGE granted on that schema.

For instructions on creating a custom role with a specified set of privileges, see Creating custom roles.

For general information about roles and privilege grants for performing SQL actions on securable objects, see Overview of Access Control.

Usage notes¶

• Regarding metadata:

  Attention

  Customers should ensure that no personal data (other than for a User object), sensitive data, export-controlled data, or other regulated data is entered as metadata when using the Snowflake service. For more information, see Metadata fields in Snowflake.

Examples¶

The following example creates a new run named run_1 in the experiment my_experiment:

ALTER EXPERIMENT my_experiment ADD RUN run_1;

The following example completes and records the run named run_1 in the experiment my_experiment:

ALTER EXPERIMENT my_experiment COMMIT RUN run_1;