Indexes
The Indexes feature in AnalyticsCreator defines the physical SQL index configuration applied to database tables during generation. Indexes are created as part of the deployment scripts for supported SQL targets.
Function
Indexes improve query performance and enforce physical data structures on generated tables. They are defined at the table level and can include standard SQL indexing features such as primary keys, uniqueness, clustering, column ordering, and compression type.
Access
Index definitions are created and managed via the Index Details window in the Editor. Each index is associated with a specific Schema and Table within the project.
Properties
| Property | Description |
|---|---|
| Schema | Target schema where the index will be applied |
| Table | Table to which the index belongs |
| Index Name | Logical name of the index in the deployment script |
| Description | Optional comment describing the index purpose |
| Compression Type | Specifies index storage format (e.g., COLUMNSTORE INDEX) |
| Is Unique | Marks the index as enforcing uniqueness |
| Is Primary Key | Flags the index as a primary key constraint |
| Is Clustered | Indicates that the index defines the physical data order |
| Is Columnstore | Indicates the use of a columnstore format for the index |
Screen Overview
The image below shows the List Indexes interface with columns labeled for easy identification
Behavior
- Indexes are created during SQL generation if enabled in the deployment settings
- Each table may define multiple indexes based on platform support
- Primary key flags enforce both uniqueness and clustering by default (unless overridden)
- Compression type and columnstore flags may be mutually exclusive depending on target
Supported Compression Types
- Columnstore Index – Read-optimized compressed index for large tables
- None – Standard row-based index without compression
Notes
- Index features are platform-dependent; not all types apply to all targets
- For OneLake delta tables, indexes are not physically created
- Index metadata is stored in the project file and regenerated per environment
