why is ETL stream so frustrating to optimize? like 80% of my

File: Screenshot (13).png (195KB, 1920x1080px) Image search: [Google]

195KB, 1920x1080px

why is ETL stream so frustrating to optimize?
like 80% of my time is for dwh query optimization.............................
can some of you masters explain to me on a technical layer why i cant do this:


alter table sales
as partition pjune2018 values less than(to_date())
tablespace tbsjune2018;

to create only one collector to store all the exceptions? a null argoument can't be viewed as 'if nothing of the previous partitions' as in every language in the world?