Newly Released SAP C_HANADEV_18 Exam PDF

 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.

To prevent changes to existing line items of the sap.test::myTable table, you can use the OData service that specifies the update authorization as no-authorization for the table. This means that the OData service does not allow any update operations on the table, such as PUT, PATCH, or MERGE. The option A shows the code snippet that defines the OData service with this restriction. The other options do not have the update no-authorization clause for the table, and therefore, they do not prevent changes to the existing line items. References: OData Service Authorization, OData Security Considerations.

The SAP Web IDE for SAP HANA graphical editor for Core Data Services (CDS) data models allows you to specify the following elements12:

• Entity: An entity is a CDS artifact that defines a data structure with attributes, keys, and associations. An entity can be mapped to a database table or view, or it can be used as a source for another entity or a calculation view. You can create an entity by dragging the entity icon from the palette to the canvas, and then defining its properties and attributes in the properties panel.
• Context: A context is a CDS artifact that defines a namespace for other CDS artifacts, such as entities, views, types, or associations. A context can be used to organize and group related CDS artifacts, and to avoid name conflicts. You can create a context by dragging the context icon from the palette to the canvas, and then defining its name and description in the properties panel. You can also add other CDS artifacts to the context by dragging them from the project explorer or the palette to the context node in the canvas.
• Association: An association is a CDS artifact that defines a relationship between two entities, based on a join condition. An association can be used to navigate from one entity to another, and to filter, aggregate, or project data from the target entity. You can create an association by dragging the association icon from the palette to the canvas, and then connecting it to the source and target entities. You can also define the cardinality, join condition, and exposed attributes of the association in the properties panel.

The other options are not correct because they are not elements that can be specified with the SAP Web IDE for SAP HANA graphical editor for CDS data models. A synonym is a database object that provides an alternative name for another database object, such as a table, view, or procedure. A synonym is not a CDS artifact, and it cannot be created or edited with the graphical editor. A procedure is a database object that contains a set of SQL statements that perform a specific task. A procedure can be created or edited with the SQL editor, but not with the graphical editor. A procedure can also be exposed as a CDS artifact, but it cannot be specified with the graphical editor. References:

• SAP HANA Platform, SAP HANA Modeling Guide for SAP HANA Web Workbench, Core Data Services
• SAP HANA Platform, SAP HANA Developer Guide for SAP HANA Web IDE, Developing Core Data Services Models, Using the Graphical Editor

 To create a graphical representation of an individual SQL statement, you can use the Plan trace. The Plan trace is a tool that allows you to generate and visualize the execution plan of an SQL statement, with estimated or actual performance information for each operator. The Plan trace can help you understand and analyze the query optimization and execution process, and identify potential performance bottlenecks or improvement opportunities12.

The other options, Expensive statements trace, Performance trace, and SQL trace, are not tools that can create a graphical representation of an individual SQL statement. The Expensive statements trace is a tool that records the SQL statements that exceed a certain threshold of resource consumption, such as CPU time, memory, or disk reads. The Expensive statements trace can help you identify the most resource-intensive queries in the system, but it does not provide a graphical view of the execution plan3. The Performance trace is a tool that records the performance statistics of the database operations, such as SQL statements, transactions, procedures, or triggers. The Performance trace can help you measure and compare the performance of different database operations, but it does not provide a graphical view of the execution plan either. The SQL trace is a tool that captures every SQL statement that enters the database at the session layer. The SQL trace can help you monitor and troubleshoot the SQL statements that are executed in the database, but it does not provide a graphical view of the execution plan either. References: 1: Plan Trace | SAP Help Portal 2: Analyzing SQL Execution with the Plan Visualizer | SAP Help Portal 3: Expensive Statements Trace | SAP Help Portal : [Performance Trace | SAP Help Portal] : [SQL Trace | SAP Help Portal]