SAP high workload when qlikview reload via SAP connector

[#1]

Dear Guru,

Just received the feedback from SAP basis team the SAP workload is very high when qlikview reload from SAP.

Can anyone please advice if there is any way that something can be done to optimize the problem?

[suniljain]

if you are extracting cluster table then definitely it high workload in SAP.

because it is cluster in nature.

I will suggest you to extract huge table with related header table.

Like

LIKP ->LIPS,

MKPF->MSEG,

BKPF->BSEG,

etc.....

if you require any help pls reply me.

[disqr_rm]

If you are putting WHERE conditions in your queries at QV side, please consider creating secondary indexes at SAP side for those fields in the table. Now you may not want to create too many indexes in SAP and your BASIS group may have concerns about it. In that case, you may want to optimize your queries to use any existing indexes and may be extract more data than you need and then filter records at QV side.

If you have problem with any specific table/fields you may post here.

[suniljain]

if you put copmlex where condition during extraction it will definitely slow extraction peocess. and also put extra load sap r/3 system.

try to put where condition on QVD.

[#5]

Hi Sunil,

What do you mean by "extract huge table with related header table"?

Because I'm also planning to optimize our data extraction. Would you give me some tips?

Thank you.

Regards,

Lester

[#6]

Hi Sunil,

What do you mean by "extract huge table with related header table"?

Because I'm also planning to optimize our data extraction. Would you give me some tips?

Thank you.

Regards,

Lester

[#7]

Hi Sunil,

What do you mean by "extract huge table with related header table"?

Because I'm also planning to optimize our data extraction. Would you give me some tips?

Thank you.

Regards,

Lester

[#8]

Hi Sunil,

What do you mean by "extract huge table with related header table"?

Because I'm also planning to optimize our data extraction. Would you give me some tips?

Thank you.

Regards,

Lester