SAP Knowledge Base Article - Public

3423607 - Bad performance for specific Odata query import job

Symptom

  • Bad performance for specific Odata query import job

Environment

  • SAP Analytics Cloud (Enterprise)

Reproducing the Issue

  1. Create an import job based on a Odata query and set the batch size to be max value 50000.
  2. Run the import job and it takes very long time (20 mins) to finish.
  3. Try to run the same query in postman, it takes much less time (around 1 mins) to get data.

Cause

 The client side(SAC) pagination (batch size = 50k) is being overwritten by the OData service. There is server side pagination implemented in the OData service. 

Resolution

Modify the Odata service side pagination limit setting to allow larger size, eg:50k.

See Also

Your feedback is important to help us improve our knowledge base.

Keywords

Odata batch , KBA , LOD-ANA-AQU-ODATA , Acquiring Data into SAC using an ODATA connection , Problem

Product

SAP Analytics Cloud 1.0