HANA SITSP 2011

3,880 views
3,704 views

Published on

My HANA Overview Presentation on SAP Inside Track São Paulo 2011

Published in: Technology
1 Comment
17 Likes
Statistics
Notes
No Downloads
Views
Total views
3,880
On SlideShare
0
From Embeds
0
Number of Embeds
75
Actions
Shares
0
Downloads
0
Comments
1
Likes
17
Embeds 0
No embeds

No notes for slide
  • Columnar data store benefitsOptimizes load of data to CPUHigh data compressionVery fast data aggregationMakes use of real-life fill of tables (few fields filled, few updates)
  • 4 minutesResponse time and throughput – HANA aka IMCE is sitting on top of the heap here. We have orders of magnitude increase in speed while maintaining high levels of throughput. Because what it does is implement all of the features of the legacy data storage mechanisms IN MEMORY. The only reason we use disk is for recovery and restart. We are the fastest.Before we get into those features, lets position and differentiate HANA with what is out there.Disk based:By the time you position the disk head to read the first block, we have already returned.Traditional DBMS – db2, 11g, mssql, aseNextGen Traditional DBMS –exadata, madison, teradata, nz, really start to blur the line with caching/disk/network optimizationMemory CacheTraditional – memcache, persistence, tangasol, CICS buffer poolsBI Based – MSTR, qlicktech, don’t let those vendors come out equal (yeah we have in memory) NO THEY DON”TWhile the NextGen Traditional DBMS does introduce further memory usage through appliance structures (Exadata for example), this will require deciding which data to store in memory and get good performance on. HANA includes all data in-memory and takes a different approach to ensure good performance on the full dataset.
  • Of the components displayed on this slide, not all are part of HANA. Business Objects Enterprise, the ERP system, the clients etc. are optional components whose presence in the system landscape depends on the customer scenario.The components listed here are: The in-memory computing engine itself, which hosts the actual data stores, a persistence layer, a calculation/execution engine, interfaces and other components The in-memory computing studio which is a front-end delivered with HANA which enables administration of the in-memory computing engine and modeling for the engine. An ERP system in which a replication agentis installed to enable data transfer from ERP to HANADatabase clients (JDBC, ODBC, ODBO) which allow client tools to connect to HANA.Optional components - a NetWeaver BW system or third party systems which can be connected to HANA via SAP BusinessObjects Data Services- a BusinessObjects Enterprise system with Data Services installed.Client tools for reporting off HANA, e.g. MS Excel, SAP BusinessObjectsAnalysis Office, SAP BusinessObjects BI reporting tools. These tools might need components in a BusinessObjects Enterprise system (such as Information Design Tool).In the following slides we take a look at several usage aspects of HANA such as data loading, modelling and reporting and discuss which parts of this setup are important for these aspects.
  • At the top is the connection and session management which creates and manages sessions and connections for the database clients. For each session a set of parameters is maintained such as e.g. auto commit settings or the curernt transaction isolation level.The client requests are analyzed and executed by the set of components summarized as „Request Processing and Execution Control“. Once a session is established, database clients typically use SQL statements to communicate with the in-memory computing engine. For analytical applications the multidimensional query language MDX is supported in addition.Features such as SQL Script, MDX and planning operations are implemented using a common infrastructure called calc engine.At the heart of the in-memory computing engine are two relational engines. The row and the column store. These relational engines act as databases. Both are in-memory databases, that is, their primary data persistence is based in RAM.The row store stores data in row based way. In this respect it behaves like traditional relational databases: data is stored and retrieved in records. A major diffenrence to traditional databases is that all data is always kept in RAM.The column store is a relational column based in-memory data engine. That means data is stored and retrieved in columns. This is an optimal concept for analytical queries. The concept is known e.g. From SAP netweaver BW Accelerator (BWA) where this technology has already demonstrated its potential.Even though the relational engines are memory based, a persistence on less volatile media is required for reasons of data safety. Otherwise a power cut or OS reboot would permanently erase all data in the database. The persistency layer handles page management and logging (redo and Undo logs) and permanently stores data in a disk storage. This storage has seperate volumes for data and log.The engine also has a component called transaction management. Transaction management is required in order to provide consistent views of the data at any given point in time (an ongoing transaction must only see that part of the data that was committed before that transaction was started).Replication Server and Load Controller arethe engine-side part of the Sybase replication manager.
  • One of the promises of HANA is to deliver real-time analytic insight on vast data volumes.For the real-time aspect, data provisioning in real time is required. This is the task of Sybase Replication Server. Tables from the ERP system are initially loaded into HANA. All subsequent changes to these ERP tables are immediately replicated into the HANA server. To this end, replication server makes use of the database logs in the ERP system.There is a tool that helps selecting the tables to be loaded and replicated. This tool is integrated into the In-Memory Computing Studio.Replication Server only allows connecting one SAP ERP system to HANA. Some additional requirements apply regarding the ERP system such as server OS, DBMS system, ERP version, SAP kernel and unicode state (only unicode is supported). Note: 1513496 gives information about Hana restrictions.Systems not fullfilling these requirements can be accessed via data services. This requires a BusinessObjects installation, with a data services server and data services designer on the client. Note 1522554 NetWeaver Support Package requirement for Data Services SAP Extractor support .Note: for practical purposes it will probably not be reasonable to connect to several ERP systems with one HANA box (one via replication, the other(s) via data services) for obvious reasons (same tables existing in all the ERP systems etc).Note: Loading from NetWeaver BW into HANA via data services technically is an application of OpenHub.
  • The High‐performance ANalytic Appliance (HANA) is a hardware and software combination that integrates a number of SAP components (for example, NewDB, Modeler, Data Services) delivered as an optimized hardware appliance in conjunction with leading hardware partners.HANA provides a flexible, data source agnostic, multi‐purpose appliance that has many deployment options. For example, customers can directly analyze large volumes of SAP ERP, SAP BW, or non‐SAP data in “real real‐time” without having to create any form of materialized views. This is possible because the software intelligently leverages the native multi‐core support and massively parallel processing capability of the appliance to provide a data source agnostic high performance analytical engine.
  • Notes: This is a example......
  • Once tables are created in HANA and loaded from the source system, the semantic relationships between the tables need to be modeled.In an ERP system, these relationships are modeled via database views and ABAP code. In HANA, these relations initially do not exist at all.Modeling can be done in several places (bottom-up description): If data services is used to create and fill the table, first modeling decisions can be made here. Data models can be created within the In-Memory Computing Engine. Models are stored in form of views and associated metadata in the engine. The front-end tool to create these models in the In-Memory computing Studio (Information Modeler within that tool). Depending on the front-end tool used to retrieve data from the In-Memory Computing Engine, further modeling decisions can be made in universes (SAP BusinessObjects Information Design Tool) or other semantic layers.
  • In reporting, client tools create queries against the database. Where the actual query is generated depends on the tool used. This slide list some of the possible reporting tools.BusinessObjects Explorer will directly create a call against a HANA interface. Excel will also directly request data via MDX. Front-end tools which report against Universes will have the SQL request against HANA created in the universe layer. BI4 Analysis reports against BICS.Please note that at the time of creating these transparencies, it is not yet decided which front-end tools will be supported in combination with HANA. The front-end tools listed in these slides are candidates.The following client side drivers are delivered with HANA: JDBC ( SQL) ODBC ( SQL) ODBO (short for OLEDB for OLAP  MDX)Which of the drivers will be used depends on the front-end tool used (and sometimes even the way in which the front-end tool is used).
  • Various connectivities exist : (O|J)DBC / ODBC (MDX) / SQL DBC (native lib for NewDB = newDB SDK (data, but also users rights, system management Here we can see BOBJ BI 4.0 client for Reporting, Crystal Report, 2 versions: * CR Enterprise include in BI 4.0 with connectivity though BI 4.0 (aka make usage of the CSL (or DSL as you like)) (C for Common, D for Dynamic) * CR 20xx standalone reporting tool, connectivity through ODBC (ODBO and MDX)BI4.0 Enterprise system will not be discussed here but separate training is available. Please contact SAP Education for further details.
  • Veryclassic BOBJ productpositionningslide, once again, positioning BI products, no good slide show withoutthisslide:ExplorerExplorer is a new BI paradigm: youcan explore your business and findanswerswhenyoudon’tknownwhich question to ask. Indeed, youdon’tneed to understand how the data isstructured, how yourqueries are built. Explorer searchesdirectly on the pre-indexed data in a very intuitive way.This tool is for “Casual User”, “Information workers who are seeking easier self-service environment” or “Users who are involved in day-to-day decisions”Web IntelligenceWeb intelligence is one of the mostadvanced ad-hoc reporting solution on the market. It lets end-users design and analyzetheirown reports and queries. This tool is the one to use for Reporting & Analysis goals, especially for the casual business users. During this webinar, we will only focus on Web Intelligence, connecting to a SAP BW data source.XcelsiusXcelsius bridges the gap between data analysis and visual presentation in a very sexy way. The Target audience is mostly for business users.Crystal ReportsCrystal Reports allowsyou to createOperational or pixel-perfect reportsThe Target audience is IT department for report authoring. It is the tool as well for most business usersfor report consumption.(** not here **)Voyager / Bex Web (=Pioneer)This is a powerful web-based OLAP analysis tool, for analyst users. It can help you to gain insight into business data and make intelligent decisions that impact corporate performance.
  • For Administration of the HANA, the In-Memory Computing Studio has an administration component. Tasks offered by the studio include (but are not limited to): Starting/stopping the In-Memory Computing Engine (upon start, the in-memory stores are reconstructed from the persistence layer) User administration including creating/deleting users and authorizations Table administration, including creating indexes or some part of the configuration for data replication Creating or replaying a backup
  • According to a current survey, 28 percent of IT managers in North America have snooped, and 44 percent of those in Europe, the Middle East, and Africa have done so, too. Around 20 percent of respondents in North America and 31 percent in EMEA say one or more of their co-workers have used administrative privileges to reach confidential or sensitive information.See http://www.darkreading.com/insider-threat/167801100/security/client-security/229401640/it-temptation-to-snoop-too-great.html
  • Auditing does not directly increase the security of the system. But wisely designed, it can help: Uncover security holes Show security breaches and privilege misuses Protect the system owner against accusations of security violation and data misuse The system owner meet their security standards In the current version of the SAP In-Memory Database, security logging and tracing is supported using the standard database log files. The features described in the following sections are supported in SAP HANA 1.0 SPS2, only.
  • Auditing in SPS02: Extensible auditing infrastructureAudit trail is stored using syslog Audit logging of authorization changes
  • The actual message that is written to the syslog is in CSV (comma-separated values) format so that it can be easily parsed and imported into other systems. The CSV format is as follows:<Event Timestamp>;<Service Name>;<Hostname>;<SID>;<Instance Number>;<Port Number>;<Policy Name>;<Policy Type Name>;<Audit Level>;<Audit Action>;<Active User>;<Target Schema>;<Target Object>;<Privilege Name>;<Grantable>;<Role Name>;<Target Principal>;<Success Status>;<Component>;<Section>;<Parameter>;<Old Value>;<New Value>;<Comment>;<Executed Statement>;It is possible to alter the audit configuration so that the audit trail is written to a text file. This must not be used on production systems. The text file writer has severe limitations. For example, it is not written in a thread-safe manner so that multiple entries, being written at the same time, can yield unexpected results. However, this can be very useful during testing the audit policies, as it is much easier to see the results of a policy in action.
  • HANA SITSP 2011

    1. 1. HANA – Overview & Roadmap<br />Henrique Pinto<br />Consultor de Soluções, SAP Brasil<br />Outubro de 2011<br />
    2. 2. Introduction to HANA<br />Core Functionalities<br />Use cases<br />A Typical SAP Landscape Discussion<br />HANA Roadmap<br />
    3. 3. Columnar<br />In-Memory<br /> “By 2012, 70% of Global 1000 organizations will load detailed data into memory as the primary method to optimize BI application performance.” <br /> - Gartner<br />
    4. 4. SAP High-Performance Analytic Appliance (SAP HANA)<br />SAP HANA is a data source agonistic in-memory appliance that enables organizations to analyze business operations in real-time based on large volumes of data <br />Who is it for?<br /> Analyst<br /> Business User<br /> Executive<br />Analyze large volumes of operational data in real-time<br />Access, model, and analyze operational data in a single environment without affecting existing applications or systems<br />Provide a high performance technological foundation for business analytics<br />What is it for?<br />
    5. 5. SAP HANASAP High-Performance Analytic Appliance<br />Preconfigured Analytical Appliance<br /><ul><li>In-Memory software + hardware(HP, IBM, Fujitsu, Cisco)</li></ul>In-Memory Computing Engine Software<br /><ul><li>Data Modeling and Data Management
    6. 6. Real-time Data replication for SAP ECC
    7. 7. Data Integration for 3rd Party Systems</li></ul>Capabilities Enabled<br /><ul><li>Analyze information in real-time at unprecedented speeds on large volumes of non-aggregated data
    8. 8. Create flexible analytic models based on real-time and historic business data
    9. 9. Foundation for new category of applications (e.g., planning, simulation) to significantly outperform current applications in category
    10. 10. Minimizes data duplication</li></ul>Other Applications<br />SAP BusinessObjects<br />SAP <br />HANA<br />MDX<br />SQL<br />BICS<br />In-Memory Computing Engine<br />SAP NetWeaver<br />BW<br />In-Memory<br />Computing<br />Calculation and Planning Engine<br />3rd Party<br />Data Management Service<br />SAP <br />Business Suite<br />Admin and Data Modeling<br />Real–Time Replication Services<br />Data Integration Services<br />
    11. 11. ROW-BASED Storage<br />Tuple 1<br />Tuple 2<br />Tuple 3<br />Tuple 4<br />Column 1<br />Column 4<br />Column 3<br />Column 2<br /> OPTIMIZED for current HW<br /> EasilyCOMPRESSABLE<br />COLUMN-BASED Storage<br />AVOID Bottlenecks – Data Storage<br />
    12. 12. Classical Approach<br />Calculation<br />APPLICATION<br />LAYER<br />DATABASE<br />LAYER<br />MOVEcalculations into database<br /> Only transferRESULTS<br />Calculation<br />Future Approach<br />AVOID Bottlenecks – Data Transfer<br />
    13. 13. In-Memory Computing – The Time is NOWOrchestrating Technology Innovations<br />HW Technology Innovations<br />SAP SW Technology Innovations<br />Row and Column Store<br />Multi-Core Architecture (8 x 8core CPU per blade)<br />Massive parallel scaling with many blades<br />One blade ~$50.000 = 1 Enterprise Class Server<br />Compression<br />Partitioning<br />64bit address space – 2TB in current servers<br />100GB/s data throughput<br />Dramatic decline in price/performance<br />No Aggregate Tables<br />Insert Only on Delta<br />
    14. 14. Response Time<br />In-Memory<br />HANA<br />microseconds10-6<br />Disk-Based DBMS with Memory Cache<br />Or<br />Solid-State DBMS<br />milliseconds10-3<br />Disk-Based DBMS<br />seconds<br />100<br />1,000<br />10,000<br />100,000<br />Throughput (transactions per second)<br />
    15. 15. Introduction to HANA<br />Core Functionalities<br />Use cases<br />A Typical SAP Landscape Discussion<br />HANA Roadmap<br />
    16. 16. Architecture OverviewSAP HANA Appliance and Surroundings<br />SAP HANA Studio<br />Clients<br />MS Excel<br />BI4 Explorer<br />Modeling<br />Administration<br />SAP BI4 universes (WebI,...)<br />Dashboard Design<br />BI4 Analysis<br />ERP<br />SAP HANA Appliance<br />Replication Agent<br />SLT Add-on<br />SAP HANA Database<br />Session Management<br />Log<br />ERP DB<br />Transaction Manager<br />Request Processing / Execution Control<br />Replication Server<br />SQL Parser<br />MDX<br />Authorization Manager<br />SAP Business Objects BI4<br />SQL Script<br />Calc Engine<br />Load Controller<br />Relational Engines<br />SBO BI4 Information Design Tool<br />Data Services Designer<br />Metadata Manager<br />Row Store<br />Column Store<br />Persistence Layer<br />Logger<br />Page Management<br />SBO BI4 servers ( program for client)<br />Data Services<br />Disk Storage<br />Data Volumes<br />Log Volumes<br />Other Source Systems<br />SAP NetWeaver BW<br />3rd Party<br />
    17. 17. SAP HANA Studio<br />Clients<br />MS Excel<br />BI4 Explorer<br />Modeling<br />Administration<br />SAP BI4 universes (WebI,...)<br />Dashboard Design<br />BI4 Analysis<br />ERP<br />SAP HANA Appliance<br />Replication Agent<br />SLT Add-on<br />SAP HANA Database<br />SAP HANA Database<br />Session Management<br />Session Management<br />Log<br />ERP DB<br />Transaction Manager<br />Transaction Manager<br />Request Processing / Execution Control<br />Request Processing / Execution Control<br />Replication Server<br />SQL Parser<br />SQL Parser<br />MDX<br />MDX<br />Authorization Manager<br />Authorization Manager<br />SAP Business Objects BI4<br />SQL Script<br />SQL Script<br />Calc Engine<br />Calc Engine<br />Load Controller<br />Relational Engines<br />Relational Engines<br />SBO BI4 Information Design Tool<br />Data Services Designer<br />Metadata Manager<br />Metadata Manager<br />Row Store<br />Row Store<br />Column Store<br />Column Store<br />Persistence Layer<br />Persistence Layer<br />Logger<br />Logger<br />Page Management<br />Page Management<br />SBO BI4 servers ( program for client)<br />Data Services<br />Disk Storage<br />Disk Storage<br />Data Volumes<br />Data Volumes<br />Log Volumes<br />Log Volumes<br />Other Source Systems<br />SAP NetWeaver BW<br />3rd Party<br />Architecture OverviewThe engine itself<br />
    18. 18. Architecture OverviewLoading Data into HANA<br />SAP HANA Studio<br />Clients<br />MS Excel<br />BI4 Explorer<br />Modeling<br />Administration<br />SAP BI4 universes (WebI,...)<br />Dashboard Design<br />BI4 Analysis<br />ERP<br />SAP HANA Appliance<br />Replication Agent<br />SLT Add-on<br />SAP HANA Database<br />Session Management<br />Log<br />ERP DB<br />Transaction Manager<br />Request Processing / Execution Control<br />Replication Server<br />SQL Parser<br />MDX<br />Authorization Manager<br />Business Objects Enterprise<br />SQL Script<br />Calc Engine<br />Load Controller<br />Relational Engines<br />SBO Information Design Tool<br />Data Services Designer<br />Metadata Manager<br />Row Store<br />Column Store<br />Persistence Layer<br />Logger<br />Page Management<br />Data Services<br />SBO BI4 servers ( program for client)<br />Disk Storage<br />Data Volumes<br />Log Volumes<br />Other Source Systems<br />SAP NetWeaver BW<br />3rd Party<br />
    19. 19. SAP BusinessObjects Data Services 4.0 and HANA<br />Metadata<br />SAPERP<br />Modeler<br />Server<br />Repository<br />BW<br />In-Memory Computing Engine(ICE)<br />Data Load<br />Open Hub<br />Designer and Management Console<br />SAP BusinessObjectsData Services 4.0<br />HANA<br />Any Source<br />© SAP AG 2011 <br />
    20. 20. HANA Modeling leveraging Data Services(Simplified Example using RFC_READ_TABLE)<br />© SAP AG 2011 <br />Create a new DataStore of type “SAP Applications” with specific connection details<br />
    21. 21. Setup Information Modeler to communicate with Data Services (Configure Import Server)<br />© SAP AG 2011 <br />Click “Import” to import meta data via Data Services or use the menu<br />
    22. 22. LT Replication Concept: Trigger-Based ApproachArchitecture and Key Building Blocks <br />SAP HANA Database<br />Source system<br />LT Replication Server<br />DB Trigger<br />Write Modules<br />DBConnection<br />RFCConnection<br />LoggingTables<br />Read Modules<br />Controler Modules<br />Application Tables<br />LT replication server does not have to be a separate SAP system and can run on any SAP system with SAP NetWeaver 7.02 ABAP stack (Kernel 7.20EXT) <br />Application Tables<br />Efficient initialization of data replication based on DB trigger and delta logging concept (as with NearZero downtime approach)<br />Flexible and reliable replication process, incl. data migration (as used for TDMS and SAP LT)<br />Fast data replication via DB connectLT replication functionality is fully integrated with SAP HANA Studio <br />
    23. 23. SAP HANA Appliance – Real Time Replication<br />Landscape Option 1: (SAP ERP 4.6c or SAP ECC 6.0 on a NW release below NW ABAP 7.02)<br /><ul><li>For any customers on SAP ERP 4.6c, utilizing SLT will require setting up an intermediary system with at least NW ABAP 7.02 load controller for replication into HANA
    24. 24. For example, a solution manager system could be used for the SLT Add-on
    25. 25. Supports Non-Unicode or MDMP systems for SAP ERP as long as SLT is installed on a NW 7.02 Unicode system</li></ul>Landscape Option 2: (SAP ECC 6.0+, running on at least NW ABAP 7.02)<br /><ul><li>For any customers on SAP ECC 6.0+ running on NW ABAP 7.02 (must be fully Unicode), utilizing SLT can be done directly for replication into HANA</li></li></ul><li>Technical Requirements and System Set-Up Information for LT Replication Server<br />LT replication server can run on any SAP system with SAP NetWeaver 7.02 ABAP stack (using SAP Kernel 7.20EXT), for example on Solution Manager 7.1 or the source system – it does not have to be a separate SAP system! <br />SAP HANA system<br />Source system<br />LT Replication Server<br />RFCConnection<br />DBConnection<br />Installation:<br /><ul><li> respective DMIS 2010 version
    26. 26. Minimum support pack level: latest available </li></ul>Installation:<br /><ul><li> HANA SPS02: includes LT replication functionality fully integrated into the UI of the HANA modeler</li></ul>Installation:<br /><ul><li> Addon DMIS 2010_1_700
    27. 27. Minimum support pack level: SP04 (planned with release of HANA SPS02) </li></ul>Basic Configuration:<br /><ul><li> Define RFC connection to source system- Define DB connection to HANA system- Define max. number of jobs to be used for data replication</li></ul>Basic Configuration:<br /><ul><li> Optional: define separate table space for logging tables
    28. 28. Define RFC user with appropriate authorization</li></ul>Basic Configuration:<br />- Create a DB user (if required)<br />System Requirements:<br />- SAP Basis: Netweaver 702 with Kernel 7.20EXT (currently limited platform availability) - Filesystem: 100 GB- RAM: 16-32 GB<br /><ul><li> CPU: 2-4 cores
    29. 29. Recommended number of background jobs: 10 </li></ul>System Requirements:<br /><ul><li> SAP Basis 4.6C and higher
    30. 30. All data bases </li></li></ul><li>Architecture OverviewData Modeling<br />SAP HANA Studio<br />Clients<br />MS Excel<br />BI4 Explorer<br />Modeling<br />Administration<br />SAP BI4 universes (WebI,...)<br />Dashboard Design<br />BI4 Analysis<br />ERP<br />SAP HANA Appliance<br />Replication Agent<br />SLT Add-on<br />SAP HANA Database<br />Session Management<br />Log<br />ERP DB<br />Transaction Manager<br />Request Processing / Execution Control<br />Replication Server<br />SQL Parser<br />MDX<br />Authorization Manager<br />Business Objects Enterprise<br />SQL Script<br />Calc Engine<br />Load Controller<br />Relational Engines<br />SBO Information Design Tool<br />Data Services Designer<br />Metadata Manager<br />Row Store<br />Column Store<br />Persistence Layer<br />Logger<br />Page Management<br />Data Services<br />SBO BI4 servers ( program for client)<br />Disk Storage<br />Data Volumes<br />Log Volumes<br />Other Source Systems<br />SAP NetWeaver BW<br />3rd Party<br />
    31. 31. Modeling for HANA 1.0Using In-Memory Computing Studio<br />Step1: (Attribute View)<br />Separate Master Data Modeling from Fact data<br /><ul><li>Build the needed master data objects as ‘Attribute Views’
    32. 32. Join text tables to master data tables
    33. 33. If required: join master data tables to each other (e.g. join ‘Plant’ to ‘Material’)</li></ul>Step 2: (Analytical View)<br />Create Cube-like view by joining attributes view to Fact data<br /><ul><li>Build a ‘Data Foundation’ based on transactional table
    34. 34. Selection of ‘Measures’ (key figures) ...
    35. 35. Add attributes (docking points for joining attribute views)</li></ul> this is basically your ‘fact table’ (key figures <br /> and dimension IDs)<br /><ul><li>Join attribute views to data foundation
    36. 36. Looks a bit like a star schema </li></li></ul><li>Attribute Views...... are the reusable dimensions used for analysis. (Time, Account, Product)<br />© SAP AG 2011<br /><ul><li>What is an Attribute View?</li></ul>Attributes add context to data.<br />Can be regarded as Master Data tables<br />Can be linked to fact tables in Analytical Views<br />
    37. 37. Modeling for HANA 1.0Using In-Memory Computing Studio<br />Step 3: (Calculation View) / Optional<br />If joins are not sufficient create a Calculation View that is something that looks like a View and has SQL Script inside<br /><ul><li>Composite view of other views (tables, re-use join, olap views)
    38. 38. Consists of a Graphical & Script based editor
    39. 39. SQL Script is a HANA-specific functional script language
    40. 40. Think of a ‘SELECT FROM HANA’ as a data flow
    41. 41. JOIN or UNION two or more data flows
    42. 42. Invoke other (built in CE or generic SQL) functions</li></li></ul><li>Analytical View… are the multidimensional views that analyze values from single fact table<br />© SAP AG 2011<br /><ul><li>An Analytic View can be regarded as a “cube”
    43. 43. Multidimensional reporting model
    44. 44. Fact table (data foundation) joined against modelled dimensions (attribute views)
    45. 45. Analytic Views do not store data
    46. 46. Data is read from the joined database tables
    47. 47. Joins and calculated measures are evaluated at run time
    48. 48. Master data for MDX/BICS are stored in system tables</li></li></ul><li>Modeling for HANA 1.0Using In-Memory Computing Studio <br />Step 4: Analytic Privileges<br /><ul><li>Analysis authorizations for row-level security
    49. 49. Can be based on attributes in analytic views
    50. 50. Analytic privilege is always a concrete implementation
    51. 51. I.e. Specific authorization for specified values of given attribute
    52. 52.  you have to create privileges for each group of users</li></li></ul><li>2 Types of Calculation Views<br />© SAP AG 2011<br />GRAPHICAL<br />SQL Script<br /><ul><li>Composite views, re-uses Analytical and Attribute views
    53. 53. SQL / SQL Script / Custom Functions</li></ul>UNION<br />Analytical View<br />UNION<br />Analytical View<br />
    54. 54. How to build content <br />Recommended<br />Not recommended<br />Calculation View<br />Analytical View<br />Tables<br />Attribute View<br />© SAP AG 2011<br />
    55. 55. Architecture OverviewReporting<br />SAP HANA Studio<br />Clients<br />MS Excel<br />BI4 Explorer<br />Modeling<br />Administration<br />SAP BI4 universes (WebI,...)<br />Dashboard Design<br />BI4 Analysis<br />ERP<br />SAP HANA Appliance<br />Replication Agent<br />SLT Add-on<br />SAP HANA Database<br />Session Management<br />Log<br />ERP DB<br />Transaction Manager<br />Request Processing / Execution Control<br />Replication Server<br />SQL Parser<br />MDX<br />Authorization Manager<br />Business Objects Enterprise<br />SQL Script<br />Calc Engine<br />Load Controller<br />Relational Engines<br />SBO Information Design Tool<br />Data Services Designer<br />Metadata Manager<br />Row Store<br />Column Store<br />Persistence Layer<br />Logger<br />Page Management<br />Data Services<br />SBO BI4 servers ( program for client)<br />Disk Storage<br />Data Volumes<br />Log Volumes<br />Other Source Systems<br />SAP NetWeaver BW<br />3rd Party<br />
    56. 56. Reporting on HANA Client and connectivity options<br />© SAP AG 2009<br />Web Intelligence<br />Crystal Reports<br />for Enterprise<br />Are part of SAP BusinessObjects BI 4.0<br />Dashboards<br />Analysis Office v1.1<br />Semantic Layer (universe UNX)<br />Excel<br />Explorer<br />Crystal Reports 2011<br />BICS<br />ODBC<br />JDBC<br />JDBC<br />ODBC<br />JDBC<br />ODBO<br />ODBC<br />MDX<br />SQL<br />SQL<br />SQL<br />SQL<br />SAP HANA <br />SAP In-memory Computing Engine<br />
    57. 57. Reporting on HANA SAP BusinessObjects BI4.0 Reporting Clients<br />© SAP AG 2009<br />Professionally Informed<br />Search &<br />Exploration<br />Dashboarding &<br />Visualization<br />EnterpriseReporting<br />Ad-Hoc QRA<br />Crystal Reports<br />Dashboard Design (Xcelsius)<br />Executives &<br />Managers<br />Explorer<br />Web Intelligence (Interactive Analysis)<br />InformationConsumers<br />Business Analysts<br />Technically Capable<br />Guided<br />Free<br />Interactive Experience<br />
    58. 58. Reporting on HANANative Excel interface - Pivot Tables (ODBO)<br />Multidimensional reporting is available via Excel Pivot Tables<br />This has the advantage of „quick and dirty“ cross-tab style reporting via Excel<br />Numerous disadvantages exist<br />The report definition is only avalable locally (workarounds exist)<br />Subject to performance limitations of the desktop machine where Excel runs<br />Pivot Tables can be initiated numerous ways but primary entry point is via the Excel DATA menu option.<br />© SAP AG 2009<br />
    59. 59. SAP BusinessObjects Analysis, Office Edition<br />© SAP AG 2009<br />
    60. 60. SAP BusinessObjects Analysis, Office Edition<br />Access Analytic and Calculation Views from Analysis Office (MS Excel or Powerpoint) via a locally defined ODBC connection<br />© SAP AG 2009<br />
    61. 61. What is BusinessObjects Explorer?It’s search against BI…<br />Use familiar key-word search to find business information<br /><ul><li>Answers “on-the-fly” and investigative questions</li></ul>Searches directly on pre-indexed data<br /><ul><li>No previous reports or metrics need exist
    62. 62. Provides fast search and exploration</li></ul>Searches across all data sources<br /><ul><li>Any universe accessible source
    63. 63. Any SAP NetWeaver BW Accelerator accessible source
    64. 64. And of course any accessible HANA system</li></li></ul><li>…and Then It’s Exploration Of the Results<br />Intuitively explore on data<br /><ul><li>No data model or data knowledge required</li></ul>Automated relevancy of results<br /><ul><li>Most relevant information is displayed first
    65. 65. Best chart type auto generated</li></ul>Share insights with others<br /><ul><li>Export to CSV or image
    66. 66. Save it locally as a browser bookmark
    67. 67. One-click to send a link to the results by email </li></li></ul><li>Architecture OverviewAdministration<br />SAP HANA Studio<br />MS Excel<br />BI4 Explorer<br />Modeling<br />Administration<br />SAP BI4 universes (WebI,...)<br />Dashboard Design<br />BI4 Analysis<br />ERP<br />SAP HANA Appliance<br />Replication Agent<br />SLT Add-on<br />SAP HANA Database<br />Session Management<br />Log<br />ERP DB<br />Transaction Manager<br />Request Processing / Execution Control<br />Replication Server<br />SQL Parser<br />MDX<br />Authorization Manager<br />Business Objects Enterprise<br />SQL Script<br />Calc Engine<br />Load Controller<br />Relational Engines<br />SBO Information Design Tool<br />Data Services Designer<br />Metadata Manager<br />Row Store<br />Column Store<br />Persistence Layer<br />Logger<br />Page Management<br />Data Services<br />SBO BI4 servers ( program for client)<br />Disk Storage<br />Data Volumes<br />Log Volumes<br />Other Source Systems<br />SAP NetWeaver BW<br />3rd Party<br />
    68. 68. MotivationThreats<br />Internal Threats <br /><ul><li>80-90% of all attacks/security breaches come from inside the intranet
    69. 69. Examples
    70. 70. Unauthorized access to data
    71. 71. Employees looking at salary tables
    72. 72. External consultants gaining access to sensitive internal information
    73. 73. Unauthorized data changes
    74. 74. Employees covering their own mistakes
    75. 75. Privilege abuse Data Import/Export
    76. 76. Most security breaches come from company-internal power users (DBAs)
    77. 77. By assigning themselves additional privileges or roles, or
    78. 78. Log on as different users</li></ul>External Threats <br /><ul><li>Hackers</li></li></ul><li>MotivationTraceability<br />Main requirement to audit a system <br /><ul><li>Traceability of actions performed in that system
    79. 79. Who did or tried to do what when?
    80. 80. Example of actions to be audited
    81. 81. Changes of a users’ authorization
    82. 82. Creation or deletion of database objects
    83. 83. Authentification of users
    84. 84. Changes of the system configuration
    85. 85. Changes of the audit configuration
    86. 86. Access to or alteration of sensitive information</li></li></ul><li>Auditing infrastructure<br />Extensible auditing infrastructure<br /><ul><li>Audit trails
    87. 87. Currently stored via syslog
    88. 88. Syslog is a standard mechanism for logging program messages on Unix/Linux</li></li></ul><li>User ProvisioningHow to get Users into the System<br />Creating Named Users in HANA<br />Actual Database Users<br />Create via SAP HANA Studio<br />Or using standard SQL statements<br />Authentication Methods<br />User / Password<br />Set up and manage passwords using SAP HANA Studio or SQL<br />Kerberos Authentication<br />Certificate-based<br />Requires Named User in HANA DB<br />
    89. 89. Events that are audited<br />Logging of successful and unsuccessful events<br /><ul><li>Access control action list
    90. 90. GRANT ANY
    91. 91. REVOKE ANY
    92. 92. GRANT PRIVILEGE
    93. 93. REVOKE PRIVILEGE
    94. 94. GRANT ROLE
    95. 95. REVOKE ROLE
    96. 96. GRANT STRUCTURED PRIVILEGE
    97. 97. REVOKE STRUCTURED PRIVILEGE
    98. 98. Create/drop principal action list
    99. 99. CREATE USER
    100. 100. DROP USER
    101. 101. CREATE ROLE
    102. 102. DROP ROLE</li></li></ul><li>Audit TrailSyslog example<br /><ul><li>Preparation steps</li></ul>1. Create audit policy <br /> CREATE AUDIT POLICY policyAdministratePrincipals AUDITING ALL CREATE ROLE, DROP ROLE, CREATE USER, DROP USER LEVEL Critical;<br />2. Activate audit<br />ALTER AUDIT POLICY policyAdministratePrincipals ENABLE;<br />3. As SYSTEM user, create new user TESTUSER3<br /><ul><li>Verifying the result in Syslog output
    103. 103. Syslog output file: /var/log/messages
    104. 104. Csv-compatible format</li></ul>May 30 11:57:06 LU00252616 HDB[5212]: 30.05.2011 09:57:06 641 Mon;indexserver;lu00252616;B01;01;30103;POLICYADMINISTRATEPRINCIPALS;CreateDropPrincipalEvent;Critical;CreateUser;SYSTEM;;;;NON GRANTABLE;;TESTUSER3;Successful;;;;;;;create user TESTUSER3 identified by XXXXXXXXXXXXX;<br />Search keyword ‘HDB[‘ in syslog<br />
    105. 105. User ManagementUser and Role Concept<br />User<br />Roles allow grouping privileges<br />Create roles for specific tasks, e.g. <br />Create data models (on a given subset of the data)<br />Activate data models<br />Manage users<br />Export/Import<br />All types of privileges can be granted to a role<br />Individual privileges<br />Roles ( create a hierarchy of roles)<br />Roles / privileges can be assigned to users<br />User / Role management are closely related<br />Reflected in almost identical editor<br />Role: edit + activate<br />Role: editmodel<br />Role: activatemodel<br />Package:activate<br />SQL:writeruntimeobject<br />Package:create/ editmodels<br />SQL:select<br />
    106. 106. Introduction to HANA<br />Core Functionalities<br />Use cases<br />A Typical SAP Landscape Discussion<br />HANA Roadmap<br />
    107. 107. SAP HANA asAcceleratorfor SAP ApplicationsExample: CO-PA Accelerated by SAP HANA<br />SAP ECC on legacy DB with secondary DB Connection into HANA<br />BI 4.0 (optional)<br />SAP GUI<br />SAP ECC<br />Analytics<br />Drill-down reporting<br />COPA Application<br />Generate HANA model<br />Aggregation Levels<br />Read Interface<br />Optional: LT Replication<br />SAP HANA Database<br />Calculation Engine<br />Secondary DB connectionRead / write<br />Primary DB connectionRead / write<br /> Aggregation Engine<br />Analytic indexes<br />DBMS<br />Redundant copy of ECC tables<br /><ul><li>Data duplicatedinto SAP HANA
    108. 108. Read interfacesaccesses SAP HANA ifavailable</li></ul>This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.<br />
    109. 109. DBMS<br />SAP HANA as Primary DB in Application ServerFirst example: BW 7.30 running on HANA …expected soon<br />SAP NetWeaver BW as a HANA based system (with “built-in” BWA)<br />SAP NetWeaver BW<br />HANA<br />DW Management<br />Calculation Engine<br /> Aggregation Engine<br />Analytic indexes<br />Analytic<br />Engine<br />Includes SAP NetWeaver BW Accelerator functionality<br /> Data Store Objects<br /> Master Data<br />Metadata<br /> InfoCube Index<br /><br /><br /> Single Data Management for Row- and Column based storage <br />DBMS<br /><ul><li>Integrated engine for data management and in-memory processing of analytical capabilities
    110. 110. Pure DB conversion. No re-implementation required.</li></ul>This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.<br />
    111. 111. Introduction to HANA<br />Core Functionalities<br />Use cases<br />A Typical SAP Landscape Discussion<br />HANA Roadmap<br />
    112. 112. Your SAP Environment Today<br />SAP BW<br />InfoCubes<br />ODS<br />Traditional DB<br />Oracle, DB2, TD, SQL Server, ASE<br />SAP ECC<br />Other<br />Non-SAP<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />
    113. 113. With SAP BWA and Explorer<br />SAP BI 4.0<br />SAP BW<br />Explorer<br />InfoCubes<br />BWA<br />ODS<br />Traditional DB<br />Oracle, DB2, TD, SQL Server, ASE<br />SAP ECC<br />Other<br />Non-SAP<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />
    114. 114. Accelerate All BW Content with SAP BW 7.3<br />SAP BI 4.0<br />SAP BW<br />Explorer<br />InfoCubes<br />BWA<br />BWA<br />ODS<br />Traditional DB<br />Oracle, DB2, TD, SQL Server, ASE<br />SAP ECC<br />Other<br />Non-SAP<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />
    115. 115. Low Latency Operational ReportingSAP HANA<br />SAP BI 4.0<br />SAP BW<br />Explorer<br />InfoCubes<br />BWA<br />BWA<br />Agile Data Mart<br />ODS<br />SAP HANA<br />Traditional DB<br />Oracle, DB2, TD, SQL Server, ASE<br />SAP ECC<br />Other<br />Non-SAP<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />
    116. 116. In-Memory Applications with SAP HANA<br />SAP BI 4.0<br />SAP BW<br />Explorer<br />InfoCubes<br />BWA<br />BWA<br />Agile Data Mart<br />In-Memory<br />Apps<br />ODS<br />SAP HANA<br />1.0<br />Traditional DB<br />Oracle, DB2, TD, SQL Server, ASE<br />SAP ECC<br />Other<br />Non-SAP<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />
    117. 117. SimplifySingle HANA Platform for All Analytical Apps<br />SAP BI 4.0<br />SAP BW<br />InfoCubes<br />Agile Data Mart<br />In-Memory<br />Apps<br />ODS<br />SAP HANA<br />SAP ECC<br />Other<br />Non-SAP<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />
    118. 118. SimplifySingle HANA Platform for All Analytical Apps<br />SAP BI 4.0<br />Enterprise Data Warehouse<br />Sybase IQ<br />SAP BW<br />InfoCubes<br />Agile Data Mart<br />In-Memory<br />Apps<br />ODS<br />SAP HANA<br />SAP ECC<br />Other<br />Non-SAP<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />
    119. 119. Simplify All SAP Applications<br />SAP BI 4.0<br />SAP BW<br />InfoCubes<br />Agile Data Mart<br />In-Memory<br />Apps<br />SAP ECC<br />ODS<br />SAP HANA<br />Other<br />Non-SAP<br />Traditional DB<br />Oracle, DB2, SQL Server, ASE<br />
    120. 120. Introduction to HANA<br />Core Functionalities<br />Use cases<br />A Typical SAP Landscape Discussion<br />HANA Roadmap<br />
    121. 121. What’s New in HANA 1.0 GA <br />Link to Main Presentation<br />Improved supportability<br />Error tracking & performance tracing<br />Unified tracing capabilities<br />Improved SQL Script support<br />Unified stored procedure language ( SQL script V2)<br />Procedural extensions to SQL script V2 <br />Improved optimizer<br />Massively improved column/row optimization ( i.e. full outer join optimizations)<br />All major functionalities are supported with “clean” SQL<br />Extended model support for HANA appliance ( i.e. left outer join support in OLAP engine)<br />
    122. 122. What’s New in HANA 1.0 SPS 2 <br />Link to Main Presentation<br />Distribution<br />Distributed NewDB on one or multiple nodes<br />Support of table and range-based partitioning <br />Automatic landscape reorganization<br />Back-up & Recovery and cold standby distributed scenarios<br />Trigger-based Data replication<br />Incorporation of SLT Basis<br />Security Auditing<br /><ul><li>Extensible auditing infrastructure
    123. 123. Auditing of authorization changes</li></li></ul><li>What’s New in HANA 1.0 SPS 3 <br />Link to Main Presentation<br />Text search engine<br />Main memory text search engine available in NewDB<br />Full SQL integration<br />Freestyle & other search capabilities similar to TREX engine<br />Strong cooperation with Enterprise Search and FuzzyLogic team<br />BW support <br />NewDB as database for BW on NW 7.30<br />In-memory optimized DSO objects<br />New C++ data load mechanism ( DSO activation)<br />New “number range’ handling<br />C++ version of BW data compaction<br />In-memory optimized InfoCubes: Faster data loads and simplified modeling<br />Piush down of OLAP engine into NewDB<br />-> NewDB will be by far the fastest DB for a 7.30 BW system<br />Information Composer<br />Key user data manipulation and modeling<br />System R integration<br />Integrated LCM<br />Live Update service<br />
    124. 124. What’s New in HANA 1.0 SPS 3 <br />Link to Main Presentation<br />Live Cache Integration<br />LifeCache integrated with full transactional consistency<br />First version available mid of May<br />Extended LC usage in later versions<br />Disc tables<br />Disc tables with limited functionality <br />Used for aged data and rarely used data<br />New implementation based on MaxDB knowledge and experience<br />Business functions<br />Currency/Unit conversion, calendar, fiscal period, number range<br />Statistic functions<br />Staging area<br />Time dependant functionalities<br />Planning engine<br />Operations like Disaggregation, copy, write-back<br />Supports BW – IP and ByD<br />Includes linear equation solver<br />
    125. 125. What’s New in HANA 1.0 SPS 3 <br />Link to Main Presentation<br />NGAP support <br />Fast data exchange between appserver and database <br />SQL script support in appserver<br />Better data type compatibility ( text, GUID, decfloat, dates) <br />Back-up & Recovery and Security<br />Point-in-time recovery<br />Log backups<br /> Additional auditing functions<br />SSL connection encryption with certificates for client connections<br />HANA-SAP IDM integration for user provisioning into IMDB<br />
    126. 126. “Innovation“<br />Mid-Term (Plan)<br />“Transformation”<br />Longer-Term (Plan)<br />“Renovation”<br />SAP HANA 1.0<br />Ramp-Up since Dec 2010<br />One Store for Data and Analytics<br /><ul><li>SAP HANA only persistence layer for SAP Business Suite
    127. 127. SAP Business Suite optimized for in-memory computing</li></ul>In-Memory Analytics<br /><ul><li>SAP HANA real-time operational analytics
    128. 128. Complete BI Suite with BI 4 runs on SAP HANA</li></ul>Next-gen Applications<br /><ul><li>SAP BW fully running on SAP HANA
    129. 129. SAP HANA platform for in-memory apps
    130. 130. SAP Business Suite runs on SAP HANA
    131. 131. Further optimization of BI 4 Suite for SAP HANA
    132. 132. Industry and LOB Analytic Apps </li></ul>Capabilities<br /><ul><li>Flexible real time analysis of operations at non-aggregated level
    133. 133. Real-Time operational planning and simulation capabilities: link to execution
    134. 134. Primary persistence and optimized for SAP BW
    135. 135. Reduced landscape complexity
    136. 136. Value chain transformation</li></ul>Benefits<br />SAP In-Memory StrategyProduct Strategy and Plan<br />
    137. 137. Obrigado!<br />Contato:<br />Henrique Pinto<br />henrique.pinto@sap.com<br />

    ×