so I attempted to build this as a POC for a client who is experiencing this overlapping type2 issue. My tables in question are relatively small (under 400k records), so VIEW performance does not scare me. also, as we pointed out, we can always materialize for performance as a last resort. however, the proposed solution here operates under the assumption that for every natural id (NId), there exists a current record (which ends on 12/31/9999). this is not always the case. some records need to have a specific end date assigned, with no subsequent record existing. under those circumstances, this approach will not work. any suggestions?
↧
