Skip to main content

SAP HANA System Architecture Overview


Server Component Description
Index server The index server contains the actual data stores and the engines for processing the data.
Name server The name server owns the information about the topology of the SAP HANA system. In a distributed system with instances of the SAP HANA database on multiple hosts, the name server knows where the components are running and which data is located on which server.
XS advanced runtime As of SAP HANA 1.0 SPS 11, SAP HANA includes an additional run-time environment for application development: SAP HANA extended application services (XS), advanced model. SAP HANA XS advanced model represents an evolution of the application server architecture within SAP HANA by building upon the strengths (and expanding the scope) of SAP HANA extended application services (XS), classic model.
The SAP HANA XS advanced runtime consists of several processes for platform services and for executing applications. For more information about the individual services, see the table below.
The SAP HANA XS Advanced runtime runs either on dedicated hosts or together with other SAP HANA components on the same host.
SAP HANA Deployment Infrastructure (HDI) server HDI handles the deployment of design-time artifacts into SAP HANA.
XS classic server SAP HANA Extended Application Services (SAP HANA XS) is the application server for native SAP HANA-based web applications. It is installed with the SAP HANA system and allows developers to write and run SAP HANA-based applications without the need to run an additional application server. SAP HANA XS is also used to run web-based tools that come with SAP HANA, for instance for administration, lifecycle management and development.
SAP HANA XS classic is the original implementation of SAP HANA XS.
The XS classic server can run as a separate server process or embedded within the index server.
Extended store server The extended store server is part of the SAP HANA dynamic tiering option for SAP HANA. It provides a high-performance disk-based column store for very big data up to the petabyte range.
For more information about SAP HANA dynamic tiering, see SAP HANA Options and Capabilities on SAP Help Portal.
Data provisioning server The data provisioning server is part of the SAP HANA smart data integration option for SAP HANA. It provides capabilities such as data provisioning in real time and batch mode, real-time data transformations, data quality functions, adapters for various types of remote sources, and an adapter SDK for developing additional adapters.
For more information about SAP HANA smart data integration, see SAP HANA Options and Capabilities on SAP Help Portal.
Streaming cluster The streaming cluster is part of the SAP HANA smart data streaming option for SAP HANA. Smart data streaming extends SAP HANA with capabilities of SAP Event Stream Processor for consuming data streams and complex event processing.
For more information about SAP HANA smart data streaming, see SAP HANA Options and Capabilities on SAP Help Portal.
Accelerator for SAP ASE The SAP ASE server is part of the SAP HANA Accelerator for SAP ASE option for SAP HANA. It provides SAP Adaptive Server Enterprise (ASE) users the ability to use SAP HANA on SAP ASE data, for real-time analytics,
SAP HANA remote data sync The remote data sync server is part of the SAP HANA Real-Time Replication option for SAP HANA. SAP HANA remote data sync is a session-based synchronization technology designed to synchronize SAP SQL Anywhere remote databases with a consolidated database.
Labels:

Comments

Post a Comment

Popular posts from this blog

What is Tensor Parallelism and relationship between Buffer and GPU

  Tensor Parallelism in GPU Tensor parallelism is a technique used to distribute the computation of large tensor operations across multiple GPUs or multiple cores within a GPU .   It is an essential method for improving the performance and scalability of deep learning models, particularly when dealing with very large models that cannot fit into the memory of a single GPU. Key Concepts Tensor Operations : Tensors are multidimensional arrays used extensively in deep learning. Common tensor operations include matrix multiplication, convolution, and element-wise operations. Parallelism : Parallelism involves dividing a task into smaller sub-tasks that can be executed simultaneously. This approach leverages the parallel processing capabilities of GPUs to speed up computations. How Tensor Parallelism Works Splitting Tensors : The core idea of tensor parallelism is to split large tensors into smaller chunks that can be processed in parallel. Each chunk is assigned to a different GP...
Post a Comment
Read more

Data Wrangling vs EDA

  Aspect Data Wrangling (Data Preprocessing) Exploratory Data Analysis (EDA) Objective Prepare raw data for modeling by cleaning, transforming, and formatting it appropriately. Explore and understand the data to gain insights, identify patterns, and make decisions on data handling and modeling. Order Typically performed as a preliminary step before EDA. Usually conducted after data wrangling to further investigate data characteristics. Data Handling Focuses on data cleaning, filling missing values, encoding categorical variables, and scaling features. Involves data visualization, statistical analysis, and summary statistics to uncover patterns, relationships, and anomalies. Techniques Techniques include imputation, outlier detection, feature scaling, and one-hot encoding. Techniques include histograms, scatter plots, box plots, correlation matrices, and descriptive statistics. Data Transformation Involves structural changes to the dataset, such as feature engineering, data normaliz...
Post a Comment
Read more

What's replicated, what's not?

Logged operations are replicated. These include, but are not limited to: DDL DML Create/alter table space Create/alter storage group Create/alter buffer pool XML data. Logged LOBs Not logged operations are not replicated. These include, but are not limited to: Database configuration parameters (this allows primary and standby databases to be configured differently). "Not logged initially" tables Not logged LOBs UDF (User Defined Function) libraries. UDF DDL is replicated. But the libraries used by UDF (such as C or Java libraries)  are not replicated, because they are not stored in the database. Users must manually copy the libraries to the standby. Note: You can use database configuration parameter  BLOCKNONLOGGED  to block not logged operations on the primary.
Post a Comment
Read more