**Architectural Logic**: SCD implementation depends on type; MERGE is the workhorse for atomicity. **SCD1**: UPDATE dim SET col = new_val WHERE key = X. **SCD2**: INSERT new row with effective_from; UPDATE current row's effective_to; set current_flag. **SCD3**: Add prev_col; on change, shift current→prev. **ETL Flow**: (1) Extract changed records. (2) Lookup dimension. (3) Apply SCD logic (MERGE or INSERT/UPDATE). (4) Generate surrogate keys....
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 BCG. 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.