Support append-only strategy in Silver layer alongside SCD2?

[aldamiz-orange]

Hi Erwin,

First, thanks for FMD — we’re using it on a Fabric engagement and it has been a real accelerator.

I wanted to raise one design question around the Silver layer. From what I understand, SCD2 is currently the standard historization approach, which makes sense for dimensions and mutable business entities.

My question is whether you also plan to support an append-only strategy for event-grained / additive fact entities.

The main reason is downstream Materialized Lake Views (MLVs) in Fabric. Incremental refresh there depends on append-only behavior. With SCD2, previous rows are expired, so the table no longer behaves as append-only, which can limit efficient downstream incremental refresh. For high-volume transactional facts, this can become a relevant constraint.

So the idea would be:

keep SCD2 as the default for state-oriented entities
allow append-only for additive/event-style facts where downstream incremental processing and clean additive semantics are more important

Is this already on your roadmap, or have you considered this design trade-off already?

Happy to discuss further or contribute if useful.

Thanks,
Juan

[edkreuk]

@aldamiz-orange great to hear and please make some noise on the socials, that you're using it. Your idea is not on the roadmap. CDF is enabled in Silver will that help to only append the new records to a new table or similar. What will happen if a record got update in the fact. Then you also have some challenges with append only. Could you elaborate a bit more on that. Happy to hear you thoughts on a way of implementing this