- Overview
- Platform setup and administration
- Platform setup and administration
- Platform architecture
- Data Bridge onboarding overview
- Connecting a Peak-managed data lake
- Connecting a customer-managed data lake
- Creating an AWS IAM role for Data Bridge
- Connecting a Snowflake data warehouse
- Connecting a Redshift data warehouse (public connectivity)
- Connecting a Redshift data warehouse (private connectivity)
- Reauthorizing a Snowflake OAuth connection
- Using Snowflake with Peak
- SQL Explorer overview
- Roles and permissions
- User management
- Inventory management solution
- Commercial pricing solution
- Merchandising solution
Using Snowflake with Peak
Snowflake-specific behavior in Peak, including incremental load support, audit fields, case-sensitive SQL semantics, and schema management considerations.
This page summarizes how Peak behaves when your organization uses Snowflake as the data warehouse.
Feeds
Snowflake supports incremental load only. When data is ingested, Peak appends audit fields such as peakauditcreatedate and feed-run-id.
SQL Explorer
Snowflake uses case-sensitive SQL semantics. Unquoted identifiers are stored and resolved in uppercase. Use double quotes if you need to preserve lowercase identifiers.
Images and Workspaces
When you build images for Workspaces, Workflows, or Web Apps, include Snowflake connectors, drivers, and connection parameters. Store credentials as environment variables prefixed with SNOWFLAKE_.
Dashboards
Snowflake requires explicit column selection and consistent case handling. If a column name uses lowercase, wrap it in double quotes and define an alias. Avoid using * in queries when lowercase identifiers are used.