C_HAMOD_2404 Practice Questions

If Table B is not pruned in a referential join, the possible issues could be:

C.  

The Keep flag is activated for the Customer column: This prevents pruning by forcing the inclusion of the column in query execution.

D.  

Integrity constraint is set to RIGHT: This setting implies that Table B data must always be considered in the join, disabling pruning.

Pruning depends on join conditions and flags; ensuring no unnecessary constraints is essential for proper optimization.

When creating a calculation view that accesses a table in an external schema:

A.  

Synonym: Synonyms act as aliases to access external schema objects. They are required to integrate external tables into the calculation view.

D.  

Authorization: You need appropriate schema authorizations to access the external table through the synonym.

A remote source (B) is used for accessing remote systems, and an SQL view (C) is not necessary for this scenario.

Performance Analysis modein SAP HANA calculation views provides insights into:

C.  

Information about join cardinality: It identifies whether joins are correctly defined and optimally used.

D.  

Joins that are defined on calculated columns: It highlights joins involving calculated columns, which can have significant performance implications.

Usage statistics (A) and memory consumption (B) are not direct outputs of Performance Analysis mode but may be derived from other tools or metrics.

Table partitioning in SAP HANA is used to enhance performance and scalability. The main reasons are:

B.  

To overcome the 2 billion record limit: Partitioning allows the table to handle more than the 2 billion records that are the limit for non-partitioned tables.

D.  

To improve query performance when accessing large column tables: Partitioning splits the table into manageable parts, allowing parallel processing and improving query performance for large datasets.