Dec 23, 2013

BoT, BoX or BoH (BW-on-HANA)

Question: What does Radio VOE (Voice of Experience) recommend about migrating  SAP-BW to
[1] Teradata;
[2] Exadata/Exalytics; or
[3] HANA
View  1: Attributes for customers with SAP applications as source system for 50%+ of critical data

View  2: Same information different visual

1.        BW-on-Teradata (BoT)

In the early 2000’s SAP partnered with Teradata as an alternative database for BW. To cut the story short globally there is currently only one customer with BW on Teradata and probably will always remain as the only customer to have ever taken a very short trip on a BoT (BW on Teradata). You don’t want to go there or ever take this path.. end of story
So that should lay to rest any endeavor for a BoT migration
PS the customer is currently seriously considering migrating their BoT to BoH in 2013..

2.       BoX (BW-on-Exadata) vs. BoH (BW-on-HANA):-

F     For BW-on-Exadata the foundational advice would be similar to the one for BW-on-TD. If 99% of the planet is going on one path don't try to reinvent another one on your own. There is inherent safety in numbers. Radio VOE has validated that the strategic advantage of following the herd far outweighs the adventurist assumptions & costs of being a loner, ie. Having the rare honor out being the 1:5000 implementations on a unique track does carry its own risks and disadvantages. The key decision is not only about tactical cost but about strategic Business Value.
       Keep this as your 'center-of-the-universe' decision factor of your final decision.


BoX (BW on Exadata)

BoH (BW-on-HANA)

What it really is


Business Application platform

What you get with BoH


Business Application Platform

Over 300 RDS solutions

Automated Database slimming applications

Predictive analytics platform

Prescriptive analytics capabilities

What you get with SoH


Over 900 prebuilt views for real-time operational views

Prebuilt Operational analytics that come free with SoH

Access to state-of-art analytics and informatics

Predictive analytics platform and algorithms


Will need Exadata Plus Exalytics, Plus

A license for every non PRD system including DR

Data base license, Plus Analytics engine

OLAP engine

Calculation engines and other applications

Check the total and final cost of ownership

All in one HANA platform and one price for PRD HANA. All other systems in the landscape come free

What type of db is this


In Memory, Columnar

Master Node RAM availability


1TB currently, 4 TB by Q2 of ’14 and 8-12TB by Q4 of ‘14


Exadata is an appliance

BW on HANA is an appliance

ACID compliance


Fully Compliant

Need for MOLAP, Aggregates, Caches



Very High Strength

Structured data - Oracle ERP

No seamless SAP integration

No seamless comprehension to SAP  config changes

Structured Data- integration to SAP Applications

100% seamless integration to SAP Master and transactional configurations

Seamless merging of multiple master data and source system deviances – on the fly in memory mergers

Medium Strength


Seamless Integration to semi Structured data


Unstructured pure Big Data

Unstructured pure Big Data

Partnered with Hadoop providers & Hadoop startups


Box compete with Teradata

HANA has no apparent competition for SAP customers.

No of Customers


2400+ to date

Additional Needs

Will need Exalytics to provide accelerated queries

Does not need any additional accelerators

HW selection

Only from Oracle

Monopoly in HW development, support and services. No competitive forces encouraged.

Multiple global HW partners approved by SAP . This leads to customer advantage as it leverages automatic market driven  competitiveness and development between HW partners

Who are the top 2 HW leaders

Oracle, Oracle and Oracle

HP is currently reported to be in the leadership position for HANA appliance installations followed by IBM

Strategic Impact

Does not align with SAP Suites strategy

Aligns to the HANA One-database strategy where customers get actual gains of HANA. Zero latency between OLTP and OLAP

How does it transform

Disc to server and back.

Data is passed from server to server till results are compiled. There is a need to break up responses


All the calculations are done in memory in the db itself

No need to break up responses

How does it perform

Slower than Teradata

Oracle Benchmark: 10 bill records <10 o:p="" secs="">

Fastest on the planet

My experience 45 billion records < 1sec

SAP Benchmark- 240 billion records < 1sec

Maturity of the technology

Is equivalent to BW Accelerator

Undisputed global leader

How does it work

1.  Database server to

2.  Compute server to

3.  Storage cells to Exadata cells

All in-memory

Data Loading

1.        ETL files in DBFS

2.        Oracle golden Gate

3.        Streams

4.        3rd Party

1.        Data integration tools

2.        SLT (Real-time from ECC

3.        BODS for batch loads

4.        DXC direct BW


Every system in the landscape is subject to a license

1.        DEV, Test, QA, and PROD

2.        HA, RD and Training

3.        Other, i.e. Projects landscape

Only PROD is licensed

All other systems and Free (not licensed)

What you get

Traditional DB accelerator

1.        Traditional ‘Wait & Debate’ engine

2.        Database

3.        Transaction Engine

Everything else supposedly are separate tools and licenses

Breakthrough HANA Platoform

1.        Real-time ‘Business NOW’ engine

2.        Database

3.        Transaction Engine

4.        Dimensional Engine

5.        Analytics Engine

6.        Predictive Engine

7.        Text Engine

Modeling methodology

Traditional- 10+ steps

ODS> ETL> DW> caching> Indexing> Aggregates> Query> Calculation Engine> Query Transforms> RESULTS

Breakthrough 3-steps

DSO> In-Memory Analytics> RESULTS

Impact of modeling method

·         Latency between operational and decision data

·         Infrastructure intensive

·         Expensive by system resources

·         Creates duplicates and is slow

Up to 1,000 times faster

No indexing or aggregates

Calculation / Transformation methodology


·         Most at OLAP (Query) layer – extremely inefficient

·         Rest in DW layer                    - Very Inefficient

Breakthrough calculation

·         Direct database transformations

·         Real-time db calculations

·         No mid-tier bottlenecks

Data-Center Impacts

·         Typically RAC (extra Costs)

·         Storage uses ASM failure groups

·         Box is a single point of failure

·         DR is a full license

Uses MPP automatic failover

Disaster recovery

·         License: full license for HCC, and even remote mirroring

·         2nd Exadata server/ non-Exadata server

·         Decompression to standard Oracle server possible with considerable performance loss

License: No extra Charge

Provided by HANA vendors

For SAP customers


All new functionalities only being developed on HANA

1.        BW seamless upgrade & migration in one step

2.        Over 900 views for ECC

3.        New RDS for CRM

4.        New RDS for SCM

5.        Industry specific solutions


1 comment:

  1. Hi Hari, I find very interesting part about Teradata. Actually I was not aware that BW can run on Teradata. Thans for sharing!