SAP Knowledge Base Article - Preview

2156717 - NLS: Queries with navigation attributes/hierarchy node restrictions are slow

Symptom

You execute a Query on an InfoProvider for which a data archiving process (DAP) is defined and that archives data to a connected near-line storage solution (NLS).
In the Query Designer and/or in the metadata settings of the InfoProvider, you have specified that the Query should also take NLS data into account.

  • You also select navigation attributes in the Query and you notice a significantly longer runtime for the Query with NLS data taken into account compared with the runtime of a Query that accesses only data from BW itself. The same applies when mainly these are used to filter data in the Query result, and no other filter is applied.
  • Selecting hierarchy nodes can result in the same issue depending on the number of leafs the node has to be resolved to.


Read more...

Environment

SAP BW release independent

Product

SAP BW/4HANA all versions ; SAP NetWeaver all versions

Keywords

Performance, Virtual Provider, Remote Cube, RemoteCube, archiving, archive, filter, ADAPT_SELDR, IF_RSDRV_VPROV_INT_QUERY~DEFINE, DEFINE, attribut, hierarchy, SAP IQ , KBA , BW-BEX-OT-VC , Virtual Cube (Remote Cube) , BW-BEX-OT , OLAP Technology , BW-WHM-DST-ARC , Archiving , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.