SnowPro Advanced Architect

By Snowflake · Question Mode

QuestionQ111

Performance, Cost, and Resource Optimization

A Snowflake Architect expects that a table will contain several terabytes of data and therefore defines a custom cluster key across three columns to improve query performance. However, queries against the table still take a long time.

Why does this occur?

Explanation

A clustering key with excessively high cardinality cannot effectively group related rows into the same micro-partitions, reducing partition pruning and leaving scans slow. Snowflake recommends using an expression to reduce cardinality when a high-cardinality column must be used as a clustering key.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!