DataMasker for Oracle - Improvement for Range Split rules
When Using a Range Splitted Rule and one wants to auto generate the different ranges, damasker is launching following query (I will write just an example):
Select MIN(NUMERICFIELD) from MyTableToBeSplitted
Select MAX(NUMERICFIELD) from MyTableToBeSplitted
This will involve reading table twice (being the default plan through FULL TABLE ACCESS or INDEX).
Talking about big tables (which are the favourite target for Range Splitted Rules), this is too much time.
Instead, perhaps query could be changed to the following:
Select MIN(NUMERICFIELD) , MAX(NUMERICFIELD) from MyTableToBeSplitted
This will improve time spent, reducing it by a 50% as table will only be read once.
Thanks in advance,