Defining Snowflake Table Indexes
The following properties are applicable to a Snowflake Table Index object.
Tab |
Section |
Property |
Description |
Additional Properties |
---|---|---|---|---|
Physical Name | Specifies the physical name of the table index |
|
||
Type | Specifies the table index type |
|
||
Generate | Specifies whether SQL is generated for the index during forward engineering |
|
||
Generate As Constraint | Indicates that when the index is generated, it will be generated as a constraint |
|
||
Members | Index Members | Column | Specifies the key columns that define the index structure for organizing and searching data | |
Also Include | Column | Specifies non-key columns added to the index to enhance query performance | ||
Snowflake | Properties | Enforced | Specifies that the constraint must be actively enforced by the database engine |
Enforced: Specifies that the constraint is actively enforced on the table. Not Enforced: Specifies that the constraint is defined but not actively enforced. |
Deferrable | Indicates whether the constraint check can be postponed until the end of a transaction |
Deferrable: Specifies that the constraint can be deferred until the end of the transaction. Not Deferrable: Specifies that the constraint must be checked immediately after each statement. |
||
Initially | Specifies the default timing for constraint enforcement |
Deferred: Specifies that the validation action is postponed until a later point in the transaction. Immediate: Specifies that the validation action is executed immediately upon statement execution. |
||
Enable/Disable | Allows toggling the constraint on or off without dropping it |
Enable: Specifies that the selected feature or constraint is activated. Disable: Specifies that the selected feature or constraint is deactivated. |
||
Do Validate | Specifies whether existing data should be checked against the constraint |
Validate: Specifies that the data must be validated against the defined constraints. No Validate: Specifies that data validation against the defined constraints is skipped. |
||
Rely | Marks the constraint as trusted by the optimizer without enforcing or validating it |
Rely: Specifies that the constraint should be relied upon by the database during query optimization. No Rely: Specifies that the constraint should not be relied upon by the database for optimization purposes. |
Copyright © 2025 Quest Software, Inc. |