Quantcast
Channel: SCN: Message List - SAP HANA and In-Memory Computing
Viewing all articles
Browse latest Browse all 8968

Re: Analyzing designs using PlanViz and understanding Dominant Operators

$
0
0

Greetings,

 

Thank you for your response. You are correct we are dealing with a  high number of records for each of the tables. BSAK in particular is the slowest one as it contains the most number of records.

 

Just for reference, I hovered over the Pop operation as you suggested, and I get the following information. Unfortunately, I'm not able to analyze it properly, only useful tidbit is that it is the "BELNR" field that is causing the delay. This field is necessary as it is one of the keys that we are using to index into the BSEG table.

 

BwPop.PNG

 

We reduced as the data as much as possible at the base level in the attribute views, but the business case requires us to perform analysis on the resulting number of records which does include aggregations like sums and counts.

 

Just from a conceptual standpoint the main data sets are the following joins

 

1. (BSAK-BSEG ) - EKKO

2. (BSIK-BSEG) - EKKO

 

3. BSIS - EKKO

 

Originally, the union node only had the result of the 1 and 2 and the result time was < 2 s for a single query which is what we are aiming for. Then we had to add  3 to the union node and the aggregation just increased dramatically.  ( ~50 s for a single record)

 

If I run the queries individually on each of the data sets, I get the wanted ~2 s time for a single query.

 

But I need to bucket them together.

 

Is there another way to bucket them together?

 

 

Thank you for your time,

Luis


Viewing all articles
Browse latest Browse all 8968

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>