Reviewed by Aditya Kumar · Last reviewed 2026-03-24
Star: One fact, denormalized dimensions—simple, fewer joins, fast. Snowflake: Normalized dimensions (e.g., dim_product → dim_category → dim_category_group)—more joins, less redundancy. Why Snowflake: When dimension tables are large and shared—a single dim_category serves many...
Red Flag: Saying 'Snowflake is always better for normalization' without addressing query performance. Pro-Move: 'We kept product dimension normalized (saves 40% storage) but flattened customer—queried 10x more—into Star for join performance'—shows trade-off analysis.
This medium-level SQL question appears frequently in data engineering interviews at companies like Goldman Sachs, Microsoft, ZS Associates. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (join, snowflake) will help you answer variations of this question confidently.
Break this problem into components. Identify the core trade-offs involved, then walk the interviewer through your reasoning step by step. Demonstrate awareness of edge cases and production considerations - this is what separates good answers from great ones.
Star: One fact, denormalized dimensions—simple, fewer joins, fast. Snowflake: Normalized dimensions (e.g., dim_product → dim_category → dim_category_group)—more joins, less redundancy. Why Snowflake: When dimension tables are large and shared—a single dim_category serves many products; denormalizing would duplicate millions of rows. Avoids inconsistent attributes across copies (e.g., category name updated in one place). Storage: Snowflake saves space when hierarchy is deep and wide. Trade-off: More joins = more complexity and potential perf hit in some engines. When Star wins: Query latency paramount, dimensions small enough to broadcast, denormalization acceptable. Cost: Snowflake reduces storage; Star reduces compute (fewer joins). Best practice: Start Star; normalize only dimensions that are large or change independently.
Red Flag: Saying 'Snowflake is always better for normalization' without addressing query performance. Pro-Move: 'We kept product dimension normalized (saves 40% storage) but flattened customer—queried 10x more—into Star for join performance'—shows trade-off analysis.
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 3 companies. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.