SAP® MaxDB - SQL Optimizer
This section gives detailed information about the SAP MaxDB SQL Optimizer.
SQL statements describe the content criteria, which the data that has to be accessed has to meet. But it does not describe how this data is to be accessed.
Each relational operation can, in principle, be converted into different access operations. But these can lead to different runtimes, for example, depending on the amount of data. Hence the scope of functions and the performance of the optimizer are of utmost importance.
This section introduces you to the performance analysis terms of the SQL optimizer.This page deals with information about the purpose and aim of the SQL optimizer and gives an introduction to the topics Qualification, Search Area, Join.... This is where subjects such as cost or rule-based SQL optimizer and the special evaluation feature of SAP MaxDB are explained.This section explains SAP MaxDB optimization strategies.The execution plan shows which strategy the Optimizer has chosen for accessing the data requested by means of the SQL statement. Hence, it is well-suited to analyzing long-running SQL statements.The SQL optimizer usually determines the access path on the basis of the costs (cost-based SQL optimizer). To deactivate this mechanism, you can explicitly specify hints for an SQL statement, which force a certain access path. In this section you get detailed information about SAP MaxDB hints.
FAQ: MaxDB SQL Optimization