SAP HANA Database

SAP HANA is an in-memory, column-oriented, relational database management system. It
combines online analytical processing (OLAP) and online transaction processing (OLTP) inone database system. It’s primary function as database server is to store and retrieve data as requested by the applications. In addition, it performs advanced analytics, such as predictive analytics, spatial data processing, text analytics, text search, streaming analytics, and graph data processing. It also includes ETL capabilities as well as an application server. Because SAP HANA is so fast, it does not require sums, indexes, materialized views, or aggregates. This reduces the database footprint. Everything is calculated on-demand and in main memory. This makes it possible for companies to run online transaction processing (OLTP) and analytics applications (OLAP) on the same instance at the same time. It allows for any type of real-time, specific queries, and analyses. On top of this, SAP has built solutions to all of the problems of columnar databases, such as concurrency (SAP HANA uses MVCC), and row-level insert and update performance (SAP HANA uses various mechanisms, such as a delta store). SAP also added engines inside SAP HANA to provide virtual online analytical processing (OLAP) functionality, data virtualization, text analysis, search, geospatial, graph, and Web. It supports open standards, such as Representational State Transfer (REST), JavaScript Object Notation (JSON), OLE DB for OLAP (ODBO), MultiDimensional eXpressions (MDX), Open Database Connectivity (ODBC), and Java Database Connectivity (JDBC).
HANA administration deals with managing SAP HANA system in a single and distributed system environment. Each HANA system can contain multi node architecture with each node containing multiple processors for fast speed data analysis and real-time data provisioning. You can use Smart data access to get the data from non-SAP systems without importing the data to HANA database, and virtual tables can be used to perform read/write data operations.
SAP HANA Administration includes the following activities:
  1.  SAP HANA multiple host system management
  2.  SAP HANA Administration Tools
  3.  SAP HANA System Management and Availability
  4.  SAP HANA Life cycle Management
  5.  SAP HANA Security and User Management
  6.  SAP HANA Backup and Recovery Management
  7.  SAP HANA Data Provisioning and Integration with non-SAP systems

Comments

Post a Comment

Popular posts from this blog

SPOOL WORK PROCESS

Spool Process: It is the Only Process that is used to output the documents to a Printer, fax, email etc.. Spool Work Processes are created by using parameter risp/wp_no_spo=1 it is possible to configure more than one spool work process based on available resources. Spool Process Work Flow: User Submits the request to print a Document. The Dialog Process handles the request and print directly or schedules to print in the background.The Print requests are stored in the TemSe(Temporary Sequential Files) Temporary Sequential Files are stored either at File System or at database Level which is defined by parameter rspo/store_location. rspo/store_location=”G” or ‘DB’ G means global directory stores the TEMSE in /usr/sap/SID/SYS/global db mean the Tables TST01 and TST03.(TST01 Contains Print Attributes and TST03 Contains the Spool Data to be Printed) Due to Spool in DB the DB Size Increases, as a Result, the backup time increases and Tapes may not fit with the data for S...
Read more

ENQUEUE WORK PROCESS

It is used to lock and unlock the Objects during an update.These locks are displayed in SM12 and Held for longer hours until the transaction is committed or rollback.These locks are issued from a lock table which resides in the main memory of the instance where enqueue process is created/located. Enque Processes are configured by parameter rdisp/wp_no_enq=1. Generally One Enque Process for instance is sufficient,more then one is required in a massive update system. The Lock table size on the memory ranges between 4mb to 100 MB(200 MB in the Net weaver 7.3 Systems ) It is defined by parameter enque/table_size=4 to 200 MB. For 4mb of enqueue table size, the Number of lock/owners/objects/arguments can be restricted up to 3715. Enqueue Flow: User submits the Request for an Update. The Dialog or Background Process Handles the Request Dia or BTC Processes communicates with Enqueue Process and obtains a lock on the record so that no other user has to write access to that r...
Read more

DIALOG PROCESS

Dialog Process: It is the only process that is used to communicate with end users Interactively using Classic GUI or Through RFC or through Http Protocol. The Average Response Time for each dialog step is 600 ms.it is displayed through ST03n Each Process can execute up to a maximum runtime of 600 seconds.if any process goes beyond this time an additional time of 60 seconds is given and the process is timed out.(ST22)(it is not mandatory to allocate additional 60 seconds Each Process Serves 5-10 users.(Calculated based on ST07) Each Process Requires 75mb to 300 mb Memory Each Process can Handle the requests that are initiated for background, spool & update and update them in temporary tables. Dialog Process is not restricted to a User and Users are not restricted to a process which is referred as process multiplexing Parameters to configure dialog processes is rdisp/wp_no_dia There should be at least minimum two dialog processes and maximum up to 100 processes. The ...
Read more