Hello,
I'm trying to compare performance of calculation view to regular SQL:
SELECTtop 200 lpad("STA_ID",30,'0') ,lpad(to_nvarchar("INSERT_TIME",'YYYYMMDDHH24MISS'),15,'0')
FROM"SSIS"."OFFK470"
ORDERBY"STA_ID"ASC
successfully executed in 761 ms 977 µs(server processing time: 720 ms 483 µs)
Fetched 200 row(s) in 35 ms 614 µs (server processing time: 0 ms 289 µs)
To:
SELECT top 200"INSRT_TIME_CALC", "STA_ID_CALC_copy_1"
FROM"_SYS_BIC"."TEST/COPY_2_OF_STA_OMRI_O"
ORDERBY"STA_ID_CALC_copy_1"ASC
successfully executed in 15.943 seconds(server processing time: 15.910 seconds)
Fetched 200 row(s) in 41 ms 583 µs (server processing time: 0 ms 370 µs)
The CV "TEST/COPY_2_OF_STA_OMRI_O" contains 2 calculated columns with exactly the same logic as in the SQL.
When comparing the visio plan I clearly see that it materialize result
Can someone suggest how to improve the CV performance?
Thanks,
Amir
Hi Amir,
Kindly check following articles. Hope it helps
https://archive.sap.com/discussions/thread/3397688
https://blogs.sap.com/2015/08/05/performance-bits-and-bites-for-sap-hana-calculation-views/
Regards,
Rupali S
Hi Rupali,
Can you please be more specific? As you can see from my printscreens the visio plan display the exact issue. the question is why it is hapenning.
I tried also with ABAP CDS table function and it works exactly like the regular SQL.
Thanks,
Amir