When creating a mixed scenario with SAP BW/4HANA and SAP HANA, what aspects should be considered for optimal performance? There are 3 correct answers to this question.

Question

Options

• AData latency
• BData volume
• CQuery runtime
• DMaintenance overhead
• ENetwork bandwidth

• A
  56% (24)
• D
  30% (13)
• E
  14% (6)

Explanation

In a mixed SAP BW/4HANA and SAP HANA scenario, data latency (A) matters because BW/4HANA typically uses scheduled ETL loads while HANA can serve near-real-time data - understanding when data was last refreshed is essential to avoid stale reporting. Data volume (B) directly impacts memory footprint, load times, and partitioning strategy, since HANA is an in-memory database where sizing missteps degrade performance significantly. Query runtime (C) must be optimized because queries can traverse both the BW semantic layer and raw HANA tables, making execution plan analysis and composite provider design critical.

Maintenance overhead (D) is an operational/administrative concern, not a runtime performance factor - it affects IT effort, not query or load speed. Network bandwidth (E) is largely a non-issue here because BW/4HANA runs natively on HANA; they share the same in-memory engine, so data movement between them is internal, not a network bottleneck.

Memory tip: Think "DVQ" - Data freshness, Volume sizing, Query speed - the three things that make or break a user's experience when querying a mixed landscape.

No community discussion yet for this question.