ALTER DCM PROJECT¶

Modifies the properties of an existing DCM project.

See also:: CREATE DCM PROJECT , DESCRIBE DCM PROJECT, DROP DCM PROJECT, EXECUTE DCM PROJECT, SHOW DCM PROJECTS, SHOW DEPLOYMENTS IN DCM PROJECT

Syntax¶

ALTER DCM PROJECT [ IF EXISTS ] <name> SET
  [ LOG_LEVEL = <log_level> ]
  [ COMMENT = '<string_literal>' ]

ALTER DCM PROJECT [ IF EXISTS ] <name> UNSET
  [ LOG_LEVEL ]
  [ COMMENT ]

Required parameters¶

name

Specifies the identifier for the DCM project 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.

SET ...

Sets one or more specified properties or parameters for the DCM project:

Optional parameters

LOG_LEVEL = log_level

Sets the logging level for the DCM project.

For more information about levels, see LOG_LEVEL. For information about setting the log level, see Setting levels for logging, metrics, and tracing.

The value can be one of the following:

TRACE
DEBUG
INFO
WARN
ERROR
FATAL
OFF

Default: OFF

COMMENT = 'string_literal'

Adds a comment or overwrites an existing comment for the DCM project.

UNSET ...

Unsets one or more specified properties or parameters for the DCM project, which resets the properties to their defaults:

LOG_LEVEL
COMMENT

To unset multiple properties or parameters with a single ALTER statement, separate each property or parameter with a comma.

When unsetting a property or parameter, specify only the property or parameter name (unless the syntax above indicates that you should specify the value). Specifying the value returns an error.

Access control requirements¶

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


Privilege	Object	Notes
OWNERSHIP	DCM project	OWNERSHIP is a special privilege on an object that is automatically granted to the role that created the object, but can also be transferred using the GRANT OWNERSHIP command to a different role by the owning role (or any role with the MANAGE GRANTS privilege).

Operating on an object in a schema requires at least one privilege on the parent database and at least one privilege on the parent 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 sets the logging level for the DCM project named my_project to DEBUG:

ALTER DCM PROJECT my_project SET LOG_LEVEL = DEBUG;

The following example adds a comment to the DCM project named my_project:

ALTER DCM PROJECT my_project SET COMMENT = 'Updated project for Q4 data management';