The truth about hana. CTAC road to hana
•Download as PPTX, PDF•
1 like•902 views
Presentation of the Puur C seminar about Hana, organized by CTAC on 24/06/14
Recommended
Recommended
More Related Content
What's hot
What's hot (15)
Similar to The truth about hana. CTAC road to hana
Similar to The truth about hana. CTAC road to hana (20)
More from Ctac Belgium
More from Ctac Belgium (14)
Recently uploaded
Recently uploaded (20)
The truth about hana. CTAC road to hana
- 1. The Truth about HANA What’s really in it for your business
- 2. 2 Keynote The new SAP User Experience Paradigm enabled by HANA Effective Data Analysis using HANA Live HANA Optimized Processes for Finance and Retail The Road(s) to HANA Tom Cenens SAP HANA Expert, Ctac Belgium SAP Mentor
- 3. you don’t have to archive data
- 4. Ceci n’est pas une base de donneés 4 Information composer & modeling studio Application services (HTML5) Text Search Planning & Calculation Engine Predictive Analysis & Business Functions R & Hadoop integration Real-time replication services In-memory database Data Services Real-time analytics Real-time apps SAP Business Suite Third-party systems Netweaver Business Client SAP Business Objects solutions Microsoft Excel Others … (Open)
- 6. Openness 6 Data center & operations Virtualization support (VMWare) Single production VM GA Multi-VM via pilot program Ivy Bridge server Scale up to 120 cores & 12TB DRAM
- 7. SAP HANA Answers 7 SAP HANA ACADEMY SCN (HANA) COMMUNITIES SAP HELP SAPHANA.COM SAP HANA ANSWERS IN-MEMORY KNOWLEDGEBASE AND SEARCH powered by SAP HANA CLOUD PLATFORM WEB BROWSER HANA STUDIO ANSWERS PLUGIN video, help files discussions, notifications content
- 8. SAP HANA Answers 8 Toolbar Menu Click blue Answers icon to find content or ask a question. Alternatively, press the F10 key Contextual Awareness Highlighted text as well as your current context determine the recommended content HANA Answers view Your source of valuable content and your connection to the HANA network of experts Notification Indicator Someone has answered your question or posted something of interest to you
- 9. The Path Forward 9 VALUE DISCOVERY BUSINESS CASE WORKSHOPS DESIGN THINKING BUSINESS EXPLORATION TECHNICAL SCAN SIZING DEPLOYMENT OPTIONS TECHNICAL EXPLORATION INFRASTRUCTURE SYSTEM COPY OPTIMIZED PROCESSES MIGRATION USER EXPERIENCE ANALYTICS PROOF OF CONCEPT
- 10. SAP Helps you 10
- 11. SAP HANA TCO 11 35 30 25 20 15 10 5 TCO3years million$ TCO without SAP HANA TCO with SAP HANA SAP BW SAP BW SAP ERP SAP ERP CUSTOM APP CUSTOM APP TCO SAVINGS ACROSS MODELED SCENARIOS 37 % TOTAL COST WITH SAP HANA 19.663.124 $ TOTAL COST WITHOUT SAP HANA 31.324.017 $ NET COST SAVINGS WITH SAP HANA 11.660.893 $ * independent survey of Forrester with 30 customers
- 12. Data Ageing 12 2013 2014 RECENT APPLICATION LOGO’S HOT DATA 2010 2011 OLD APPLICATION LOGO’S COLD DATA SAP HANA 2012
- 13. Reduced Footprint Collapsed Landscape Smaller Data Footprint Simplified Data Processing Simpler Set-up Simpler administration and Operation Simpler application development 13 SPACIAL TEXT PREDICTIVE DB PLANNING DB ANALYTICS DB TRANSACTIONAL DB SAP HANA
- 15. Migration to SAP HANA 15 SAP Business Suite RDBMS SAP Business Suite SAP HANA 1 update 2 DB migration
- 16. The Path Forward 16 VALUE DISCOVERY BUSINESS CASE WORKSHOPS DESIGN THINKING BUSINESS EXPLORATION TECHNICAL SCAN SIZING DEPLOYMENT OPTIONS TECHNICAL EXPLORATION INFRASTRUCTURE SYSTEM COPY OPTIMIZED PROCESSES MIGRATION USER EXPERIENCE ANALYTICS PROOF OF CONCEPT 1 day per module 3 days 1 day per module 1 day 1 day 1 day cloud infrastructure as of 15k / 3 months 5 days 5 days 5 days 3 days 3 days * estimations based on ERP 6 Enhancement Pack 7 and POC scoping 1 day
- 17. Ctac HANA experience Certified HANA partner Fit4Retail on HANA Migration to BW on HANA Support for BW on HANA 17
- 18. SAP HANA Ecosystem 18 SUITE ON HANA CLOUD SOFTWARE HCP HANA CLOUD PLATFORM ariba success factors cloud 4 customer CROSS-APPLICATION CONNECTIVITY THROUGH HANA CLOUD PLATFORM
Editor's Notes
- What if a database had no latency? That also means it’s about answering questions so you don’t have to wonder “What if”. Before we continue, let me ensure there is no room left for interpretation on some of these what if questions. In 2006, Hasso’s students at the Hasso Plattner Institute were bored of hearing about SAP Business ByDesign in the lectures that Hasso did. They wanted to hear about what Google was doing for example. Hasso then said, let’s do something different and he put the idea forward to create a new database. What if a database had no latency? The trend was there back then already that processing power, memory & disk was growing fast so they could anticipate how far hardware would advance over time. They started project “Sans Soucci DB” and as such he set out with a number of colleagues and undergraduate students to create this new database. The database was presented to SAP and accepted in 2009. Later on SAP named the product HANA after Vishal Sikka went on vacation to the island HANA near Hawaii and called up Hasso on the way home with the idea for the name. We all know latency still exists but it is now so little that we now have real-time applications that can provide real-time information. What if Hasso has a good pharmasist? A couple of year ago, an analyst asked Larry Ellison, Oracle’s CEO what he thinks about SAP HANA and back then he answered it’s a wacko idea and he said “get me Hasso’s pharmasist”. Up till today, I have yet to be convinced that the pharmasist creates bad subscriptions, in fact, I believe he’s got some great stuff in stock. I want to buy some.
- SAP HANA is more than a database, just witnessed this first hand today. We’ve demonstrated multiple key functions & features today, real-time applications with real-time analytics, search & predictive capabilities and of course Suite on HANA, dipped into a HTML5 based user experience.
- Leveraging the availability of SAP HANA Maintenance Revisions, customers can opt to either keep an older SAP HANA Support Package Stack (SPS) running for around three months after the release of a new SPS, or to directly adopt the new SPS upon release, depending on their individual and unique needs for when to adopt new features and capabilities of SAP HANA. Customers can further plan their SAP maintenance stack in accordance with clearly defined SAP HANA Datacenter Service Points at the end of March and at the end of September; based on a Revision which has become much more mature, as it has been available for over three months and has also been running in production enterprise systems at SAP. Only provides fixes for major bugs concerning critical functionality in key SAP HANA scenarios (Business Suite on SAP HANA, BW on SAP HANA, SAP HANA Data Marts) • Only provides fixes for production systems, or endangered go lives within the next 3 weeks • Only provides fixes for bugs with non existing workaround • Only provides fixes with minor code dependencies and code changes or impact
- SAP has been working hard on making the SAP HANA platform an open platform. In the technology front, just recently productive General Available of VMWare was announced. For multi-VM there is a pilot program ongoing currently as well. With the new Ivy Bridge based servers, servers can scale up to 120 cores & 12 TB DRAM which can serve the largest databases in the world. HP featured the “kraken” at SAPPHIRENOW. I’ve also seen what EMC has in store for the near future EMC bought DSSD and just recently introduced PCIe Flash Appliance aimed at in-memory databases and big data. It’s so fast that it can be used for super fast SAP HANA failover
- Benefits to Customers / Partners Improved Experience and Productivity Find solutions faster Showcase your knowledge Discussions Notifications Answers returned based on your context Stay in the flow (in Studio) Access all HANA technical information from one place
- 70% on software 15% on hardware 20% on administration and development labor Our interviews with four existing customers, survey of 25 additional customers, and subsequent financial analysis found that a composite organization based on these interviewed organizations could expect to experience the risk-adjusted costs and costs savings shown in Figures 2 and 3 when utilizing HANA for this purpose. (See Appendix A for a description of the composite organization.) As demonstrated by the total cost savings with HANA, there were significant reductions in the hardware, software, and labor required for each application. Savings. Based on the composite total cost model, the sample organization experienced the following risk-adjusted benefits (that represent those experienced and projected by the interviewed companies): • Reduced hardware cost (simpler data footprint/simpler landscape/simpler setup). Moving to the HANA platform allows customers to reduce the volume of servers and storage required, due to the data compression, as well as efficiencies gained due to HANA’s functionality. • Lower software costs (simpler data footprint/simpler landscape/simpler setup). HANA also allows for a reduction and elimination in many of the software products such as ETL, data replication, management, and other middleware software. Additionally, the HANA platform includes advanced analytics capabilities such as text, ge, and predictive analytics as part of its platform offering without additional license. • Faster development time (simpler application development/simpler user experience). All of the interviewees cited a faster, more efficient application development process through automation and minimizing complexity, which allowed for a reduction in resource time. • Increased productivity for administrators (simpler processing and operations). Due to the simplification of the environment with HANA, customers are able to reduce the amount of administration time required to tune, optimize, and manage databases and servers. › Costs. The sample organization experienced the following risk-adjusted costs: • HANA appliance cost. In this model, we have included the HANA appliance as the hardware for the deployment. However, we note that SAP also offers the SAP HANA tailored data center integration delivery approach, allowing customers to utilize enterprise hardware and potentially offering additional cost savings. • Software licensing costs. This includes the software cost associated with HANA, as well as the costs of the application software. We include initial costs as well as ongoing maintenance. • Development cost. This cost category includes the resource cost for development for the applications moved to HANA. • Administration cost. This cost category includes the resource cost for administration for the applications moved to HANA.
- Almost a year ago, there was a big discussion going on if we still need archiving or not. As archiving was there, it’s still there and it’s available but now, SAP has created a new option which can be more interesting: Data Aging. When we look at which data is requested from a system, we can distinct between hot data and cold data. Hot data is data that is often requested, cold data, is data that is seldomly requested. This principal can be used to keep cold data on disk and only temporarily load it into memory when that data is requested. As you can see on the slide, one could do that based on the year the data was created and once data is considered cold, it could then be stored elsewhere. This can remove the need for archiving because archiving mostly takes place when performance of the system is impacted due to large datasets. When you would request recent data in the above example, SAP HANA would give the result back, very fast. If you request cold data, it would take a little bit longer because SAP HANA would fetch the data from disk and then put it in-memory. In the end, it’s interesting functionality from a cost perspective as well since you can then reduce the size of the memory that is needed to run your in-memory database. SAP is working on this data aging concept and has already released the first integrated functionality in business suite with the release of simple finance for ERP. You can expect that this concept will be worked out to a larger extent in the future. Data which does not need to come back at the speed of light can resort elsewhere to reduce the memory footprint needed for the database. An example can be technical logs. Those are not mission critical and are not constantly requested so it does no harm that they reside in the Sybase ASE database at that moment in time.
- When we look at sizing & footprint of SAP HANA, we see that SAP HANA still needs disks. Otherwise you could loose your data if there is a power failure since DRAM is emptied upon power down. In general, when you take a traditional SAP environment and translate it into an environment powered by SAP HANA, the footprint drops because you have compression on HANA but also because you don’t keep your data multiple times. You won’t copy over data because you don’t have to. large data compression ratio with HANA, ranging from 4 to 10 times. One interviewee stated, “Our data growth on BW has been 34% per year, but we’ve cut down to 12% with HANA.” Additionally, data compression is only one of many factors that leads to overall data footprint reduction. Forrester’s interviews with customers and app development teams have revealed these additional major factors: a simpler data model, the elimination of aggregates/indices, the elimination of redundant copies of data in ERP and BW, and columnar/dictionary-ba <als bullet points zetten>
- HANA can be deployed in multiple ways