Explore topic-wise InterviewSolutions in .

During COMPILATION, the call to the procedure is REWRITTEN for processing by the CALCULATION ENGINE.

During compilation, the call to the procedure is rewritten for processing by the calculation engine.

When a user creates a new procedure, the HANA DATABASE QUERY compiler FIRST:

• PARSE the statements
• Check the statement semantic correctness
• Optimize the code for Declarative and Imperative LOGIC
• Code generation creates Calculation models for Declarative logic and L nodes for Imperative logic
• Compiled procedure creates Content in the database Catalog and in Repository

When a user creates a new procedure, the HANA database query compiler first:

 It should be used in CASES where other modeling CONSTRUCTS of HANA such as Attribute views or ANALYTIC views are not sufficient.

 It should be used in cases where other modeling constructs of HANA such as Attribute views or Analytic views are not sufficient.

TRACE operator. It traces the tabular data passed as its argument into a local temporary table and return its INPUT unmodified. The names of the temporary tables can be retrieved from the SYS.SQL SCRIPT TRACE VIEW. 

Example: out = TRACE (:input);

TRACE operator. It traces the tabular data passed as its argument into a local temporary table and return its input unmodified. The names of the temporary tables can be retrieved from the SYS.SQL SCRIPT TRACE view. 

Example: out = TRACE (:input);

Break means LOOP should stop PROCESSING, CONTINUE means loop should stop processing the CURRENT ITERATION and immediately start processing the next iteration.

Break means loop should stop processing, CONTINUE means loop should stop processing the current iteration and immediately start processing the next iteration.

From the ADMINISTRATION perspective, navigate to TAB “Trace Configuration” . In ORDER to change settings, you need to have system PRIVILEGES “TRACE ADMIN” and “INFILE ADMIN”. 

From the Administration perspective, navigate to tab “Trace Configuration” . In order to change settings, you need to have system privileges “TRACE ADMIN” and “INFILE ADMIN”. 

It is a set of SQL extensions for SAP HANA DATABASE which allow developers to push data intensive logic into the database.

It is a set of SQL extensions for SAP HANA database which allow developers to push data intensive logic into the database.

SAP HANA 1.0 is an analytics APPLIANCE which consists of certified hardware, and In Memory DataBase (IMDB), an Analytics ENGINE and some tooling for getting data in and out of HANA. The LOGIC and structures are built by the user and a tool is used.

EXAMPLE: SAP BusinessObjects, to visualize or analyze data.

SAP HANA 1.0 is an analytics appliance which consists of certified hardware, and In Memory DataBase (IMDB), an Analytics Engine and some tooling for getting data in and out of HANA. The logic and structures are built by the user and a tool is used.

Example: SAP BusinessObjects, to visualize or analyze data.

The full form of SLT is SAP Landscape Transformation which is nothing but a trigger based replication. It is the replication TECHNOLOGY to pass the DATA from the source system to the TARGET system. Here the source can be EITHER SAP or non-SAP whereas the Target system is SAP HANA system which contains HANA database.

The full form of SLT is SAP Landscape Transformation which is nothing but a trigger based replication. It is the replication technology to pass the data from the source system to the target system. Here the source can be either SAP or non-SAP whereas the Target system is SAP HANA system which contains HANA database.

YES. It can be LOADED and REPLICATED for up to 4 TARGETS.

Yes. It can be loaded and replicated for up to 4 targets.

The information required to create the CONNECTION between the source system, SLT system, and the SAP HANA system is specified within the SLT system as a CONFIGURATION. A new configuration in Configuration & MONITORING DASHBOARD (transaction LTR) can hence be defined.

The information required to create the connection between the source system, SLT system, and the SAP HANA system is specified within the SLT system as a Configuration. A new configuration in Configuration & Monitoring Dashboard (transaction LTR) can hence be defined.

DMIS add-on is installed in SLT replication SERVER for SAP source systems. The role IUUC_REPL_CONTENT is ASSIGNED to the user for RFC connection but not DDIC. DMIS add-on is notrequired and grants a database user SUFFICIENT authorization for data replication for a non-SAP source SYSTEM.

DMIS add-on is installed in SLT replication server for SAP source systems. The role IUUC_REPL_CONTENT is assigned to the user for RFC connection but not DDIC. DMIS add-on is notrequired and grants a database user sufficient authorization for data replication for a non-SAP source system.

replication settings like modifying target table structures, specifying PERFORMANCE OPTIMIZATION settings that defines TRANSFORMATION RULES.

replication settings like modifying target table structures, specifying performance optimization settings that defines transformation rules.

Latency is the LENGTH of time to REPLICATE DATA (a table entry) from the SOURCE system to the TARGET system.

Latency is the length of time to replicate data (a table entry) from the source system to the target system.

Transformation rule is a rule specified in the ADVANCED Replication settings TRANSACTION for source TABLES such a way that the data is transformed during the replication process. 

For EXAMPLE: one can specify rule to Convert fields, Fill empty fields and SKIP records

Transformation rule is a rule specified in the Advanced Replication settings transaction for source tables such a way that the data is transformed during the replication process. 

For example: one can specify rule to Convert fields, Fill empty fields and Skip records

PRIVATE ATTRIBUTES are the attributes USED INSIDE a modeling VIEWS and cannot be used outside the view.These are used in a modeling view to customize the behavior of an attribute for only that view.

Private attributes are the attributes used inside a modeling views and cannot be used outside the view.These are used in a modeling view to customize the behavior of an attribute for only that view.

Theory wise at least very well. Most mid-size workloads - 2TB of in-memory storage is equivalent to 5-20TB of Oracle storage can be run by the biggest single server HANA hardware. HANA works in a way that means it is possible to chain multiple systems together which means that scalability has thus-far been determined by the size of customers' wallets. Whilst SAP talk up "BIG Data" quite a LOT, HANA currently only scales to the small-end of Big Data referring to the kind of huge datasets that FaceBook or GOOGLE have to store - not Terabytes, but rather PETABYTES.

Theory wise at least very well. Most mid-size workloads - 2TB of in-memory storage is equivalent to 5-20TB of Oracle storage can be run by the biggest single server HANA hardware. HANA works in a way that means it is possible to chain multiple systems together which means that scalability has thus-far been determined by the size of customers' wallets. Whilst SAP talk up "Big Data" quite a lot, HANA currently only scales to the small-end of Big Data referring to the kind of huge datasets that FaceBook or Google have to store - not Terabytes, but rather Petabytes.

A shared network attached and varies from vendor to vendor and is called the storage. Here both regular magnetic disks and SSD storage can be USED for the backup of the database (HANA runs in memory remember, so disk storage is just for backup, and later, for data ageing). If the operator require 2X storage that you have RAM, which is 2x the database size - i.e. storage size = 4x database size. Anyways in most cases there is additional ultra-high speed SSD storage for LOG files.

A shared network attached and varies from vendor to vendor and is called the storage. Here both regular magnetic disks and SSD storage can be used for the backup of the database (HANA runs in memory remember, so disk storage is just for backup, and later, for data ageing). If the operator require 2x storage that you have RAM, which is 2x the database size - i.e. storage size = 4x database size. Anyways in most cases there is additional ultra-high speed SSD storage for log files.

If Sybase Replication Server (SRS) for near real-time data is used then the licensing still (SAP have license deals pending) needs to CHECKED. If DB2 is RUN then its fine but with Oracle and Microsoft SQL Server there are some license challenges. So if license is bought through SAP, because you may have a limited license that does not allow EXTRACTION

If Sybase Replication Server (SRS) for near real-time data is used then the licensing still (SAP have license deals pending) needs to checked. If DB2 is run then its fine but with Oracle and Microsoft SQL Server there are some license challenges. So if license is bought through SAP, because you may have a limited license that does not allow extraction

SRS has additional RESTRICTIONS which are worth to be understood. It only REPLICATES UNICODE data and does not SUPPORT IBM DB2 compress TABLES.

SRS has additional restrictions which are worth to be understood. It only replicates Unicode data and does not support IBM DB2 compress tables.

Yes it is possible to specify type of data LOAD and REPLICATION in SAP HANA, it can be either in real time, or SCHEDULED by time or by INTERVAL.

Yes it is possible to specify type of data load and replication in SAP HANA, it can be either in real time, or scheduled by time or by interval.

Each job occupies 1 BGD work processes in SLT REPLICATION server. For each configuration, the PARAMETER Data Transfer Jobs restricts the maximum number of data load job for each mass transfer ID (MT_ID).

A mass transfer ID requires at least 4 background jobs to be available:

One master job

One master controller job

At least one data load job

One ADDITIONAL job either for migration/access plan calculation/to change configuration SETTINGS in "Configuration and Monitoring Dashboard".

Each job occupies 1 BGD work processes in SLT replication server. For each configuration, the parameter Data Transfer Jobs restricts the maximum number of data load job for each mass transfer ID (MT_ID).

A mass transfer ID requires at least 4 background jobs to be available:

One master job

One master controller job

At least one data load job

One additional job either for migration/access plan calculation/to change configuration settings in "Configuration and Monitoring Dashboard".