A.Switch the storage type of you custom database tables to column store and use the database utility (SE14) to perform the database table conversion.

B.Activate your ABAP custom coding, which was deactivated before the database migration, using U transaction SFW5.

C.Perform regular performance scans on the ABAP coding delivered by SAP as part of your development process.

D.Perform regular performance scans on your ABAP custom coding as part of the development process.

A.It schedules ABAP programs to monitor and log all database accesses.

B.It can be active in a production system with minimal performance overhead.

C.It displays the database execution plan for all SQL statements.

D.It collects monitoring data asynchronously without additional database interaction.

A.Use the static method use_features of class cl_abap_dbfeatures.

B.Check the value of the ABAP system field sy-cdsfeatures.

C.Check the Open SQL statement in the Explain SQL Statement transaction (SDBE).

D.Perform a static code check using the FUNCTIONAL_DB variant.

A.Join Engine

B.OLAP Engine

C.Calc Engine

D.SQL Engine

A.Shared file systems for only one server

B.Services-Name and index server on all nodes

C.Active clusters for all servers

D.High availability configuration