What types of user-defined functions are supported by SAP HANA? Note: There are 2 correct answers to this question.
Correct Answer: B,D
Question 32
Which services can you use in SAP HANA, express edition? There are 3 correct answers to this question.
Correct Answer: B,C,E
SAP HANA, express edition is a streamlined version of SAP HANA that can run on laptops and other resource-constrained hosts, such as a cloud-hosted virtual machine. SAP HANA, express edition is free to use for in-memory databases up to 32 GB of RAM. SAP HANA, express edition supports the following services: * Text analytics: This service allows you to analyze unstructured text data, such as documents, emails, tweets, and blogs, using natural language processing techniques. You can use text analytics to extract entities, facts, sentiments, and keywords from text data, and to perform linguistic analysis, such as tokenization, lemmatization, and part-of-speech tagging. * Multi-core and parallelization: This service allows you to leverage the multi-core architecture and parallel processing capabilities of SAP HANA to optimize the performance of data-intensive operations, such as queries, calculations, and transformations. You can use multi-core and parallelization to distribute the workload across multiple CPU cores and threads, and to execute tasks in parallel or in batches. * Columnar OLTP and OLAP: This service allows you to store and process data in a columnar format, which enables faster data compression, aggregation, and analysis. You can use columnar OLTP and OLAP to support both transactional and analytical workloads on the same data set, without requiring data duplication or pre-aggregation. The other options are not correct because: * A. Dynamic tiering: This service allows you to extend the SAP HANA in-memory database with disk-based tables that can store large volumes of warm or cold data. You can use dynamic tiering to reduce the memory footprint and cost of SAP HANA, while still maintaining query access to the disk-based data. However, dynamic tiering is not supported by SAP HANA, express edition, as it requires additional hardware and software components. * D. System replication: This service allows you to create and maintain one or more secondary SAP HANA systems that are identical copies of a primary SAP HANA system. You can use system replication to ensure high availability and disaster recovery of SAP HANA, as the secondary systems can take over the role of the primary system in case of a failure. However, system replication is not supported by SAP HANA, express edition, as it requires additional licenses and configuration. References: * SAP HANA, express edition, Overview * SAP HANA, express edition, Features * SAP HANA, express edition, FAQ
Question 33
Which of the following can be used when implementing transaction management logic in SQLScript using savepoints? Note: There are 3 correct answers to this question.
Correct Answer: A,B,C
According to the SAP HANA SQLScript Reference, the following statements can be used when implementing transaction management logic in SQLScript using savepoints: * Savepoint: Creates a savepoint with a specified name within the current transaction. A savepoint marks a point in the transaction that can be rolled back to without affecting the rest of the transaction. For example, SAVEPOINT sp1; * Rollback to savepoint: Rolls back the current transaction to the specified savepoint. All changes made after the savepoint are undone, but the transaction remains active. For example, ROLLBACK TO SAVEPOINT sp1; * Release savepoint: Releases the specified savepoint and all subsequent savepoints. The released savepoints are no longer valid and cannot be rolled back to. For example, RELEASE SAVEPOINT sp1; The other options are incorrect, because: * Reverse savepoint is not a valid statement in SQLScript. There is no such statement in the SAP HANA * SQLScript Reference. * Alter system savepoint is not a statement that can be used in SQLScript, but a statement that can be used in SQL. It triggers a savepoint operation for the entire database system, not for a specific transaction. It is used for administrative purposes, such as backup and recovery, not for transaction management logic. References: SAP HANA SQLScript Reference, Chapter 6, Section 6.4.2, page 2111.
Question 34
You need to access a remote database table object within your HDB module in a Multi-target application project. In SAP HANA extended application services, advanced model (XS advanced) a user-provided service was created to access the external schema. The service is already declared in the Multi-target application project YAML file. Which activities do you perform?
Correct Answer: C,D,E
To access a remote database table object within your HDB module in a Multi-target application project, you need to perform the following activities: * Create/update the .hdbgrants file providing authorizations for the remote schema. This file defines the privileges that are granted to the HDI container technical users for accessing the remote schema. You need to specify the user-provided service name, the schema name, and the privileges, such as SELECT, INSERT, UPDATE, DELETE, EXECUTE, etc. You can also use the wildcard character (*) to grant privileges on all objects in the remote schema. * Create a synonym for the remote table object. A synonym is a database object that provides an alternative name for another database object, such as a table, view, or procedure. You can use synonyms to simplify the access to remote objects by avoiding the need to specify the full qualified name. You can create a synonym in your HDB module by using the .hdbsynonym file, where you specify the target object name, the target object schema, and the user-provided service name. * Create a view that refers to the table. A view is a database object that defines a logical table based on the result set of a SQL query. You can use views to access data from one or more tables, including remote tables, by applying filters, joins, aggregations, calculations, etc. You can create a view in your HDB module by using the .hdbview file, where you specify the SQL query that references the synonym of the remote table object. The other options are incorrect because you do not need to create a view that refers to a synonym, nor create a synonym that refers to a view. These are redundant steps that do not add any value to the access of the remote table object. References: * Accessing Remote Data - SAP Help Portal * Granting Privileges on Remote Schemas - SAP Help Portal * Creating Synonyms - SAP Help Portal * Creating Views - SAP Help Portal
Question 35
After reviewing the SQL Analyzer results, which of the following would you consider for optimizing the performance? There are 2 correct answers to this question.
