Skip to main content

Module 20: Performance Optimization (BW/4HANA)

Performance in BW/4HANA is not about hardware alone — it is about correct design, modeling, and pushdown.
Most performance issues are design problems, not system limitations.

This module covers:

  • Data volume management
  • Partitioning strategies
  • Query performance tuning
  • HANA execution plans
  • BW analyzer & performance tools

1. Data Volume Management (Foundation)​

Why Data Volume Matters​

  • Larger datasets = slower queries
  • Higher memory consumption
  • Longer load and activation times
Rule of Thumb

If you don't control data volume, nothing else will scale.

Techniques for Data Volume Management​

TechniquePurpose
Delta loadingReduce load volume
Data agingManage historical data
ArchivingRemove obsolete data
Selective persistenceAvoid unnecessary storage
tip

Persist only what you analyze.

2. Partitioning Strategies (Very Important)​

2.1 What is Partitioning?​

Partitioning splits large tables into smaller, manageable chunks.

Typical partition keys:

  • Time (Fiscal Year / Month)
  • Organizational units

2.2 Partitioning in BW/4HANA​

  • aDSO tables
  • PSA tables
  • Change log tables
aDSO (Sales)
 ├─ 2023
 ├─ 2024
 └─ 2025

2.3 Best Practices for Partitioning​

DO

Use time-based partitioning
Align partitions with query filters

AVOID

Over-partitioning
Using low-cardinality fields

3. Query Performance Tuning​

3.1 Common Query Performance Killers​

Avoid These

Too many free characteristics
Complex CKFs
Deep drilldowns
Reporting directly on aDSOs

3.2 Query Optimization Techniques​

DO

Use CompositeProviders
Filter early
Reduce number of characteristics
Use RKFs instead of CKFs where possible

Query Design Rule​

Golden Rule

Model heavy, query light.

4. HANA Execution Plans (Advanced)​

4.1 What is a HANA Execution Plan?​

An execution plan shows:

  • How HANA processes a query
  • Join order
  • Filter pushdown
  • Estimated cost

4.2 Why Execution Plans Matter​

  • Identify bottlenecks
  • Validate pushdown
  • Compare alternative designs
info

Execution plans explain why a query is slow, not just that it is slow.

4.3 What to Look For​

IndicatorMeaning
Large intermediate resultsMissing filters
Expensive joinsBad join order
Full table scansNo pruning

5. BW Analyzer & Performance Tools​

5.1 BW Analyzer​

BW Analyzer helps analyze:

  • Query execution time
  • Backend processing steps
  • Data transfer volume

5.2 Additional Performance Tools​

ToolPurpose
HANA Studio / DB ExplorerExecution plans
ST05SQL trace
ST12Combined trace
RSRTQuery runtime analysis
Best Practice

Use BW Analyzer + HANA tools together.

6. Performance Optimization Workflow​

Detect Issue
   ↓
Identify Layer (Model / Query / DB)
   ↓
Analyze Execution Plan
   ↓
Optimize Design
   ↓
Validate Improvement

7. BW/4HANA vs Classic BW (Performance)​

AreaClassic BWBW/4HANA
AggregatesMandatoryEliminated
PushdownLimitedNative
Tuning focusQueryModel + HANA
ScalabilityModerateHigh

8. Common Performance Mistakes​

Avoid These

Adding aggregates (obsolete)
ABAP-heavy logic
Over-modeling
Ignoring execution plans

9. Interview-Grade Questions​

Q1. What is the most common BW/4HANA performance issue?​

Answer: Poor data modeling that prevents HANA pushdown, leading to excessive data movement and inefficient queries.

Q2. How do you analyze BW query performance?​

Answer: Using BW Analyzer, RSRT, and HANA execution plans to identify bottlenecks and optimize modeling or query design.

10. Summary​

  • Performance starts with design
  • Data volume must be controlled
  • Partitioning improves scalability
  • Execution plans are essential
  • Tools provide insight, not solutions

11. What's Next?​

➡️ Module 21: Security, Auditing & Compliance

Learning Tip

In BW/4HANA, performance tuning is architecture refinement.