**Architectural Logic**: SCD0 (no history) to SCD3 (current + previous value) adds limited history without full Type 2 complexity. **Migration**: Add prev_value and effective_from columns; on update, shift current→previous before applying new value. **SQL**: `UPDATE dim SET prev_value = current_value, current_value = new_value, updated_at = NOW() WHERE key = X`. Or MERGE with equivalent logic....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Nagarro. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.