Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Star schema**: One central fact table; dimensions connected directly; denormalized dimensions. **Snowflake**: Normalized dimensions (dim → sub-dim). **Normalized (3NF)**: Many tables, minimal redundancy. **Star benefits**: Simpler queries, fewer JOINs, optimized for analytics,...
Star schema: One central fact table; dimensions connected directly; denormalized dimensions. Snowflake: Normalized dimensions (dim → sub-dim). Normalized (3NF): Many tables, minimal redundancy. Star benefits: Simpler queries, fewer JOINs, optimized for analytics, intuitive for BI. Snowflake adds flexibility, reduces redundancy—useful when dimension hierarchies are complex and storage matters. Normalized: Less redundancy; complex for analytics. Why star for analytics: Query simplicity and performance; BI tools expect star. Scalability trade-offs: Star can duplicate dimension attributes; snowflake reduces that at cost of joins. Cost: Star = more storage, faster reads; normalized = less storage, slower reads.
Red Flag: Proposing normalized schema for analytics without justification. Pro-Move: 'Star for marts; we snowflaked only the product hierarchy (50+ levels).'
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.