Customer 360 Enterprise Data Platform — Denodo on Azure · View 20 of 39 · Runtime
Read the steps that are missing
- Five sources are in the view and only three are contacted. Branch pruning removed marketing and billing because no projected column came from them — that is where most of the federated performance comes from, not from the network.
- The crosswalk is read on every query and never from a cache, which is the cost of the correctness guarantee on view 07.
- Row filtering and masking are the last step before the result leaves. They are never pushed into a source predicate, so a mask cannot leak through a WHERE clause.
Numbers
- 1.9 s end to end against a 5 s Customer360 target; the SAP delegated aggregate is the longest single leg at about 700 ms.
- Case data came from a cache refreshed 4 minutes earlier, inside its declared 15-minute window.
Assumptions
- Source statistics are current enough for the cost-based optimiser to pick the join order. Stale statistics are the most common cause of a good plan turning bad and are refreshed weekly.
- The MPP scan is over gold Delta tables only; it never scans bronze.
