8/11/2019 In-Memory SAPHANA Update

http://slidepdf.com/reader/full/in-memory-saphana-update 1/4

 

In-Memory SAP HANA- Update 

Hi All,

Our group is going to reach 20,000 members sometime by next week or so. So firstly thanks to

each of you for making this possible. As we reach 20k (a major milestones) I thought of

reaching out and sharing what's happening in SAP HANA world.. Right now we are seeing

some major shifts in the Big-Data and HANA environment that most of you may be aware of.

IoT is very big and getting bigger. I am betting my next 5-10 years on HANA-for-IoT strategic

architecture.

1. My Prediction is that HANA Appliances will be replaced by TDI Open-ware solutions HW

http://lnkd.in/bsJA3BY. A sign of SAP HANA maturity and the first glimpse of DC ownership and

lower TCO's at the same or better quality. Better quality fo no single company manufacturers all

thins the best on the planet.

2. Internet of things (IoT) needs to become a HANA planning and business consideration

mandate; We are witnessing a major hurdle in IoT management as our initial HANA customersmature and want to now go out and dredge the ocean of social networks and devices for

absolute diamonds in the rough. Look for a paper due for publishing on the EDGE safeguarding

for HANA initiatives (under review with Scott from SAP right now- what I am terming as the

HANA4IoT future.

We have now reached a point of CONVERGRENCE of BIG-DATA (Hadoop), SAP HANA (In

Memory and Columnar); IoT (Seamless and secure device connectivity) and CLOUD. This is

the sweet spot where there are few folks with experience. I plan to become the global thought

leader in this area and any suggestions and comments highly appreciated. Thanks in advance..

3. Optimization is another area of specialization. It can reduce your BW-on-HANA TCO by over

40%. Last customer we reduced costs by 68%. This represents initial and annual costs.

So as we hit our 20K mark want to focus all HANA architects to start thinking

 A. Keep your eyes focused on Business Benefits and the Bottom Line for all things HANA.

Speed alone is not enough. (Tell me the benefit of accelerating a 715 second query to sub

second if business will never use it). re3member gartners statement in 2010 'Without business

in business intelligence, BI is dead"

B. HANA strategic architecture and Infra workshops with Big-Data, HANA, IoT and Cloud

considerations and alternatives.

C. Demand a reduction of at least 40% initial and annual TCO in BoH Migrations

D. HANA is a Strategic Business Solution and not another technical installation.

Let make sure we do our HANA 'Right the first time- every time'

Is TDI going to make HANA appliance obsolete?

8/11/2019 In-Memory SAPHANA Update

http://slidepdf.com/reader/full/in-memory-saphana-update 2/4

Up until recently your only option for moving to HANA was to buy a HANA appliance. However, we knowall too well that no single company does all things better than any other company. to solve thisdilemma SAP introduced the TDI (Tailored Datacenter Integration) model which allows companies tomix and match their leveraged vendors and datacenter skills, without compromising the overall qualityof the HANA solution. TDI is way ahead of its time and customers need to adapt to the future ratherthan hesitate. TDI allows customers to mix and match certified servers into existing enterprise storagesystems. This reduces time-to-value, risks, and costs for strategic HANA adoption, and conforms to yourdatacenter standards rather effortlessly. 

Note 1: At the current time we can clearly state that scale-out HANA systems are nottruly an appliance as they are not enclosed into a single environment butinterconnected in some way or the other. The same reasoning establishes that onlythe single node HANA Scale-Up actually qualifies as an appliance.Note 2: TDI is a concept ahead of its time. I predict that in another 3-5 years most of the HANAappliances will be replaced with generic TDI architecture devices with medium to large customers. Sostart thinking and planning for a cost mitigated HANA TDI architecture. Note 3: HANA-for-IOT (HANA4IoT) is also a concept ahead of its time. Most customers that adoptedHANA in 2010 are now being faced with IoT (Internet of Things) architecture and infrastructureconcerns. So plan your HANA4IoT along with TDI discussions 

I firmly believe that the TDI model truly establishes the confidence SAP has in their HANA platform byallowing open -are in a controlled manner as an approved HANA environment. It allows customers tomove from current HANA 'black-box' appliances towards a more IT determined open-ware environment.As we proceed on the path of TDI we see models where customers mix and match their HANAcomponents by leveraged partners and their world-class capabilities rather than buying a box IT is notallowed to touch. Typically customers choose their HANA PRD environments on bare metal and non-PRDon virtual servers. However, a new kid on the block called ‘Docker’ is promising to even make virtualservers kind of obsolete. Docker with their disruptive technology is leapfrogging to provide the nextgeneration of possibilities. Watch this one closely.

SAP HANA, though quite mature, is still a new kid on the block with exceptional business value andbusiness benefit potentials. In its first step it came with very tight controls in the form of a lock-downappliance. As SAP HANA stabilizes we are seeing an adoption towards open-ware and TDI is that future

option available today. One of the indications of maturity is SAP allowing TDI HANA systems thattake customers from a single vendor monopolistic chokehold to a more open platform design. AsSAP HANA continues to mature the market is clearly moving from HANA appliances to HANA TDI systemsthat leverage customer strengths and get out of the ‘Black-Box’ appliance model. We will start to seethe best practices of HANA installation shift from a single vendor appliance model to a ‘mix-&-match'TDI one. 

Historically the SAP Go-T0-Market decision- to start with an appliance model has solid reasons. BWAwas an appliance and SAP HANA was a disruptive extension that took the same appliance route.However, as HANA matures and becomes more main stream SAP is already allowing customers to optfor a more open platform. Customers can today chose an IBM or Cisco compute (HANA servers), and mixthat with an EMC or NetApp storage. TDI is the first step to open platform of a maturing SAP HANA. It isalso the first step to increasing ROI and decreasing TCO in HANA implementations. 

Some facts about HANA (+ and -) 

1. 

The standard recommendation is scale-out for BI and scale-up for ERP.2.  (+) HANA comes on a shared cluster architecture allowing administrators to split tables (or partitions of

columnar tables) across multiple nodes in a cluster. This is very different from an Oracle cluster but that isanother discussion 

8/11/2019 In-Memory SAPHANA Update

http://slidepdf.com/reader/full/in-memory-saphana-update 3/4

3.  (+) HANA can run on both RDBMS and Columnar simultaneously allowing operations and analytics to runoff the same database. This leads to large-scale Real-Time operational decision enhancement. 

4.  (+) HANA is currently on SP 8 and so far we can store row tables on a single master node of the cluster.SP 8 now supports multi tenancy and a host of new functionalities.  

5.  (-) today it is only possible to store row tables on a single master node of the cluster  6.

 

(-) All connections to the HANA system are controlled by a single ‘Master nameserver’ making this apotential bottleneck for very large scale-out deployments (>10 servers) 

7.  (-) Single commits from different HANA nodes, i.e. joins of data across different HANA nodes, andtranslates into performance costs due to distribution of tables across the various servers. 

8.  (-) Business continuity of SAP HANA in a scale-out of clusters will always be more complex thanoperating out of a single node system 

9.  (-) TREX is an essential part of HANA that SAP continues to leverage from their existing portfolio. TREXleverages the ‘shared filesystem’ to store all the data when in a multi host scale-out mode. TREXpredates BWA and MAXDB. It was built on a NFS access to persistency.  

10.  HANA, over time has evolved from being an analytic engine to become the SAP platform. Its historicalevolutionary path still clings to some legacy considerations as we move forward beyond it being ‘just’ ananalytic engine.

11.  SAP continues to make rapid developments and over time most of the current issues will becomeobsolete. HANA Scale out is still on a maturity path. HANA is evolving extremely rapidly and mostappliance partners clearly state that all HANA scale-out appliances need to be on the same version

control. So though 12-18 months today seems to be an eternity it will come very rapidly in real life.12.  HANA appliances are evolving very rapidly with newer versions coming out every 6 months or so. So if

you bought a HANA appliance 6 months ago then you have the following options today. [1] Continue withthe current appliance that your appliance partner may stop supporting shortly, or [2] Totallyreinstall/change all the procured appliances and change to the new appliances and new supportcontracts. Imaging doing this every 18-20 months. If you think this sounds far-fetched ask your appliancevendor as to 'till when will they continue to support BWA appliances" and therein you have your answerabout proceeding on the appliance or TDI models  

Evolution of SAP HANA 

 

Started as an analytics database 

  Evolved as the preferred database for SAP BW    Becoming the preferred platform for operational Suite on HANA (ERP, CRm and SCM) 

  Stage 1:  – Platform safeguarding- HANA Appliances only 

 

Stage 2: - Platform maturity and open-ware = TDI HANA model 

a.  TDI releases IT from the choke-hold of a single appliance vendor by allowing mix-and-match byestablished leveraged customer vendors. Currently this is limited to certified partners.  

b.  There is already a large enough SAP HANA customer base that is selecting the HANA TDI options. Whichallows customers to choose their preferred, server/ storage/ networking/ IoT vendors independently. 

c.  Critical Note: when thinking TDI also consider your strategic IoT data acquisition in the partner mix. 

Strategically TDI is the first sign that SAP HANA is maturing and opening to meet the terms of thecustomers focused solutions based on an open market adoption. There is clear evidence that HANA

adoption will continue to grow. So while some customers choose the appliance route to HANA we see aclear long-term adoption to best-in-class, multi-vendor solutions.

As more and more customers adapt to HANA we are also seeing many of them take the TDI route toHANA. This allows more and more customers manage to extricate themselves from the choke-hold ofthe ‘black-box’ approach of HANA appliances. In the 2014-16 timeframe we predict that SAP HANA willbecome just another SAP application in your datacenter freeing customers from the chokehold of HANAappliances. One that can be deployed on approved infrastructure of the TDI model. 

8/11/2019 In-Memory SAPHANA Update

http://slidepdf.com/reader/full/in-memory-saphana-update 4/4

What we are providing to customers today: 

Customer 1 is a large financial institution that loves their HW partner but does not like their supportexperience. So they have chosen the TDI route with neutral support capabilities, they are choosingtheir own preferred vendors for server and storage and allowing us to integrate the two componentsalong with a SAP TDI certification. This directly impacts their initial costs, support costs and strategiccosts without compromising quality of support. 

Customer 2 is a large data-center where ROI and TCO are critical considerations. They plan to runhundreds of HANA customer as hosted or on the HANA cloud model. They already have strategicalliances with Compute/server, storage and network partners and clearly see the benefits of not goingon the ‘Black-Box’ monopoly chokehold of the appliance model. TDI is every customer’s answer tobreak free from current monopolistic control appliance model to a more open infrastructure model.Open architecture allows customers to leverage market competitive forces. Appliances, on the other-hand, locks customer into monopolistic command and control scenarios.

TDI is as close to how you run your net weaver platform today, where the customer chooses theirpartners  procures the components and installs their SAP applications for SAP HANA. 

Takeaway: 

1. There is no single vendor that does all thing best on the planet. Server, Storage, network devices,communications, IoT and IoE security fabric, certified HANA backup, etc. 2. TDI allows customers to get out of the choke-grasp of a single vendor monopoly and launches themon a path of open-ware selections based on world class providers.3. Appliances are surely on their way out and TDI is on the way in- so plan your HANA Infra with thefuture in mind. 

4. VM servers could be on the way out with the Docker disruptive technology options as it promises toboth enhances the quality and capabilities and lowers TCO.  

If unclear then reach out for your TDI solution and launch your HANA Infrastructure with world classend-to-end leveraged partners and not get into a choke-hold grasp of an appliance and what itrepresents.