Hybrid tables can be created via Diagram explorer (DB explorer) or reverse engineering (RE).
The following options and parameters are available for creating and configuring hybrid tables in Snowflake projects.
Hybrid tables properties
Naming and case-sensitivity
All SqlDBM objects must have a unique physical name (in physical project types), taking the schema into account. The logical name is used for metadata and descriptive purposes. See Snowflake Tables for additional details.
Indexes and constraints
Hybrid tables require a primary key (PK) and also support foreign keys, alternative keys, and Index keys. Clustering keys are not supported in hybrid tables.
Options
Options for Hybrid tables are shared with tables, except that Hybrid tables can not be Transient or Temporary, and they should not be created under Transient schemas. For details on other options, see Snowflake Tables.