This action might not be possible to undo. Are you sure you want to continue?
BW on SAP HANA
Understanding HANA technology, what it means to your business, and what to expect during data migration
The SAP Business Warehouse (BW) is a core part of the SAP NetWeaver technology. Serving as a powerful Enterprise Data Warehouse application platform BW provides flexible reporting and analysis tools. Businesses are able to make well-founded decisions on the basis of this analysis. Business information from SAP and external data sources are integrated, and consolidated in BW on HANA. SAP HANA (HANA) is a new database and analytics engine. Data now resides in main-memory (RAM) and no longer on a hard disk. Complex calculations on data are not carried out in the application layer, but are moved to the database. By running BW on HANA your business will experience significant gains in speed for retrieving analytical queries and reports. In this section, we introduce core concepts of SAP HANA in-memory computing, and how these concepts can help your SAP NetWeaver 7.3 Business Warehouse run better. We also consider some of the technical implications of upgrading your current data warehouse to version 7.3, and of migrating it to the SAP HANA database. Lastly, we cover what you might expect during the process of transitioning to this new technology.
Row vs. Column Data Storage
Relational databases typically use row-based data storage. However, column-based storage may be more suitable for some business applications. As shown in the figure below, a database table is conceptually a two-dimensional structure composed of cells arranged in rows and columns. Because computer memory is structured linearly, there are two options for the sequences of cell values stored in contiguous memory locations:
Row Storage - The data sequence consists of the data fields in one table row. Column Storage - The data sequence consists of the entries in one table column.
Traditional databases store data simply in rows. The HANA in-memory database stores data in both rows and columns. It is this combination of both storage approaches that produces the speed, flexibility and performance of the HANA database. OLAP queries on huge amounts of data take a lot of time because every single row is touched to collect the data for the query response. In columnar tables, this information is stored physically next to each other, significantly increasing the speed of certain data queries. Data is also compressed, enabling shorter loading times. The following example shows the different usage of column and row storage, and positions them relative to row and column queries. Column storage is most useful for OLAP queries because these queries get just a few attributes from every data entry. But for traditional OLTP queries, it is more advantageous to store all attributes side-by-side in row tables. HANA combines the benefits of both row- and column-storage tables.
The elements of in-memory computing are not new. 3 .In-memory Technology In-memory technology moves data and information sources from remote databases into local memory so the results of analyses and transactions are available immediately. However. dramatically improved hardware economics and software technology innovations have made it possible to realize The Realtime Enterprise with in-memory business applications.
.e. the database needs to be queried in parallel. Query processing also involves data processing.i. HANA's real-time platform combines high-volume transactions with analytics to help create solutions that take your business performance to the next level. on the degree of system parallelism. The HANA database is optimized to use the capabilities of multi-core processors in order to enable incredibly fast queries. The result: Instant answers to your complex queries. HANA distributes the workload across multiple cores of a single system. The SAP HANA Appliance is a combination of in-memory software and SAP-partner hardware that allows you to query multiple types of sources at speeds and in volumes as never before.The cost of main memory has decreased significantly. The HANA in-memory database can help your applications zero-in on the information you need— without wasting time sifting through irrelevant data. Multi-core Processors Processor speed is no longer dependent on clock speed but rather. It is now cost effective to store all data of a large enterprise in main memory. 4 . With optimized loading routines. and better decision making across your enterprise. Processing multiple queries at the same time is handled by multi-threaded applications which map each query to a single core. Parallelism can be achieved on different levels from the application level to query execution on the database level. Modern server boards have many CPUs with several cores each. The SAP HANA Appliance can fail over to a cold standby server to guarantee high availability. system data can be restored quickly in case of power failures. All data are kept in main memory and can be processed at an incredible speed.
SAP HANA Modeler SAP HANA Modeler is a graphical data modeling tool used to design analytical models and. Tools: HANA Studio and Modeler The two most important tools that come with BW on SAP HANA are the HANA Studio. analytical privileges that govern access to those models. Studio is used for data modeling and provisioning. HANA uses multi-core systems on different layers to achieve highly-parallelized query execution. SAP HANA Modeler supports: • • • • • • ERP table metadata upload: Mass ERP table metadata upload using the Load Controller API Selective ERP table metadata import using Data Services integration Extractor metadata upload: Extractor table metadata upload using the Load Controller API Selective Extractor table metadata import using Data Services integration 5 . the system management application. later. and the HANA Modeler. SAP HANA Studio SAP HANA Studio is pre-installed on the SAP HANA Appliance. the data migration and optimization application.Using column-based tables enables easier data partitioning. and parallel processing wherever allowed.
more timely business decisions Lower Total Cost of Ownership (TCO) Tight integration with other parts of your SAP landscape Simplified configuration and operation Improved BW performance Answering many important business questions immediately Significantly faster analytics and reporting Access to the most current and complete business information Realtime access to transactional data Development of deeper insights into your business Elimination of data aggregation Cost effective management of large volumes of data New possibilities applying groundbreaking in-memory hardware innovations to your business needs BUSINESS VALUE: 6 .Business Value BW on HANA enables • • • • • • • • • • • • • Faster information for better.
HANA helps your SAP NetWeaver 7. eliminating redundant storage.Faster decision-making Having the right information when you need it Increasingly sophisticated business decision models depend on fast access to and manipulation of massive data stores. Modeling. and to predict Available to Promise (ATP) more accurately. Lower Total Cost of Ownership (TCO) Reducing costs through simplification In-memory computing with HANA becomes the primary persistence model for the enterprise business warehouse and will enable significant rationalization of existing BW landscapes resulting in lower overall TCO. Simplification of Models. System administration is simplified through one set of tools. HANA enables you to analyze large amounts of data. Insight into business operations demands data volumes and velocity that are beyond the capabilities of traditional disk-based systems. As an example. in near real time. in many cases. and the need to unload and reload data when remodeling these objects. layers in your Enterprise Data Warehouse can be eliminated because the speed of loading and querying makes some objects unnecessary. from virtually any source. having the most current order and logistics information makes it possible to manage your inventory more efficiently. and the enhanced performance for both loading and querying make it possible to 7 .3 Business Warehouse run better than ever. making it possible to access reports with up-to-the-minute information. This simplification of remodeling makes it possible to respond quicker and with less disruption when new requirements are identified by the business. and Re-Modeling BW on HANA allows for simplification of existing models since. Reduced Data Redundancy The physical models implemented by BW on HANA for InfoCubes and DSOs eliminate redundancy within a model. The structure of the physical models that are implemented for in-memory optimized InfoCubes and Datastore Objects (DSOs) has also been simplified.
Bex. gauges. There is still the same BW application process but. web-based interface with offline capabilities • Start from a blank slate or use an existing analysis or report • Multi-source access • Interactivity with filtering. 8 . System operation stays as it is. skins. Simplified configuration and operational management Non-disruptive innovation and advanced administrative tools Your current business processes inside BW can stay as they are and will mesh perfectly with HANA. and selectors. calculations. and process chains do not need to be remodeled. and maintain your data warehouse.eliminate entire models in many cases. Dashboards can then be customized with pre-built components. sorting. and more • Data lineage Lightens the IT workload • Self-service analysis and reporting • Controlled and secure access with tight BI platform integration Intuitive. The result is that the same amount of data for BW on HANA requires significantly less storage. yet easy-to-use business intelligence • Intuitive. Simplified Operations and Monitoring With the integration of basic HANA administration capabilities with the BW Admin Cockpit it is possible to perform and monitor most common database and data warehouse functions from one place. Expert users do not need to get retrained because they can continue to use their current BI or other frontend tools. This reduces the number of tools that have to be installed. and can drill-down into data details. With HANA there is no need to retrain end users familiar with BW. Tight product integration Increased flexibility because client tools provide more options • Tighter integration with SAP BusinessObjects Data Services • Enhanced integration with SAP BusinessObjects Metadata Management • Rapid prototyping of Ad-Hoc-Scenarios via BW Workspaces Webi. updates and reports much faster than before. it is now possible to run queries. with BW on SAP HANA. business-centric view of information with universes With Excelsius Dashboards business users can conduct “what-if” analyses with sliders and other controls. operate. learned. Xcelsius empower business users with powerful. ranking. and reduces the skill set and training required to create. maps. charts. and maintained.
A more complex option: Upgrade an existing BW system to version 7. SAP strongly recommends you follow a parallel approach to data migration: keeping your production landscape in place while bringing up the BW on SAP HANA system. Because of its design it allows transactional and OLAP reporting in a single system. The easiest option: Create a totally new BW instance. with the assurance that the existing production landscape is still available as a fallback.In addition. which makes it simpler. and can be integrated with NetWeaver Identity Management to ensure security remains intact. This third option is important for companies who already have an active BW system which must function continously and without interruption. SAP also strongly recommends you consider the high availability and backup/recovery procedures of HANA before starting to use it in production systems. 9 . 1. 3.1 What is SAP HANA? SAP HANA is a general purpose and ANSI standards-compliant in-memory database.3 SPS5. than traditional RDBMS systems like Oracle. HANA supports the BW Analysis Authorization Concept. and much faster. 2. then change the underlying database from a traditional disk-based relational database to the new in-memory HANA system. while creating a new BW instance running on the HANA database. and connect it to the SAP HANA database. A parallel approach mitigates risk while simultaneously enabling you to familiarize yourself with the administration and capabilities of HANA. All three achieve the same result: copying your BW data into an SAP HANA database. 1. The most popular option: Keep the current BW system running on a traditional database. If this is the case for your company. You can implement SAP NetWeaver BW scenario by scenario. Migration Options Various approaches to system implementation Three options exist for implementing BW on SAP HANA.
This is what SAP call innovation without disruption and it seems to work really nicely.2. You build the logic and structures yourself. to visualise or analyse data. SP03 which provided support for BW and SP04 which provides support for Text Analytics and High Availability. and there is some discounting based on volume. Security. XLS. And this update takes about 10 minutes and can be done online in High Availability environments. Multi-language and technical. and the smallest appliance is 128GB.there is no release of SP04.1. demo. There are volume discounts so as you buy HANA. It is one simple price based on appliance size.0. it's best to contact your account exec directly and talk to them. SAP BusinessObjects. and use a tool e. SAP HANA SP02 (Revision 12) is the general-availability release of SAP HANA to the market. And for example. The minimum purchase amount is currently 64GB. High Availability ETL-based Data Acquisition by SAP HANA Direct Extractor Connection 10 . But the patches are just to let people know about the new features . Revision 28 is SP04. 1. you can easily incrementally expand up to 256GB. the price decreases. 1. an In Memory DataBase (IMDB) an Analytics Engine and some tooling for getting data in and out of HANA. SP02 which was the generally available version. But what SAP have done is really interesting: they have removed the versions and provide innovations automatically when you update HANA.5 and 2.2 Is SAP HANA an appliance? SAP HANA comes shipped as a pre-configured appliance from your hardware vendor and the license is bought from SAP. As usual with SAP licenses.4 Why is SAP HANA versionless and what is innovation without disruption? SAP HANA was originally going to be numbered 1.3 How is SAP HANA licensed? With SAP HANA. Usability.0 and you will see this in some early literature. 1.SP01 which was the ramp-up. But the reality is that SAP HANA only comes released in Revisions. you pay based on the size of productive usage.saying that it can cost as little as €13k per 64GB unit. All test.5 What are the key benefits of SAP HANA Patches? SAP HANA SP01 (Revision 10) is the initial release of SAP HANA to ramp-up. So when last week. we got the innovations from SP04 included. 1. HA and DR licenses are included in this price and there are no hidden extras like CPU or user licenses. SAP HANA has patches . SAP HANA SP03 (Revision 20) brought: • • Support for the SAP NetWeaver BW database Information Composer SAP HANA SP04 (Revision 28) brought: • • • • Loading Data from Flat Files (CSV. Note that Steve Lucas from SAP has given some HANA prices for BW to the market -What Oracle won't tell you about SAP HANA . SAP HANA is an analytics appliance that consists of certified hardware. This means if you buy 64GB today. For the purposes of information and marketing. 1.g. which is upgradeable to 256GB. I had all our SAP HANA systems updated to SAP HANA Revision 28. XLSX) including automatic table creation in HANA Studio Enhancements for Attribute/Calculation Views. SAP HANA is priced by the 64GB unit right now.
In addition. they are likely to be massively faster.• • Predictive Analytics Library (PAL) R Programming Language Integration 1. In addition. The biggest examples of where I have seen SAP HANA not able to provide a benefit is where it is compared featurefunction as a replacement to an existing transactional system. The really great SAP HANA apps that have been created mix three big performance improvements. Inmemory technology is typically 100-1000x faster than disk for this reason.000x club".8 What is SAP HANA great at? The best thing that HANA brings to the table is the ability to aggregate large data volumes in near real-time . So. the performance of in-memory analytics. second.9 Where might SAP HANA not provide a benefit? SAP HANA improves the biggest bottleneck that exists in standard database platforms .The SAP BW on HANA FAQ 1. SAP wanted to prove the reliability of SAP HANA and its ability to support business critical applications. In fact. SAP ERP on HANA is expected to be released into ramp-up in Q4 2012. to optimise ERP on HANA it is necessary to push the logic down into the database and make use of the SAP HANA stored procedure language SQLScript.7 What is SAP ERP on HANA? SAP planned from the start to allow customers to run their ERP or Business Suite on SAP HANA.3. 1. ERP basely makes use of database stored procedures. I have broken this out into a separate article . This work is in progress.6 What is SAP NetWeaver BW on HANA? SAP now supports SAP HANA as the underlying database for its first Business Suite product. and what's more because of the high analytical performance of SAP HANA. it runs its own ERP system. SCM and PLM will follow. but not 100 or 1000 times faster. However. ERP on HANA does not provide the same level of benefits that BW on HANA does. affectionately called "NSP" by employees. 1. However. SAP has built a set of Analytics Apps on top of HANA and this are set to be great point use cases to get customers up and running quickly. on HANA in parallel. From a technology perspective.and to have the data updated in near real-time. This is because ERP is predominately transactional (OLTP) and SAP HANA does not optimise large transactional volumes to the extent that it does the OLAP functions of SAP BW. the NetWeaver BW Data Warehouse. The improvements in performance and flexibility it allows resolve many of the classic data warehouse problems that have plagued the market for 20 years. SAP ERP is not optimised for any particular database and this was a deliberate decision. CRM. powered by SAP HANA looks like it will be a no-brainer for the majority of SAP's 14. a change in process that allows further improvements. The reason for this is because SAP HANA provides opportunities to simplify the architecture of the existing solution and simply replacing the database does not provide this opportunity. This is what SAP's CTO Vishal Sikka affectionally calls the "100.10 How does SAP HANA compare to Oracle Exalytics? 11 . the analytics functions are realtime where they were replicated before.the spinning disks. 1. SAP HANA does in this instance not require a separate data warehouse for analytics . First. out the box. It will still run faster than ERP on Oracle or DB2.000 BW customers. it is already possible to run the Business Suite on IMDB and SAP has trialled moving some large databases into HANA already. For example.you can just build real-time virtual OLAP functions on top of your transactional OLTP store. SAP NetWeaver BW 7. an inefficient design and third. SAP's demos show hundreds of billions of records of data being aggregated in a matter of seconds.
1. but once the Business Suite runs on IMDB. HANA stores a copy on magnetic disk.saying that it can cost as little as €13k per 64GB unit. As usual with SAP licenses. In case of hardware failure. 1. And you do not pay a performance penalty because everything happens in-memory. in case of power failure or the like. another will replace it.15 What compression can I expect as compared to alternatives? 12 . in case of power failure in the main site. However if you run an Oracle or DB2 data mart that performs poorly. you store the information once in the SAP HANA appliance. this all happens within the same machine. If the power goes out. and there is some discounting based on volume.13 Why is SAP HANA so fast? Regular RDBMS technologies put the information on spinning plates of iron (hard disks) from which the information is retrieved. it will reload the last save point and then apply the log files when you switch it back on. you can easily incrementally expand up to 256GB. In addition. 1. The same applies if you buy your SAP BW licenses from another database vendor directly. HANA stores information in electronic memory.11 What happens if hardware or power fails? Intel has a comprehensive collection of Reliability. you could replace this outright with SAP HANA and that would allow you to actually eliminate some licenses today. it's best to contact your account exec directly and talk to them. most SAP systems have the database on one system and a calculation engine on another. With Oracle. then you replicate this into the Exalytics Times-Ten database for reporting and into Essbase for forecasting. This doesn't affect anything in the short term because many of those people buying HANA today will still need an Oracle ERP system. SAP HANA writes a copy of what is happening in memory to disk. analytical reporting. From that one store you can do transaction processing. 1. SAP HANA supports fully Highly Available scenarios and standby nodes. and the smallest appliance is 128GB.This is a perfect example of the simplification example I gave in the last question. Oracle won't be needed any more by SAP customers who purchase HANA. By contrast if you use SAP HANA. enables the solution to be more easily changed and more agile. Note that Steve Lucas from SAP has given some HANA prices for BW to the market -What Oracle won't tell you about SAP HANA . In addition. This means if you buy 64GB today. and they pass information between them. forecasting and predictives. Availability and Scalability features in their SAP HANA hardware and this includes predictive memory failure. This is designed to avoid hardware failure but obviously hardware does fail from time to time. you need to build your transactional database in Exadata. fault tolerance and recovery of failed memory.12 What does SAP HANA cost? SAP HANA is priced by the 64GB unit right now. which is upgradeable to 256GB. It also supports Disaster Recovery using disk mirroring to an alternative location. using a combination of save-points and log files. With HANA.14 Does SAP HANA replace Oracle? It's the elephant in the room. The minimum purchase amount is currently 64GB. 1. which is some 50x faster (depending on how you calculate). If one node fails. With HANA you are not moving information around the whole time and this simplifies the solution.
Remember that you do get compression on this so this is equivalent to 160TB of raw data for a 16TB appliance. These volumes remain the domain of solutions like Hadoop. If you are using DB2 or Oracle compression then you can expect that to reduce to 5x compression with HANA in an average scenario. but only in the labs so far. 2. which refers to the kind of huge datasets that FaceBook or Google have to store . If you have raw flat files or uncompressed databases like DB2 or Oracle then I generally see 10x compression to be a good start point. you can expect by 2013 for much larger appliances to be certified. Fujitsu and IBM currently do not have a blade solution and IBM have stated that it is not their current strategy. HANA currently only scales to the small-end of Big Data. they had 27TB of SAP BW database. There are no public plans to compete against IBM/HP/Dell in this space. but it may make sense for SAP to enter the appliance market. If you can make the mental jump of what that would mean to your organisation then you can see the potential.sap.3 Does SAP make its own SAP HANA hardware? Yes.4 How big does SAP HANA scale? The largest certified appliance is 16TB and there are 100TB appliances in the lab. 2. 2. You transact. they started with 7TB and got 5x compression. which will run on HANA. which requires a change in the design philosophy of computer systems. the better the compression. SAP HANA database hardware 2. So when the database was moved to SAP HANA.not Terabytes. given that we moved from 1TB to 16TB certified appliances in the last year.16 What is the wider market opportunity for in-memory technologies? I think that this is the biggest challenge that SAP HANA provides today: because it simplifies and changes the way in which computer solutions can be designed. This is because their GPFS filesystem requires local disk storage in the system and blades cannot hold this. Note that this is missing the point because HANA allows simplification. 2. but rather Petabytes. plan. forecast and consolidate on a single version of the truth. That said. The fewer unique values. In real life this means compression of 27TB down to 1.The answer is it really depends on the number of unique values in your data. I have been talking to a number of people that see the potential and the key is this: you move all your data into one place. In one customer I have dealt with.1 What hardware is supported right now? I have broken out the SAP HANA Hardware guide into a separate FAQ .com/pam (login required). report. 1.2 Why doesn't SAP HANA run on blades? Running SAP HANA on blades is only relevant in multi-node systems. 3. But for "big data" fans. SAP HANA does run on blades from Cisco and HP.1 What source databases does SAP HANA support in real-time? 13 . Technical FAQ 3.The SAP HANA Hardware FAQ There is a supported hardware list on SAP's website at: http://service. especially in the context of Data Centres and even more so in the context of the SAP Business byDesign cloud offering.5TB or 18:1. but 20TB of this was aggregates and indexes used to improve performance.
the Business Content extractors are redirected. but if you buy it through SAP then you may have a restricted license that does not allow for usage of SRS. You can reasonably load into HANA using Data Services every 10 minutes and Data Services allows for excellent flexibility because you can take care of complex business transformations including e.2 What source databases does SAP HANA support for batch loads? If you use SAP BusinessObjects Data Services 4. clarifying some things I may have not explained so well or even just asking a question that I haven't covered would be really useful for the wider market. I hear that SAP plan to open up a certification for third-party ETL tools later in 2012. address verification outside of HANA. 3. the Direct Extractor Connection. SRS has additional restrictions which are worth bearing on mind. which send data from an SAP Business Suite system to SAP HANA. because it allows for application-layer transformations and therefore greater flexibility than the SRS model. What is the difference between SAP Business Warehouse Accelerator (SAP BWA) & SAP HANA? SAP BW Accelerator (SAP BWA) is an in-memory accelerator for BW.There are two mechanisms that HANA supports for near-real-time data loads. 4. First is the Sybase Replication Server (SRS). SAP BWA is focused 14 . only the SAP BI4 suite and Analysis for Excel client are supported. With DXC. In addition there is a new model.0 for bulk loads then pretty much anything.g. If you buy your database license direct from the vendor then you are fine. depending on how you license the database layer of SAP. HANA is a full featured in-memory platform. Data Services was previously called Data Integrator. It can only replicate Unicode data and does not support IBM DB2 compressed tables at this time. extracted data flows into SAP HANA directly. JDBC and MDX standards for BI (or other connections). Again there is set to be a certification process starting later in 2012 that will allow third-party vendors to certify their software. However there are plans to move the Data Services ETL engine into SAP HANA which would allow transformations to happen in-memory. corrections & credits This is a work in progress and your help correcting me. This was expected to be the most common mechanism for SAP data sources but there remain some license challenges around replicating data out of Microsoft and Oracle databases.including the SAP Mobility Platform for real-time replication to mobile devices. Follow-ons. which may allow simplified modelling within HANA. which works with SAP or non-SAP source systems running on Microsoft. SLT is also near-real-time and works from a trigger from the SAP Business Suite products.3 What BI Platforms does SAP HANA support? SAP HANA supports the ODBC. Let me know and I'll expand this as the months go on! Q. This is both database-independent and pretty neat. Note that SLT has now been extended to work with non-SAP source systems. IBM or Oracle databases. and instead of flowing into SAP Business Warehouse. Transform & Load tool that supports many databases. This provides a means to work with Business Content DataSources (DXC). prior to being acquired by Business Objects. BO-DS is a very flexible Extract. BWA was specifically designed accelerate BW queries by reducing the data acquisition time by persisting copies of the InfoCube data in-memory. For those scenarios. This would provide a significant benefit over any other ETL tool. and was previously called Acta. 3. Today. However I have tested a number of different tools on top of HANA and they generally work well . SAP have a second choice of replication mechanism called System Landscape Transformation (SLT).
Part 2 • How HANA affects Data Warehousing • HANA and BW 7. for example. As such. Overview Part 1 • Review In-Memory Overview HANA and BW 7. In this way it will be able to dramatically improve the overall performance of SAP NetWeaver BW by combining the value proposition of both the database & BWA into a single platform. scenarios and use cases while HANA and BW 7. 15 . I've decided to convert the underlying slide presentation into two blogs. I've presented on this topic to many customers and colleagues in and outside Walldorf.0 release and above.see The SAP Run Better Tour .30 .Part 2 • In-Memory @ SAP • HANA and BW 7. It shows what the semiconductor industry predicts on how the listed components will evolve . SAP BWA can be used today with any SAP BW 7.Part 2 • Conclusion • HANA and BW 7.30 ..Part 2 • HANA Scenarios • HANA and BW 7.3 and above. Data can be loaded into SAP HANA from SAP & non-SAP data sources and viewed using SAP BusinessObjects front end tools. let's review the fundamentals behind in-memory computing. HANA & BW 7.on improving the query performance of SAP NetWeaver BW.30 .30 .BW Roadmap.30 . with the first focusing on the motivation. SAP HANA is an in-memory appliance and platform for delivering high-performance analytics and applications. SAP HANA will also act as an In-memory database that will power SAP NetWeaver BW 7.3 PART -1 Over the past few months. let's have a look at the table in figure 1 that I've gratefully borrowed from Andy Bechtolsheim's presentation at HPTS 2009. To that end. Before I start with the first blog please note that the usual disclaimer applies. Everything here has been announced at some SAP event . So I'm focusing on bringing pieces into context rather than revealing something that has not been known before.30 .Part 2 • HANA as BWA • HANA and BW 7.see the ITRS. In the near future.Part 2 looks at the combination of HANA and BW from a technical angle.30 .Part 2 Review In-Memory For a start. As there seems to be such a high demand. it includes a full-featured in-memory database.
Actually. The "however part" (B) is fundamental and carries a big mandate for the software industry. However. SAP's response to this is what has been labeled in-memory computing. the clock rateand the cores. The CAP theorem is an instance of that. the second blog will provide examples in the context of BW for this.Figure 1: CPU module roadmap It is sufficient to look at the first two lines. supporting the multi-core architectures via software parallelism is key • in-memory: a prerequisite for parallelism is to have the related data located close to the cores in local memory • columnar data structures: this.g. e. Moore's law will continue to apply. B. see here for a few examples implemented by Ebay. 16 . is a prerequisite to fit data into main memory. In my opinion. based on MySQL nodes or Hadoop. However. namely exploiting inherent properties of the underlying applications to relieve some of the traditional RDBMS constraints in order to build innovative data processing clusters. SAP's BWA is another good example as it is tailored towards the BW schema. it is something that many other companies already and successfully do. Two things can be concluded from that: A.with power efficiency being the main reason for this change. namely that parallelism will be key on those future CPU architectures. the last item is one of the most overlooked and undervalued in the current debate. it will be based on scaling the number of CPU cores rather than the CPU clock rate . this term over-emphasizes the aspect of main memory and comes a bit short of some other aspects that are at the heart of the performance benefits achieved in this context. in turn. The logic goes along the following lines: • parallelism: as seen in figure 1. the columnar approach is extremely I/O efficient and is an enabler for the next bullet • compression: columnar data can be more efficiently compressed than rowbased data due to a higher repetition of values and thus a higher potential to compress • application-awareness: this is separate from the previous four technology arguments and comes down to building an engine tailored towards the SAP applications.
g. stand-alone SQL database. • extraction programs • DDL code (like CREATE TABLE statements) • constraints. • a full. including hierarchies • defining and interpreting semantics on top of tables and columns. • SAP's implementation of an in-memory DB. e. tailored towards SAP applications. it comprises more than just IMCE • HANA is the term you likely hear in public • for the remainder of this presentation: IMCE ≈ HANA (to avoid too much confusion) How HANA affects Data Warehousing The following pseudo equations originate from some joky internal discussions that we had but have proven to be helpful: 1. in a simplified (albeit not 100% technically correct) way.In-Memory @ SAP SAP's response to the imperative for a new software architecture is its In-Memory Computing Engine (IMCE. you can look at HANA as • roughly: IMCE as an appliance • however. o column X is the parent column of a parent-child hierarchy H associated to dimension D o column Y is a unit key figure with the associated unit stored in column U o column Z is an attribute of dimension members whose key is compound in columns A and B o table T holds natural language descriptions for dimension member keys. aka NewDB). albeit not tied to BW alone anymore. • an OLAP processor for MDX queries. Now. validation rules • data transformations and harmonization • process definitions. Also. HANA is the acronym for High Performance Analytical Appliance. whereby column L indicates the language and column C the description 17 . e. I don't want to engage into a deep essay on IMCE and think that . schedules and monitoring. failure handling (especially consistent restart) • KPI definitions • business semantic like rules on how to convert currencies or fiscal year definitions • management of shared and private dimensions.for simple purposes .g.you can look at IMCE as • an evolution of BWA. Under Xyou can imagine code that is manually written or generated by tools. Today: EDW = RDBMS + X This means that an enterprise data warehouse (EDW) is not equal to a database system but requires a complement (here: X).
especially the performance cost model . how to index and/or partition those tables • (meta data) lifecycle of models and tables. Essentially.HANA Relationship. Y needs to address the same requirements as Xbut in a different way. HANA Scenarios From my experience. Now: RDBMS ⇒ HANA This indicates that traditional RDBMS technology gets overhauled by inmemory computing as implemented in HANA. etc. like versioning. As HANA is not an exact 1:1 replacement of an RDBMS and as the constraints and "physical rules" of in-memory computing changes . It is a paradigm shift similar to moving from analog to digital photography. 2. changes including impact analysis and propagation. Beyond that. to a Y in 3. hierarchies • logging. members. development / test / production setup • (data) lifecycle: archiving and the underlying management of archives (what has been archived and what not. meta data definitions.column P in table Q is a foreign key of members of dimension D.year. Still. especially modeling and management based on higher conceptual levels like dimensions. So. based on hierarchies like day month . auditing and other compliance-related features • etc etc etc In summary. meaning that many more options are possible in Yin comparison to X. week .e.3 enablement of HANA planned for end of 2011. Thus: (new) EDW = HANA + Y Now. 1. previously the X) needs to be adjusted to accommodate those new constraints and rules. This is indicated by moving from X in 1.g. get combined into 3. e. and 2. avoid overlapping data containers.year • table and data management like defining standards on how to store a dimension (tables and their respective layouts). o 18 . First steps will be visible with the BW 7. I've discussed figures 2 and 3 in my blog on The BW . Simply think of all the additional things that are possible with digital photography today! BW will follow this transformation from X to Y by tailoring it towards HANA. It can be a bundle of generated code. BW is an off-the-shelf instance of X. the slides shown in figures 2. manually written programs etc.the software that sits on top (i. there are trade-off decisions behind those scenarios. Please note that there is no "best" scenario but that each of the scenarios in figure 2 over-emphasize a certain property at the expense of another one. 3 and 4 are extremely helpful as they trigger fruitful discussions with customers. there are even new and more opportunities given by the new constraints and rules. X addresses those requirements. This confuses many people who would like SAP to give a simple answer. 3.) • security. referential integrity is guaranteed (yes/no) o time and calendar semantics.quarter .
whether there will be new releases of BWA. learn to operate HANA and already see a large amount of benefits. For example. Figure 2: HANA scenarios. it's like when you buy a car: you need to trade off various aspects for choosing the right model for your specific purposes. whether investsments into BWA would be safe etc. Figure 3: HANA scenarios and their respective trade-offs.note that release 7. e. HANA has a calculation engine that has been improved in comparison to the one in BWA.3 landscape .g.3 is a prerequisite for running BW with HANA: • "conservative approach" (the two small arrows in figure 4): you bring in HANA as an accelerator for your existing BW.But. it should be possible to buy a HANA box that can be set up and configured to run as an accelerator next to a BW like BWA did before. That way. you gain confidence with HANA. I guess. The basic plan is to enable HANA to play the role of a BWA in the future. In other words: in 2012 (plan!). BWA as 19 . • "progressive approach" (the long arrow in figure 4): this translates into migrating the DBMS server underlying your BW system to HANA. HANA as BWA There have been many questions on the BWA-HANA relationship. This offers two options to bring HANA into an existing BW 7.
accelerator becomes obsolete as HANA already incorporates the BWA calculation capabilities. Hopefully. it has clarified what role HANA will play in a BW context. Figure 4: Migration options for a classic towards a HANA-based BW. BW will eventually become a pure management software implementing a best practice approach that orchestrates the heavy data lifting inside HANA. It should become obvious that there is a significant complement even though. HANA and BW 7. 20 . performance critical operators that are today implemented in the BW application stack are moved into the HANA engine. and on a technical level.30 Part 2 will describe some examples on what is possible. Conclusion This concludes this first part.
This action might not be possible to undo. Are you sure you want to continue?