You are on page 1of 4

HANA NOTES Video 1: SAP HANA appliance is new innovative product from SAP which uses in-memory technology

to achieve breaktrough performance in scanning, grouping, and aggregating data for reporting purposes. Data agnostic Real-time Very, very fast 2 million records per millisecond per core 10 million complex aggregations calculated on the fly per second per core Random complex queries on over 450 billion records in a matter of seconds. Parallel processing Uses column AND row storage 64-bit server architecture

Terminology SAP HANA appliance software -- appliance SAP HANA database -- database SAP HANA application cloud -- cloud SAP HANA studio client Always use SAP HANA, not simply HANA

Creating Models in SAP HANA Select ERP tables, and understand metadata using transaction SD11 LOAD ERP tables into SAP HANA Recreate table relationships in SAP HANA Create analysis authorizations Build report(s) on top of data model Verify that what you see is correct

Video 2: Look & Feel Java-based Eclipse environment targeted for administrator use Starting out, choose perspective (pre-defined views) o Administration console perspective Used to administrate and monitor the engine Need server address and instance number Also need user and password to connect to instance o Information Modeler perspective Used by PR architects

Create new packages and views and analytic privileges, and procedures May set a default client number using options. o Documentation view perspective Links to current available documentation o Lifecycle management perspective Update appliance software Navigator panel o In navigator view, each instance has its own tree o The created column views are always located in the schema _SYS_BIC o Metadata in _SYS_BI o Content organized in packages o Attribute views, analytic views, calculation views, analytic privileges organized in folders

Video 3: Architecture SAP HANA database developed using C++ and runs on Linux servers SAP HANA database system Consists of: o Index Server Most important server Contains actual data and engines for processing o XS Engine Optional component which allows clients to get data via access engine (HTTP) o Preprocessor server Analyzing text data o Statistics server Collects information about status, performance, and resource consumption from all other components o Name server Hold info about topology of database Used in distributed setup on instances Know where components are running and which data is located on which server Index server components o Connection and Session management o Transaction manager Coordinates transactions, keeps track of running and closed transactions o Request Processing and execution control SQL processor Stored procedure processor Planning engine MDX engine Calc engine

Authentication Invoked when new connection is established o Authorization manager Invoked by other components of Index server o Relational stores Row store Stored in RAM Column store Stored in RAM Disk based store Stored in disk Used for tracing data or old data that isnt kept in memory o Object store o Persistence Layer Page management Logger Responsible for retrieving data from disk storage o Disk storage Data volumes Transaction log volumes o Repository Provides versioning of metadata objects Supports export and import of repository content Loading data into HANA o Using data services Load ERP or third party data into relational stores o Using SLT System (SAP landscape transformation) Need DB connection from SLT to HANA database Need to create RFC connection from source o Direct extraction connection Use BW extractors to load into HANA Persistence Layer o Ensures database is restored to most recent committed state after restart or power failure o Regular savepoints full persisted image of DB at time of savepoint o Captures logs o Default is every 10 minutes (can be changed) o Data belonging to last written savepoint will NOT be overwritten o Saves committed AND uncommitted o Changelog is acquired Backup and recovery options

o o o

Can make backups of data volumes, log volumes, and configuration files If Disk failure happens, we can restore state just before the failure (except noncommitted transactions) Can also do Point in time Recovery or last data backup

Video 4: Data Provisioning Using BODS to import metadata into HANA o Create a conection to an SAP target system SAP ERP, for example o Import the metadata via HANA studio into SAP HANA o Import the metadata back into Data Services o Create a data services job to populate SAP HANA o Execute a DS job to populate SAP HANA o Preview uploaded data