ðŸ“ĶObject types

Object types are sorted in execution order. See explanation after the table.

Object type
CREATE
COMPARE
DROP
Notes

ACCOUNT_PARAMETER

N/A

UNSAFE +

N/A

ACCOUNTADMIN, skip on empty config

RESOURCE_MONITOR

UNSAFE

UNSAFE

UNSAFE

ACCOUNTADMIN

WAREHOUSE

SAFE

SAFE

SAFE

ACCOUNTADMIN to assign RESOURCE_MONITOR

WAREHOUSE_ROLE

SAFE

SAFE

SAFE

DATABASE

SAFE

UNSAFE

UNSAFE

SCHEMA

SAFE

UNSAFE

UNSAFE

SCHEMA_ROLE

SAFE

SAFE

SAFE

SECRET

SAFE

SAFE

SAFE

NETWORK_RULE

SAFE

SAFE and UNSAFE

UNSAFE

ALTER is safe, REPLACE is unsafe

EXTERNAL_ACCESS_INTEGRATION

SAFE

SAFE

SAFE

FILE_FORMAT

SAFE

SAFE

SAFE

Short hash

STAGE

SAFE

SAFE and UNSAFE

UNSAFE

SEQUENCE

SAFE

SAFE

UNSAFE

FUNCTION

SAFE

SAFE

SAFE

Short hash

EXTERNAL_FUNCTION

SAFE

SAFE

SAFE

Short hash

PROCEDURE

SAFE

SAFE

SAFE

Short hash

TABLE

SAFE

SAFE and UNSAFE +

UNSAFE

EVENT_TABLE

SAFE

SAFE and UNSAFE

UNSAFE

HYBRID_TABLE

SAFE

UNSAFE

UNSAFE

Short hash

DYNAMIC_TABLE

SAFE

SAFE and UNSAFE

UNSAFE

EXTERNAL_TABLE

SAFE

SAFE

SAFE

Short hash

PRIMARY_KEY

SAFE

SAFE

SAFE

UNIQUE_KEY

SAFE

SAFE

SAFE

FOREIGN_KEY

SAFE

SAFE

SAFE

STREAM

SAFE

UNSAFE

UNSAFE

MATERIALIZED_VIEW

SAFE

UNSAFE

UNSAFE

VIEW

SAFE

SAFE

SAFE

PIPE

SAFE

UNSAFE

UNSAFE

Short hash

TASK

SAFE

SAFE

SAFE

Short hash

ALERT

SAFE

SAFE

SAFE

SHARE (outbound)

UNSAFE +

UNSAFE +

UNSAFE +

TECHNICAL_ROLE

SAFE

SAFE

SAFE

BUSINESS_ROLE

SAFE

SAFE

SAFE

USER_ROLE

SAFE

SAFE

SAFE

USER

SAFE

UNSAFE

UNSAFE

AGGREGATION_POLICY

UNSAFE +

UNSAFE +

UNSAFE +

AUTHENTICATION_POLICY

UNSAFE +

UNSAFE +

UNSAFE +

MASKING_POLICY

UNSAFE +

UNSAFE +

UNSAFE +

NETWORK_POLICY

UNSAFE

UNSAFE

UNSAFE

PROJECTION_POLICY

UNSAFE +

UNSAFE +

UNSAFE +

ROW_ACCESS_POLICY

UNSAFE +

UNSAFE +

UNSAFE +

Notes

  • Safe & unsafe operations are explained in "Safe & unsafe DDL" guide.

  • Some role types are generated dynamically. You may read more in Role hierarchy guide.

  • + means that additional setting or CLI argument might be required to apply this change.

  • ACCOUNTADMIN note means that only user with this role can apply this change. It should be applied by human administrator manually or by SnowDDL user having this role automatically.

  • Short hash note means that objects of this type will have a short hash added to comment. It is explained in Short hash guide.

  • In some cases both "safe" and "unsafe" changes can be applied to the same object type and operation type. Please refer to specific object type documentation for more details.

Last updated