on 2018 Dec 03 1:56 PM
Hi gurus, I´ve a performance problem inserting a large result-set (180M), coming from a select clause, into Hana DB. Although the sql clause runs ok, when i add the insert clause, i get an OOM. I have studing the case carefully, and looking for a late materialization issue. The plan of the select with and without insert are the next:


In the insert, we dont have a Late Materialization processing. Since it´s an error new for me and is difficult to find appropiate documentation, i can´t figure out if thats the normal behaviour, or not. Should has the insert COLUMN SEARCH operator the LATE MATERIALIZATION processing?
lars.breddemann any inside advicing would be really appreciated! Sorry for the inconvenience, if you came to Mallorca you have some beers for sure 🙂
Kind regards!
Request clarification before answering.
For sure you have your beers! 🙂 Thanks for your help Lars, i´ve been working tunning the SQL in 2 main points:
- Partitioning destination table like you recomend--> get us major improvements in inserting time and memory consumption
- Rewriting logic from calculation view to plain sql--> major improvements in memory consumption.
At the end, the memory consumption becomes stable and in reazonable limits.
Thanks again Lars!!!!!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 13 | |
| 8 | |
| 7 | |
| 5 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.