Hana Questions (30 question)

1)What is a workspace?

The place where you work on project-related objects is called a repository workspace.

2) What is a package and its types? (structural/non-structural)

package is used to group together related content objects in SAP HANA studio.  By default it creates non-structural:

1) Structural: package only contains sub packages.  It cannot contain repository objects.
2)  non structural: package contains both repository objects and sub packages

3) What are the default packages delivered with the repository?

SAP, system-local, system-local generated, system-local.private

4) What can be the max. length of a package name?

190 characters including dots

5) What are package privileges?

REPO.READ
REPO.EDIT_NATIVE_OBJECTS
REPO.ACTIVATE_NATIVE_OBJECTS
REPO.MAINTAIN_NATIVE_PACKAGES


6)REPO.READ

Read access to the selected package and design time objects(both native and imported)

7)REPO.EDIT_NATIVE_OBJECTS

Authorization to modify design-time objects in packages originating in the system the user is working in.

8) REPO.ACTIVATE_NATIVE_OBJECTS(activate/reactivate)

Authorization to activate/reactivate design-time objects in package originating in the system the user is working in

9) REPO.MAINTAIN_NATIVE-PACKAGES(update/delete)

Authorization to update or delete native packages or create sub-packages of packages originating in the system in which the user is working.

10) How many objects is uniquely identified in the repository?

Each object is uniquely identified by the combination of package name, object name, and object type.

11)  What are the two developer roles in HANA SPS05?

Modeler and Application programmer

12) Modeler

concerned with the definition of model and schemas used in the SAP HANA, the specification and defintion of tables, views, primary keys, indexes, partitions and inter-relationships of the data, designing and defining authorization and access control through specification of privileges, roles, and users and generally uses the perspective "Administration Console" and "Modeler"

13) Application Programmer

Concerned with building SAP HANA applications which are designed based on MVC architecture and generally uses the perspective "SAP HANA development"

14)  What is SAP XS (extended-application-service)?

SAP HANA XS provides end-to-end support for web-based applications

15) What are development objects?

The building blocks of SAP HANA applications are called development objects.

16)  What is a repository?

The HANA repository is a storage system for development objects and is built into SAP HANA.  The repository supports Version Control, Transport, and sharing objects between multiple developers.  We can add objects to the repository, update the objects, publish the objects, and compile these objects into run-time objects.

17) What are the different perspectives available in HANA?

Modeler: used for creating various types of views and analytical privileges.

SAP HANA development: used for programming applications for creating development objects to access or update data models such as Server side Java script or HTML files.  

Administration: Used to monitor the system and change settings.

Debug:  used to debug such as SQLScript or server-side javascript (.xsjs files)

18) Before starting development work in SAP HANA studio, what are the roles a user should have on SAP HANA server?

Modeling, content_admin

19)  What is a Delivery Unit?

Delivery Unit( DU ) is a container used by the Life Cycle Manager (LCM) to transport repository objects between the SAP HANA systems.  

20)  What are Transformation Rules (Data trans.during the repl process)?

A rule specified in the advanced replication settings transaction for source tables such that data is transformed during the replication process.  i.e. you can specify rule to convert fields, fill empty fields, skip records.

21)  What happens when you set-up a new configuration? (GUID and MT)?

The database connection is automatically created along with GUID and Mass Transfer (MT_ID)

Schema GUID ensures that configuration with the same schema name can be created.
mt_id is used in the naming of SLT jobs and the system can uniquely identify a schema

22)  what factors (4) influence the change/increase the number of jobs? (configurations, load/repl, initial, latency)?

1) number of configurations managed by the SLT replication server
2)  Number of tables to be loaded/replicated for each configuration
3) expected speed of initial load
4) Expected replication latency time.  As a rule of thumb, one BDG job should be used for each 10 tables in replication to achieve acceptable latency times.

23)  When to change the number of data Transfer jobs? (Latency, resources, complete)

1)  If the speed of the initial load/replication latency time is not satisfactory
2)  If SLT replication server has more resources than initially available, we can increase the number of data transfer and/or initial load jobs
3)  After the completion of the initial load, we may want to reduce the number of initial load jobs.


24)  What the jobs involved in replication process? (5) MM DAM

1) Master job (IUUC_Monitor_<MT_ID>)
2) Master Controller Job (IUUC_REPLIC_CNTR><MT_ID>)
3) Data Load Job(DTL_MT_DATA_LOAD_<MT_ID><2digits>)
4) Migration Object Definition Job (IUUC_DEF_MIG_OBJ<2digits>)
5) Access Plan calculation Job(ACC_PLAN_CALC_<MT_ID>_<2digits>)

25) What is the relation between the number of data transfer jobs in the configuration settings and the available BGD work processes?

Each job occupies 1 BGD work processes in SLT replication server.  For each configuration, the parameter Data Transfer Jobs restricts the max 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 A'Configuration and Monitoring a Dashboard'

26)  If you set the parameter "data transfer jobs" to 04 in a configuration "SCHEMA1", a mass transfer ID 001 is assigned.  Then what jobs should be in the system?

1 Master Job ( IUUC_MONITOR_SCHEMA1)
1 MASTER CONTROLLER JOB (IUUC_REPL_CNTR_001_0001)
At most 4 parallel jobs for MT_ID 001
(DTL_MT_DATA_LOAD_001_/1/-01/-03/-05)

Performance.  It lots of tables are selected for load/replication at the same time, it may happen that there are not enough background jobs available to start the load procedure for all tables immediately.  In this case you can increase the number of initial load jobs, otherwise tables will be handled sequentially.  

For tables with large volumes of data, you can use the transaction 'Advanced Replication Settings (IUUC_REPL_CONT)" to further optimize the load and replication procedure for dedicated tables.

27)  What happens after the SLT replication is over?

The SLT replication server creates 1 user, 4 roles, 2 stored procedures and 8 tables.
1 User
1 privilege
4 Roles
<Replication Schema>_DATA_PROV
<REPLICATION_SCHEMA>_POWER_USER
<REPLICATION_SCHEMA>_USER_ADMIN
<REPLICATION_SCHEMA>_SELECT
2 STORED PROCEDURES
RS_GRANT_ACCESS, RS_REEVOKE_ACCESS
8 TABLES

28)  What are the different replication scenarios?

Load, Replicate, Stop, Suspend, and Resume

a) load

Starts an initial load of replication data from the source system.  The procedure is a one-time event after it is completed, further changes to the source system database will not be replicated.

For the initial load procedure, neither database triggers nor logging tables are created in teh source system.  Default settings use reading type 3 with up to 3 background jobs in parallel to load tables in parallel or subsequently into the HANA system.

b)replicate

combines an intial load procedure and the subsequent replication procedures(real time or scheduled)

Before the initial load procedure will start, database trigger and related logging tables are created for each table in the source system as well as in SLT replication server.

c) Stop Replication (triggers)

Stop any current load or replication process of a table; removes the database trigge and related logging table completely.  Only use the function if you do want to continue a selected table otherwise you must initially load the table again to ensure data consistency.


d) Suspend

Pause a table from a running replication.  The database trigger will not be deleted from the source system.  

e) Resume

Restarts the application for a suspended table.  The previous suspended replication will be resumed(no new initial load required)


28)  What happens if the replication is suspended for along period of time or system outage of SLT or HANA system?

The size of the logging table increases.

29)  What is an analytic view?

Analytic views are used to model data that includes measures.  In case of multiple tables, measures must originate from only one of these tables (central table).  you can model columns, calculated columns, restricted columns, variables, and input parameters.

30)  How do you fine tune attributes of analytic views?  (6 types: restrictions, drill, hidden, aggregation, currency)

1)  Can apply fitler to restrict values
2)  Can be defined as hidden so that they can be processed, but not visible to end users
3) Can be defined as key attributes and used when joining multiple tables
4) can be further drilled down by "drill down enable" property( you can disable this behavior for selected attributes)
5)  You can model aggregation type of measures
6) you can model currency and unit of measure.

31) Can we include attribute views in Analytic view definition?

Yes

32)