What you need to know before migrating to SAP Hana

  • View

  • Download

Embed Size (px)


SAP HANA is superfast in memeory database and plaform enabling new possibilities in terms of analytical reporting and realtime data acquisition and consumption. However, the business case is often hard to prove due to high licence costs. Based on our experience with SAP HANA migrations we have collected the most important points for Data Management in SAP BW and system optimisation before moving all data to SAP HANA. Just in few steps you can enhance the benefits of SAP HANA. This presentation will explain you how to analyse your BW, why to implement near line storage what data to housekeep and how code optimisation will help you.

Text of What you need to know before migrating to SAP Hana

  • 1. Thumbs up or thumbs down?! What you need to know before migrating to SAP HANA. Gregor Stoeckler, DataVard

2. 2014 DataVard GmbH # 2 Value vs. Cost vs.How much VALUE do your data generate? How much COST do your data generate? 3. 2014 DataVard GmbH # 3 UserhappinessTCO&dataaccessTCO Lean Data Management with OutBoard Performance optimization, Tuning In-memory Ensure SLAs are met GOALS TACTICS Set up central policies Use appropriate storage: Archiving, NLS, Smart data access Set up central policies Perform housekeeping Automation Information at your fingertips Speed and high availability is key Keep & store Reduce cost Purge, delete & housekeeping Hot Data Business critical data Data required for reporting and planning Cold Data / Old Data Aged data, history Infrequent, rare use Need to keep (external/ legal, internal requirements) Dead Data Technical data (e.g. logs, protocols, PSA) Redundant data 4. 2014 DataVard GmbH # 4 5% 15% 15% 9% 11% 32% 5% 5% 3% Master data Temporary data Other data PSA data Changelog data ODS data Cube E data Cube F data Cube D data Typical data distribution in SAP BW* Comments: 13-17% of system size is reporting data Temporary data is subject to housekeeping (BALDAT, RS*DONE, ...) HANA sizing report gives a 1st indication (OSS note 1736976) Only 12% of all data in BW is actually used. Forrester research* Source: DataVard BW Fitness Test 5. 2014 DataVard GmbH # 5 A customer example - Randstad CAUSE Problem System size is growing steadily (35%+) Some reports are used infrequently Several reporting solutions only used temporarily EFFECT Situation No classification of data into important/unimportant Data growth due to high granularity of data Long ETL runtimes regardsless of several optimizations 6. 2014 DataVard GmbH # 6 A customer example (Randstad) with HeatMap Cost-/Value-Analysis Cost of storing data (incl. RAID and Backup) Measure # of access Other important KPIs: #User, # of loads, duration of loads, etc. 7. 2014 DataVard GmbH # 7 BW Fitness Test Sample Check Here The BW Fitness Test prepared us excellently to make our SAP BW fit for the future. We now manage our aged data with Nearline Storage and improved our Load Performance. Steffen Muesel, Randstad 8. 2014 DataVard GmbH # 8 Key take aways Paving the Road to HANA System analysis - Know where you are Using our Gartner-awarded BW Fitness Test will analyse and benchmark your system against more than 150 others. Remember: only 13-17% of your system are in active use. Build a plan - your very personal Road to HANA Based on the assessment we present to you improvement potential and short term benefits, including a review of your HANA sizing, housekeeping and archiving potential. Data Model and ETL changes Start adopting Data Models, Lookups and Transformations that could be optimized for the use under HANA. Code optimization: optimize customer code and replace non-compatible code. Clean up & optimize your system already now Archive/NLS: to move inactive data into a highly compressed store. Housekeeping: clean up of dead / temporary data. 9. 2014 DataVard GmbH # 9 DataVard presents DataVard SAP Data Management since 1998 Customers range from SMEs (60 users) to Fortune 500 (e.g. Allianz, BASF, KPMG, Roche, Nestle) Development partner of SAP Landscape Transformation Suite (LT) and Information Lifecycle Management (ILM) 7 locations in Germany (HQ), Italy, Slovakia, United Kingdom and the US 10. www.datavard.com 11. 2014 DataVard GmbH # 13 Copyright DataVard GmbH. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of DataVard GmbH. The information contained herein may be changed without prior notice. DataVard and OutBoard are trademarks or registered trademarks of DataVard GmbH and its affiliated companies. SAP, R/3, SAP NetWeaver, SAP BusinessObjects, SAP MaxDB, SAP HANA 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 other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are provided by DataVard GmbH and its affiliated companies (DataVard") for informational purposes only, without representation or warranty of any kind, and DataVard shall not be liable for errors or omissions with respect to the materials. The only warranties for DataVard products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. Copyright