Qlik Community

QlikView Connectors


Breathe easy -- you now have more time to plan your next steps with Qlik!
QlikView 11.2 Extended Support is now valid through December 31, 2020. Click here for more information.


SAP SQL Connector - Problem with parallel extractions

Customer claims that is not possible to start parallel extractions, without having problems with it. The extraction aborts with time out errors or rfc erros.

They modified the reload tasks, extracting data in sequence, no more parallel extraction. For now the problems are gone and the extractions are stable, but the time frame is getting short.

Some  extractions have cluster tables as source, and they are queried using index fields. Also transparent transactional tables are extracted using dates as primary filter, like Billings and Sales Orders.

Any recomendation on which tables had to be extracted alone, and which one in parallel ?

How do I now if a select is using and index or is doing a full scan ?

Customer is using SAP Connector 5.2, and we are planning to migrate to 5.5 but he want to sure where is the problem, sap system, bad scripting or connector bug that is fixed on recent version.

4 Replies
Honored Contributor II

SAP SQL Connector - Problem with parallel extractions

Pablo, basis admin should be able to tell you if a select is doing a full scan or not.

You can also check index information on tables using transaction SE11. You should also check indexes on related tables. For example, recently in a customer, I found the extraction on FI tables (BSIS, BSAS, etc.) was faster going through the header table (BKPF), as it had date fields indexed than going straight to the detail table.

We tried to load as many extractions in parallel as we can, but mainly run parallel extractions on cluster tables like BSEG so the extraction doesn't take for ever.


SAP SQL Connector - Problem with parallel extractions


  Thank you for this valuable information. Will help a lot.

Not applicable

SAP SQL Connector - Problem with parallel extractions


In ST05 you can run sql trace on user to see what access to Databse is taken. For sales we have created index on creation date and change date to quickly extract VBAK and vbap for example.


Honored Contributor

SAP SQL Connector - Problem with parallel extractions

you sap connection abort only in case of qlikview application is unable to get response from sap server.

so my suggestion is to increase value of time out parameter in sap connection string so that your connection is not aborted.