Essential cookies keep authentication working. With your permission, we also use analytics cookies to understand and improve the product. Read our Privacy Policy

DataEngPrep.tech
QuestionsPracticeAI CoachDashboardPricingBlog
ProLogin
Home/Questions/SQL/When would you choose a Snowflake schema over a Star schema?

When would you choose a Snowflake schema over a Star schema?

SQLmedium0.6 min read

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...

🤖 Analyze Your Answer
Frequency
Low
Asked at 3 companies
Category
487
questions in SQL
Difficulty Split
130E|271M|86H
in this category
Total Bank
1,863
across 7 categories
Asked at these companies
Goldman SachsMicrosoftZS Associates
Interview Pro Tip

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.

Key Concepts Tested
joinsnowflake

Why This Question Matters

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.

How to Approach This

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.

Expert Answer
110 words

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.

⚡
Pro Tip

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.

Want all answers as a PDF for offline study?
Seven focused volumes with 750+ in-depth answers — Answer Vault →
Related Study Guide
📘

Goldman Sachs Data Engineer Interview Questions & Answers (2026)

Practice the 41 most asked data engineering questions at Goldman Sachs. Covers SQL, Spark/Big Data, Behavioral and more.

8 min read →

Related SQL Questions

mediumWrite an SQL query to find the second-highest salary from an employee table.FreemediumDemonstrate the difference between DENSE_RANK() and RANK()FreemediumDiscuss differences between ROW_NUMBER(), RANK(), and DENSE_RANK(), and provide examples from your projects.FreemediumExplain the differences between Data Warehouse, Data Lake, and Delta LakeFreemediumExplain the differences between Repartition and Coalesce. When would you use each?Free

Level up your prep

Recommended
Educative
Educative Unlimited

800+ hands-on courses — Grokking System Design, Coding Patterns, and AI mock interviews for your DE loop.

Start learning →

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.

← Back to all questionsMore SQL questions →
Categories
All QuestionsSQLSpark / Big DataPython / CodingSystem DesignCloud / ToolsBehavioral
By Company
AmazonGoogleDatabricksSnowflakeAWSAzureMicrosoftNetflixUberTCS
Interview Guides
All GuidesTop SQL QuestionsTop Spark QuestionsPySpark QuestionsTop Python QuestionsTop System DesignKafka QuestionsAirflow QuestionsSQL Window FunctionsETL QuestionsData Modeling
Products
AI Interview CoachAnswer AnalyzerSQL PlaygroundResume AnalyzerAnswer Vault PDFsPricing
Company
About & Editorial PolicyContact UsAI DisclosureDisclaimerTerms of ServicePrivacy Policy
© 2026 DataEngPrep.tech. All rights reserved.
AboutBlogContactDisclaimer