3 factors that impact hana cost

8/16/2019 3 Factors That Impact HANA Cost

1/43

© Copyright 2013Wellesley Information Services, Inc.

All rig hts reserved .

3 Critical Factors ThatImpact SAP HANA Costand ROI

Douglas Janes, Hewlett-PackardUddhav Gupta, SAP


2/43

1

In This Session …

• You will learn factors to consider before implementing SAP HANA,

including:

Hardware requirements

Requirements for the SAP HANA system, including sizing

and high availabili ty requirements

Additional systems that may be required Software impacts

SAP HANA licensing costs

Impacts to source systems Business use case scenarios and using rapid deployment

solutions (RDS) as a way to minimize implementation costs


3/43

2

What We’ll Cover …

• Hardware requirements

• Software impacts

• Business usage scenarios

• SAP HANA Pricing

• Wrap-up


4/43

3

Selecting the Correct SAP HANA System —

Sizing

• Available sizing tools from SAP

SAP Notes

SAP Note 1514966 (Non-BW data sources)

SAP Note 1637145 (BW data sources)

Notes include sizing papers and scripts to gather data from

source databases Quick Sizing tool (http://service.sap.com/quicksizing *)

Sizes a broad range of scenarios, including standalone, SAP

NetWeaver ®

BW powered by SAP HANA, and a variety ofapplications

Accepts data input from sizing note (above)

* Requires login credentials to the SAP Service Marketplace


5/43

4

Limits to SAP HANA Scalabil ity

• Current maximum size is 8TB RAM (16 SAP HANA nodes)

Equates to 28TB source system, assuming 3.5:1 effective

compression ratio

Certification restrict ion only

Scale out architectures are designed to increase in modular

fashion

4-nodebase

system

Add racks as needed

• Adds SAP HANA nodes (up to 4 per rack)

• Adds storage nodes (2 per rack)

• Adds disk array (local storage for storage nodes)

• Adds 10 GbE network switches and SAN

switches

40 Gbpsbetween

racks

Larger configurations will becertified based on market demand


6/43

5

Scalability — Other Factors to Consider

• Enterprise applications need more than simple scalability

Functionality

New RDS

New applications (e.g., SAP NetWeaver ® BW, SAP ERP)

New interfaces (e.g., Direct Extractor Connection – DXC)

Improved backup and recovery

Add incremental backup

Add integration with third-party tools

Backup installation and configuration files (bare-metalrecovery)

Disaster recovery

Certification complete – customer implementations underway


7/43

6

Scalability and Data Compression (Current

State)

• Data compression benefits

Reduces memory and disk requirements

Increases data read (query) performance

• Current limit to compression

Largely a function of converting from row-based to columnar

data store Effective compression l imited by database compression that is

already in effect

Highly dependent upon type of data Small number of unique values = high compression

Large number of unique values = low compression


8/43

7

Scalability and Compression (Future State)

DataCopies

Current State

Data copied between systems

• Significant amount of duplicate data

• Overhead on systems/networks to copy

data

Future StateSystems share SAP HANA database

• No duplicate data

• No overhead to copy data between

systems


9/43

8

Integration Options — Overview

• Choice of back-end and front-end systems can dictate

requirements for integration components (e.g., SLT) and vice

versa

SAP ERP, SAP

CRM, etc.

SAP HANA

Non-SAPSystem(s) SAP Data Services 4.0

BW (app server)

SLT

SAP BusinessObjects BIApplications 4.0


10/43

9

Possible Additional Systems

• SAP Landscape Transformation (SLT) server

Used to copy data into SAP HANA

Alternate to SRS

Preferred for replication scenarios

• SAP Data Services 4.0

Used to copy data into SAP HANA

Extract, Transform, and Load (ETL) scenarios

• Other SAP BusinessObjects 4.0 servers

Used to present data to end users


11/43

10

SAP Landscape Transformation (SLT) Server

• Most commonly used for SAP Business Suite applications (SAP

ERP and SAP CRM)

Supported on Basis release 4.6C and higher

Requires installation of DMIS 2010 1

Installation instructions included in SAP Note 1468391

• Support expanded to include databases for non-SAP systems Must be compliant with DB/OS restrictions for SAP

NetWeaver 7.02

Listed in Platform Availabil ity Matrix http://service.sap.com/pam (search for “ EHP2 NetWeaver” )

Requires login credentials to the SAP Service Marketplace


12/43

11

SLT Installation Options

• SLT can be installed on the source system in some cases

Advantage: Simpler landscape (no additional server needed)

Disadvantages

Places additional workload on the source system

Places additional restrictions on the source system

• Recommendation: Install SLT on separate system

Places fewest restrictions on source system

Same SLT system can be used for non-SAP systems


13/43

12

SLT Installation Requirements

• Must be compatible with DMIS 1 700

SAP NetWeaver 7.00 with 720 EXT kernel

See platform availabili ty matrix (PAM) for supported DB/OS

combination

http://service.sap.com/pam *

Select “ SAP NetWeaver 7.0” quick l ink Unicode database implementation required

• Minimum hardware requirements

100GB available space in fi le system 16 to 32GB RAM

2 to 4 processor cores



14/43

13

SAP Data Services

• Most flexible method to copy data into SAP HANA

SAP applications (e.g., SAP NetWeaver BW)

Non-SAP applications

Programming language APIs (e.g., C++)

Files (e.g., Excel spreadsheet)

• Provides options for complex integration scenarios

Merge data from multiple source systems

Perform data cleansing and transformation

• Potentially simpler/less expensive implementation May already have SAP BusinessObjects infrastructure

(licenses), including SAP Data Services


15/43

14

SAP Data Services — Installation

Requirements

• Minimum hardware requirements (single server)

2 to 4 CPUs

8GB RAM 23GB free space in f ilesystem

• Supports distributed landscape

Recommended if heavy workload is expected Components to install (may be part of large SAP BusinessObjects

installation)

BI (includes Web application server)

Job Server Access Server

Adaptive Processing Services

Central Management Console (CMS) – includes DB server


16/43

15

SAP Data Services — Installation

Requirements (cont.)

• Detailed l ist of hardware specifications by operating system

available from platform availabili ty matrix (PAM)

http://service.sap.com/pam *

Select “SBOP DATA SERVICES 4.0” quick link

Data Services 4.0 SP2 – Linux

Data Services 4.0 SP2 – Windows 32-bit Data Services 4.0 SP2 – Windows 64-bit

Data Services 4.0 SP2 – AIX 64-bit

Data Services 4.0 SP2 – Solaris 64-bit



17/43

16

SAP Data Services —

Sizing Requirements

Online Sizing Tool – Inputhttp://wiki.sdn.sap.com/wiki/display/EIM/DataServices+Performance+example

Source: SAP


18/43

17

SAP Data Services —

Sizing Requirements (cont.)

Online Sizing Tool – Output

Source: SAP


19/43

18

SAP BusinessObjects Front-End Servers

• SAP BusinessObjects 4.0 provides an extensive variety of

analytical and reporting tools that have been integrated with

SAP HANA Most commonly used with SAP HANA

SAP BusinessObjects Explorer — Many RDS make use of

Explorer SAP BusinessObjects Analysis, edition for OLAP (Web-

based)

SAP BusinessObjects Analysis, edition for Microsoft Office

Complete list available from product home page

www.sap.com/solutions/analytics/business-intelligence/

solutions-overview.epx


20/43

19

Sizing – SAP BusinessObjects ApplicationsSAP Quick Sizing

http://service.sap.com/quicksizing *

Additional tools:

• Explorer Sizing Guide (SAP Note 1577353)

• Business Information Sizing CompanionGuide

* Requires log in credentials to the SAP Service Marketplace


21/43

20

Direct Extractor Connection (DXC)• New ETL tool introduced by SAP

Limited transformation capabilities

• Uses Business Content DataSource Extractors (already used forSAP NetWeaver BW) to copy data into SAP HANA

• Does not require additional server

Default configuration makes use of embedded SAP NetWeaver

BW in SAP ERP systems based on SAP ECC 6.0 or higher

Uses HTTP connection to source system

• Sidecar approach available

Used for older versions of ECC (no embedded BW) Customers who do not wish to use embedded BW

Install SAP NetWeaver BW 7.x system external to ECC system

May use SAP NetWeaver BW powered by SAP HANA ifavailable


22/43

21

Special Considerations for Specif ic Solutions

• Some SAP HANA solutions place specific restrictions on the

source system, in addition to what is imposed by the desired

integration servers CO-PA Accelerator requires SAP ERP 6.0

Smart Meter Analytics requires SAP NetWeaver BW 7.30

SAP NetWeaver BW powered by SAP HANA requires SAPNetWeaver BW 7.30

• Some SAP HANA solutions dictate the choice of integration

servers

Smart Meter Analytics requires SAP Data Services 4.0


23/43

22






• Wrap-up


24/43

23

Impacts to Source System by SAP HANA

Solution

• CO-PA Accelerator example

SAP ERP 6.0 is required

May have to upgrade SAP ERP system as part ofimplementation

• SAP Smart Meter Analytics example

SAP NetWeaver BW 7.30 SPS 04 is required May have to upgrade SAP NetWeaver BW system

Alternatively, may have to set up special purpose SAP

NetWeaver BW system SAP BusinessObjects Data Services XI 4.0 SP02 is required


25/43

24

Impacts to Source System by Data Transfer

Method• Sybase Replication Server

Most restrictive of all the replication methods

No longer used for new implementations• SLT Server

SAP ERP and other ABAP applications

4.6C and higher — No upgrade needed for most customers Non-SAP databases

Must adhere to SAP NetWeaver 7.02 OS/DB restrictions

• SAP BusinessObjects Data Services

Imposes fewest restrictions on data sources

No real-time replication (scheduled data loads)

Supports lower data volumes compared to replication


26/43

25






• Wrap-up


27/43

26

Custom Implementation vs. Standard SAP

ContentSAP Delivered

Applications/ContentCustom

Applications/Content

Complexity

Consulting Services

Duration of Project

Cost

D e c r e a s

i n g

I n c r e a s

i n g


28/43


29/43

28

When to Implement Custom/Complex

Applications• Business Warehouse powered by SAP HANA example

Steps to implement

Upgrade SAP BusinessObjects to 4.0 Upgrade SAP NetWeaver Business Warehouse to 7.30

Optimize SAP NetWeaver Business Warehouse

Migrate database to SAP HANA Advantages

Improve query performance

Potentially simplify landscape by eliminating SAP NetWeaverBW Accelerator

Simplify administration (e.g., elimination of aggregates)

Summary: Benefits outweigh increased costs for more complex

project


30/43

29

Benefits of Rapid Deployment Solution

• Natural extension of appliance concept

Only SAP and certified partners (e.g., HP and Accenture) are

permitted to deliver solution• Reduced need for extensive in-house expertise or consulting

services significantly reduces cost of implementation

• Significantly reduces time to value if ready-made solutionmatches business needs


31/43


32/43

SAP HANA Pricing


33/43

© 2013 SAP AG. All rights reserved. 32

SAP HANA Pricing Overview

+SAP Named

Users

SAP HANA(Full use/Runtime)

=

SAP BusinessObjects BI Solutions(Package/A la carte)

TOTALSoftware cost

Hardware+

SAP HANAPremium Content

SAP HANAApplications

Required Licensable ComponentsA

Optional Licensable Components (must be purchased independently of SAP HANA)B

& &

Engine

Engine

Sold separately

by H/w partners


34/43

© 2013 SAP AG. All rights reserved. 33

Popular SAP HANA Engine SKUs

Database edition forSAP NetWeaver BW(RUNTIME license –limited to use with

SAP NetWeaver BW)

Enterprise edition(FULL USE)

SAP HANA Engine

SAP HANA

SAP BusinessObjects Data Integrator

SAP Landscape Transformation s/w

SAP HANA Data Distribution Rights

SAP HANA Engine

SAP HANA

SAP Direct Extractor Connection s/w

SAP HANA Engine

SAP HANA

Platform Edition(FULL USE)

Memory that may be used by SAP HANA software as measured in gigabytes (GB)

1 Unit of SAP HANA = 64GB of Memory

SOFTWARE LICENSE FOR PRODUCTION SYSTEMS COVERS THE RIGHTS TO USE

FOR NON-PRODUCTION SYSTEMS


35/43

SAP HANA Licensing Options

34

1 Database license is appropriate for BW only scenarios

2 Platform license is appropriate when SAP BusinessObjects 4.0 licensing, including SAP Data Services, is already in

place

3 Data Services

$

$$$

Already own

Data Services

4.0?

Choose

Platform EditionY

SAP approval

for SRS?

Choose

Extended Edition

N

Y

Choose

Enterprise Edition

N

BW only?

N

Choose

Database EditionY

License Core DS3/

SLT

SRS

Database1 X

Platform2 X

Enterprise X X

Extended X X X


36/43

35






• Wrap-up


37/43

36

SAP HANA Systems Available from HP

X-Small Small Medium Medium+ Large XLScale-Out

Server ProLiant DL580G7

ProLiant DL580

G7

ProLiant DL580

G7

ProLiant DL980

G7

ProLiant

DL980 G7

Up to 16

ProLiant BL680

G7*

Processor 2 Intel x86-E7and EX

2 Intel x86-E7and EX




4 Intel x86-E7/blade

In-Memorydatabase

128G 256G 512G 512G 1TB 512G/blade

Max. 8TB total

Persistentstorage

2x300GB SAS

Ext 25x146G

SAS

2x300GB SAS

Ext 25x146G

SAS

2x300GB SAS

Ext 25x146G

SAS

2x300GB SAS

Ext 25x300G

SAS

2x300GB SAS

Ext 25x300G

SAS

HP X9300 IBRIX

gateway

HP P6550 EVA

Low-latencylog storage

1x320GB FIO 1x320GB FIO 2x320GB FIO 2x320GB FIO 4x320GB FIO Shared storage

used

Software SLES11SAP HANA

SLES11

SAP HANA

SLES11

SAP HANA

SLES11

SAP HANA

SLES11

SAP HANA

SLES11

SAP HANA

HP Servicesfor SAP HANA

HP FastStart

HP Technology

Support

HP FastStart

HP Technology

Support

HP FastStart

HP Technology

Support

HP FastStart

HP Technology

Support

HP FastStart

HP

Technology

Support

HP FastStart

HP Technology

Support

Scale-up

List Price(HW only)

$63 thousand $633 thousandto $2.4 million


38/43

37

Where to Find More Information

• http://help.sap.com/hana_appliance

SAP HANA Technical Operations Manual

Installation Guide, SAP BusinessObjects Data Services XI 4.0 Installation Guide, Trigger-Based Replication (SLT)

• http://service.sap.com/pam *

SAP BusinessObjects Data Services 4.0 Supported Platforms Quick Link: SBOP Data Services 4.0

• http://service.sap.com/notes *

Sizing HANA for non-BW sources (SAP Note 1514966) Sizing HANA for BW sources (SAP Note 1637145)



39/43

38

7 Key Points to Take Home

• Carefully examine your business requirements and identify a clear

objective that SAP HANA can help you achieve

• Give strong consideration to implementing one of the ready-madesolutions available from SAP

This will typically reduce the length of the implementation,

reduce costs, and very quickly show value to the business

• Carefully evaluate impacts to the existing systems – not just the

cost of the SAP HANA system itself – and try to select a solution

that is minimally disruptive as a starting point

• Consider your requirements for high availabili ty and disasterrecovery, in addition to sizing requirements for SAP HANA

As SAP’s vision for SAP HANA matures, you may find that it

becomes the central database in your landscape


40/43

39

7 Key Points to Take Home (cont.)

• Consider all of the options for getting data into the SAP HANA

system and select those that are least disruptive and offer the most

flexibility for the future For example, installing SLT on your SAP ERP system may seem

like an inexpensive approach, but it limits your abili ty to integrate

other systems into the SAP HANA landscape over time

• Do not be overly preoccupied with issues of scalability SAP HANA capacit ies will increase over time (HP already has

customers testing configurations larger than 16 nodes)

•

Leverage the resources of your hardware partner andimplementation partner to plan the SAP HANA implementation as

fully as possible — Down to the hostnames and IP addresses of the

new SAP HANA and related systems

Eliminate unexpected, costly surprises during the implementation


41/43

40

Your Turn!

How to contact us:

Doug Janes, [email protected]: WeeDoogieJ

Uddhav Gupta, [email protected]

Please remember to complete your session evaluation


42/43

41

Disclaimer

SAP, R/3, mySAP, mySAP.com, SAP NetWeaver ®, Duet®, PartnerEdge, and other SAP products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product

and service names mentioned are the trademarks of their respective companies. Wellesley Information Services is neither ownednor controlled by

SAP.

3 factors that impact hana cost

Documents