openSAP Hanasql2 Week 1 All Slides

Week 1: Understanding SAP HANA SQLScript Optimizer
Unit 1: Course Introduction

Course introduction
Overview
▪ Weekly assignments / final exam Using the Optimizer for SQLScript Programming in SAP HANA
▪ Discussion forum
Week 1
▪ Use your own SAP HANA Understanding SAP HANA SQLScript Optimizer
system for practice
Week 2
SAP HANA SQLScript Supportability Features
Week 3 Investigating SQLScript Performance Caused by SQL
Final Exam
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Course introduction
Unit 1: Course introduction
Unit 2: SAP HANA SQLScript optimizer

▪ Learn how the SQLScript engine works, including SQLScript optimizer
▪ Learn how the SQLScript engine works with the SQL engine and SQL plan cache
Unit 3: SAP HANA SQLScript optimization rules – Part 1

▪ Learn four rules
Unit 4: SAP HANA SQLScript optimization rules – Part 2

▪ Familiarize yourself with four rules
▪ Be able to recognize original code after it has been optimized
Unit 5: SQLScript general analysis strategy

▪ Learn how to approach SQLScript performance issues

Course introduction
Week 2: SAP HANA SQLScript Supportability Features
Unit 1: SQLScript supportability
Unit 2: SQLScript supportability – SQL Trace

▪ Demo: collecting SQL Trace and checking the result
Unit 3: SQLScript supportability – Plan Profiler

▪ Demo: collecting Plan Profiler and checking the result
Unit 4: SQLScript supportability – M_ACTIVE_PROCEDURES

▪ Demo: collecting M_ACTIVE_PROCEDURES and checking the result
Unit 5: SQLScript supportability – EXPLAIN PLAN FOR CALL

▪ Demo: collecting EXPLAIN PLAN FOR CALL and checking the result
Unit 6: SQLScript supportability – Plan Visualizer

▪ Demo: using the new SQL analyzer tool
Course introduction
Week 3: Investigating SQLScript Performance Caused by SQL
Unit 1: INLINE feature
Unit 2: Case study 1 – Using the INLINE feature
Unit 3: BIND_AS_PARAMETER and BIND_AS_VALUE functions
Unit 4: Case study 2 – Using BIND_AS_VALUE
Unit 5: Using SQL hint in SQLScript
Unit 6: Pinning SQL hint for SQLScript

Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Unit 2: SAP HANA SQLScript Optimizer
SAP HANA SQLScript optimizer
Learning objectives
By the end of this week you will Using the Optimizer for SQLScript Programming in SAP HANA
understand
Week 1
▪ How SQLScript is executed
Understanding SAP HANA SQLScript Optimizer
▪ How SQLScript optimizer works
▪ The difference between SQLScript
optimizer and SQL optimizer
Week 2
▪ How SQLScript works with SQL plan SAP HANA SQLScript Supportability Features
cache
▪ General analysis strategy for SQLScript
Week 3
performance issues
Investigating SQLScript Performance Caused by SQL
Final Exam

What is SQLScript?
A programming language of SAP HANA CREATE PROCEDURE HELLO(IN P NVARCHAR(8))

AS BEGIN
SQLScript supports DECLARE V_NAME NVARCHAR(8) = :P;
▪ Imperative programming constructs IF :P = '' THEN
▪ Declarative SQL statements V_NAME = 'SAP HANA';
END IF;
SELECT 'HELLO, ' || :V_NAME FROM DUMMY;
END;
CALL HELLO('');

What is SQLScript?

AS BEGIN
END IF;
CREATE PROCEDURE statement
CALL statement END;
CALL HELLO('');

What is SQLScript?
Imperative programing constructs

AS BEGIN
END IF;
CALL statement END;
SQLScript procedure HELLO has imperative

programming constructs CALL HELLO('');

What is SQLScript?

AS BEGIN
END IF;
CALL statement END;

Declarative SQL statements
SQLScript procedure HELLO has imperative
programming constructs and a declarative CALL HELLO('');
SQL statement

CREATE PROCEDURE HELLO(IN P NVARCHAR(8))
How does the SQLScript engine work? AS BEGIN
DECLARE V_NAME NVARCHAR(8) = :P;
IF :P = '' THEN
V_NAME = 'SAP HANA';
When a user executes a SQLScript procedure, END IF;

the SQLScript engine does the following: END;
▪ Compilation
▪ Optimization CALL HELLO('');
▪ Execution
Compilation
Optimization
Execution

What is the SQLScript optimizer? AS BEGIN
IF :P = '' THEN

▪ Compilation
▪ Execution
Compilation
Optimization
Execution

SQLScript and SQL plan cache AS BEGIN
IF :P = '' THEN

▪ Compilation Plan
Cache
▪ Execution
Compilation
The SQLScript execution plan is cached in SQL
plan cache
Optimization
Execution

SQLScript and SQL plan cache AS BEGIN
IF :P = '' THEN

▪ Compilation Plan
Cache
▪ Execution
The SQLScript execution plan is cached in SQL Compilation

plan cache
Once cached, the cached execution plan is

used, skipping the compilation and optimization Optimization
phases
Execution

SQLScript optimizer and SQL optimizer AS BEGIN
IF :P = '' THEN
The SQLScript engine executes imperative END IF;

programming constructs END;
The SQLScript engine passes declarative SQL

statements to the SQL engine in the CALL HELLO('');
“Execution” phase
Compilation Compilation
Optimization Optimization
Execution Execution
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC SQLScript Engine SQL Engine 11
IF :P = '' THEN


statements to the SQL engine in the CALL HELLO(''); SELECT 'HELLO, ' ... FROM DUMMY;
Execution Execution
IF :P = '' THEN


statements to the SQL engine in the CALL HELLO(''); SELECT 'HELLO, ' ... FROM DUMMY;
The SQLScript engine reshapes SQL
statements during the “Optimization” phase,
before passing them to the SQL engine
stmt Optimization Optimization
stmt’
stmt”
Execution Execution
SQLScript and SQL plan cache
Plan Cache
1. The SQLScript execution plan for
CALL HELLO(‘’);
is inserted into the SQL plan cache.
CALL HELLO('');
Execution Execution
Plan Cache
CALL HELLO(‘’);
2. The SQLScript engine passes
CALL HELLO(''); SELECT 'HELLO, ' ... FROM DUMMY;
SELECT ‘HELLO, ’ … FROM DUMMY;
to the SQL engine.
3. The SQL query plan for
is inserted into the SQL plan cache too.
Execution Execution
Plan Cache
CALL HELLO(‘’);
CALL HELLO('');
to the SQL engine.
4. For the next CALL HELLO(‘’), the execution plan Optimization Optimization
is reused without the SQLScript
compilation/optimization phases.
Execution Execution
Plan Cache
CALL HELLO(‘’);
CALL HELLO(''); SELECT 'HELLO, ' ... FROM DUMMY;
to the SQL engine.
4. For the next CALL HELLO(‘’), the execution plan Optimization Optimization
is reused without the SQLScript
5. For the next SELECT ‘HELLO, ’ … FROM
DUMMY, the query plan is reused without the SQL Execution Execution
SAP HANA SQLScript Optimizer
Key takeaways
The SQLScript engine has three phases –

compilation, optimization and execution.
The SQLScript engine deals with imperative

programming constructs.

statements to the SQL engine in the “Execution”
phase.
The SQLScript optimizer reshapes SQL

statements during the “Optimization” phase.
The SQLScript execution plan is cached in the

SQL plan cache.

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 3: SAP HANA SQLScript Optimization Rules
– Part 1
SAP HANA SQLScript optimization rules – Part 1
Four rules of the SAP HANA SQLScript optimizer
Constant
propagation
Control flow Procedure

simplification flattening
SQL statement
inlining and
parallelization
Constant propagation
Evaluate the SQL expression and folding constant.

Propagate the value through the value chain.

Evaluate the SQL expression and folding constant. CREATE PROCEDURE HELLO(IN P NVARCHAR(8))
AS BEGIN
IF :P = '' THEN
When an empty string ‘’ is given as an input V_NAME = 'SAP HANA';
parameter of the SQLScript procedure HELLO, this
END IF;
constant value is used in compile time.
END;
CALL HELLO('');

Evaluate the SQL expression and folding constant. CREATE PROCEDURE HELLO( '' )
AS BEGIN
DECLARE V_NAME NVARCHAR(8) = '';
IF '' = '' THEN
When an empty string ‘’ is given as an input V_NAME = 'SAP HANA';
parameter of the SQLScript procedure HELLO, this
END IF;
constant value is used in compile time.
The SQLScript optimizer propagates the empty
END;
string ‘’ as a constant to all positions of variable P.
CALL HELLO('');

Procedure flattening
Unfold the body of the callee SQLScript into the

body of the caller SQLScript.

CREATE PROCEDURE WHO(OUT N NVARCHAR(8))
Unfold the body of the callee SQLScript into the AS BEGIN

body of the caller SQLScript. SELECT TOP 1 'SAP HANA' INTO N FROM DUMMY;
END;
The SQLScript procedure WHO is executed

inside the procedure HELLO.
AS BEGIN
DECLARE V_NAME NVARCHAR(8);
CALL WHO(V_NAME);
END;
CALL HELLO('');

CREATE PROCEDURE WHO(OUT N NVARCHAR(8))
Unfold the body of the callee SQLScript into the AS BEGIN

body of the caller SQLScript. SELECT TOP 1 'SAP HANA' INTO N FROM DUMMY;
END;
The SQLScript procedure WHO is executed

inside the procedure HELLO. Then the body of
the procedure WHO is unfolded instead of CALL AS BEGIN
WHO(). DECLARE V_NAME NVARCHAR(8);
SELECT TOP 1 'SAP HANA' INTO V_NAME FROM DUMMY;
END;
CALL HELLO('');

SQL statement inlining and parallelization
SQL statements with no dependency can be

executed in parallel.
SQL statements with dependency can be merged
into a single SQL statement.

SQL statements with no dependency can be CREATE PROCEDURE HELLO()

executed in parallel. AS BEGIN
SQL statements with dependency can be merged RESULT = SELECT 'HELLO' FROM DUMMY;
into a single SQL statement. SELECT * FROM DUMMY, :RESULT;
END;
The two SQL statements in the procedure HELLO

have dependency, since RESULT of the first
statement is used in the second one. CALL HELLO();

SQL statements with no dependency can be CREATE PROCEDURE HELLO()

executed in parallel. AS BEGIN
SQL statements with dependency can be merged WITH "_SYS_RESULT_2" AS (SELECT 'HELLO' FROM DUMMY)
into a single SQL statement. SELECT * FROM DUMMY, "_SYS_RESULT_2" "RESULT" ;
END;
The two SQL statements in the procedure HELLO

have dependency, since RESULT of the first
statement is used in the second one. These two CALL HELLO();
SQL statements can be combined by using a
“WITH” clause. This optimization is called the
“inlining” feature.

Control flow simplification
Dead-code elimination
▪ Statements, if it is guaranteed that their
generated results will never be used.
▪ Unreachable branches, if it is determined that the
conditions for branches are evaluated as false
after constant propagation.

Dead-code elimination CREATE PROCEDURE HELLO(IN P NVARCHAR(8))
▪ Statements, if it is guaranteed that their AS BEGIN

generated results will never be used. DECLARE V_NAME NVARCHAR(8) = :P;
▪ Unreachable branches, if it is determined that the IF :P = '' THEN

conditions for branches are evaluated as false V_NAME = 'SAP HANA';
after constant propagation. END IF;
END;
CALL HELLO('HI');

Dead-code elimination CREATE PROCEDURE HELLO( 'HI' )

generated results will never be used. DECLARE V_NAME NVARCHAR(8) = 'HI';
▪ Unreachable branches, if it is determined that the IF 'HI' = '' THEN

After constant propagation, it turned out that the END;
condition of the IF statement is always false
( ‘HI’ = ‘’ )
CALL HELLO('HI');

Dead-code elimination CREATE PROCEDURE HELLO( 'HI' )

generated results will never be used. DECLARE V_NAME NVARCHAR(8) = 'HI';
▪ Unreachable branches, if it is determined that the IF 'HI' = '' THEN

After constant propagation, it turned out that the END;
condition of the IF statement is always false
( ‘HI’ = ‘’ ), so this IF branch can be eliminated
before execution time.
CALL HELLO('HI');

Key takeaways
Four SQLScript optimization rules

▪ Constant propagation
▪ Procedure flattening
▪ SQL statement inlining and parallelization
▪ Control flow simplification

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 4: SAP HANA SQLScript Optimization Rules
– Part 2
Four rules of the SAP HANA SQLScript optimizer
Constant
propagation
Control flow Procedure

simplification flattening
SQL statement
inlining and
parallelization
When “CALL P1(‘TA’)” is executed
A base table and table type CREATE TABLE TAB1 (MATERIAL NVARCHAR(10), FABRIC_ID NVARCHAR(10));
INSERT INTO TAB1 VALUES ('ABC' , 'BI');
CREATE TYPE T_RESULT AS TABLE (MATERIAL NVARCHAR(10), FABRIC_ID NVARCHAR(10));
SQLScript procedure P2 CREATE PROCEDURE P2(IN F2 NVARCHAR(13), OUT T_RESULT TAB1)

AS BEGIN
DECLARE V_F_ID NVARCHAR(13);
IF :F2 = 'TA' THEN
V_F_ID = 'BI';
END IF;
T_TABLE = SELECT DISTINCT MATERIAL, FABRIC_ID FROM TAB1
WHERE :V_F_ID = '' OR :V_F_ID = FABRIC_ID;
T_RESULT = SELECT * FROM :T_TABLE ORDER BY MATERIAL;
END;
SQLScript procedure P1 CREATE PROCEDURE P1(IN F1 NVARCHAR(13))

AS BEGIN
CALL P2(:F1, :COMPOSITION);
SELECT * FROM :COMPOSITION ORDER BY MATERIAL;
END;

-- CREATE PROCEDURE P2(IN F2 NVARCHAR(13), OUT T_RESULT TAB1)

AS BEGIN
IF :F2 = 'TA' THEN
V_F_ID = 'BI';
END IF;
END;
-- CREATE PROCEDURE P1(IN F1 NVARCHAR(13))

AS BEGIN
END;


AS BEGIN
IF :F2 = 'TA' THEN
V_F_ID = 'BI';
END IF;
END;
-- CREATE PROCEDURE P1( 'TA' )

AS BEGIN
CALL P2('TA', :COMPOSITION);
END;


AS BEGIN
IF :F2 = 'TA' THEN
V_F_ID = 'BI';
END IF;
END;

AS BEGIN
END;

-- CREATE PROCEDURE P2( 'TA' , OUT T_RESULT TAB1)

AS BEGIN
IF 'TA'= 'TA' THEN
V_F_ID = 'BI';
END IF;
END;

AS BEGIN
END;

-- CREATE PROCEDURE P2( 'TA' , OUT T_RESULT TAB1)

AS BEGIN
IF 'TA'= 'TA' THEN
V_F_ID = 'BI';
END IF;
END;

AS BEGIN
END;


AS BEGIN
IF 'TA'= 'TA' THEN
V_F_ID = 'BI';
END IF;
SELECT * FROM :T_RESULT ORDER BY MATERIAL;
END;


AS BEGIN
IF 'TA'= 'TA' THEN
V_F_ID = 'BI';
END IF;
END;


AS BEGIN
V_F_ID = 'BI';

END;

Constant propagation, again!

AS BEGIN
V_F_ID = 'BI';

END;

Constant propagation, again!

AS BEGIN

WHERE 'BI' = '' OR 'BI' = FABRIC_ID;
END;


AS BEGIN

WHERE 'BI' = '' OR 'BI' = FABRIC_ID;
END;


AS BEGIN
WITH "_SYS_T_TABLE_2" AS
(SELECT DISTINCT MATERIAL, FABRIC_ID FROM TAB1
WHERE 'BI' = '' OR 'BI' = FABRIC_ID),
"_SYS_T_RESULT_1" AS
(SELECT * FROM "_SYS_T_TABLE_2" "T_TABLE"
ORDER BY MATERIAL)
SELECT * FROM "_SYS_T_RESULT_1" "COMPOSITION"
ORDER BY MATERIAL;
END;

Final output of the SQLScript optimizer
AS BEGIN
WITH "_SYS_T_TABLE_2" AS
(SELECT DISTINCT MATERIAL, FABRIC_ID FROM TAB1
WHERE 'BI' = '' OR 'BI' = FABRIC_ID),
"_SYS_T_RESULT_1" AS
(SELECT * FROM "_SYS_T_TABLE_2" "T_TABLE"
ORDER BY MATERIAL)
ORDER BY MATERIAL;
END;

Output of the SQLScript optimizer
Definition of SQLScript procedure P1 Actual running code of P1 by CALL P1(‘TA’)
CREATE PROCEDURE P2(IN F2 NVARCHAR(13), OUT T_RESULT TAB1)

AS BEGIN
IF :F2 = 'TA' THEN
V_F_ID = 'BI';
END IF;
END;
CREATE PROCEDURE P1(IN F1 NVARCHAR(13))

AS BEGIN
END;

Output of the SQLScript optimizer
Definition of SQLScript procedure P1 Actual running code of P1 by CALL P1(‘TA’)
CREATE PROCEDURE P2(IN F2 NVARCHAR(13), OUT T_RESULT TAB1)

AS BEGIN
IF :F2 = 'TA' THEN AS BEGIN
V_F_ID = 'BI'; WITH "_SYS_T_TABLE_2" AS
END IF; (SELECT DISTINCT MATERIAL, FABRIC_ID FROM TAB1
T_TABLE = SELECT DISTINCT MATERIAL, FABRIC_ID FROM TAB1 WHERE 'BI' = '' OR 'BI' = FABRIC_ID),
WHERE :V_F_ID = '' OR :V_F_ID = FABRIC_ID; "_SYS_T_RESULT_1" AS
T_RESULT = SELECT * FROM :T_TABLE ORDER BY MATERIAL; (SELECT * FROM "_SYS_T_TABLE_2" "T_TABLE"
END; ORDER BY MATERIAL)
CREATE PROCEDURE P1(IN F1 NVARCHAR(13)) ORDER BY MATERIAL;
AS BEGIN END;
END;

Key takeaways
The output of the SQLScript optimizer can be

very different with the code of a procedure
definition.
Recognizing the output result of SQLScript

optimization is the first step in investigating a
performance issue.

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 5: SQLScript General Analysis Strategy
SQLScript general analysis strategy
Find a dominant step AS BEGIN
......
In which step does the procedure take long

SELECT ...... ;
to execute? END;
CALL HELLO(''); SELECT ...... ;
Execution Execution
Find a dominant step – Imperative constructs CREATE PROCEDURE HELLO(IN P NVARCHAR(8))
AS BEGIN
......

SELECT ...... ;
to execute? END;
▪ Execution in SQLScript
(= anti-patterns of SQLScript code) CALL HELLO(''); SELECT ...... ;
– Row-based calculation
– Inefficient usage of imperative constructs
Execution Execution
Find a dominant step – Imperative constructs CREATE PROCEDURE HELLO(IN P NVARCHAR(8))
AS BEGIN
......
In which step does the procedure takes long

SELECT ...... ;
to execute? END;
▪ Execution inBest practices for anti-patterns are well documented in

SQLScript
▪ “Best
(= anti-patterns Practices for
of SQLScript Using SQLScript” in SAP HANA SQLScript Reference
code)
▪ “SQLScript Performance Guidelines” in SAP HANA Performance Guide for Developers
CALL HELLO(''); SELECT ...... ;
– InefficientPlease
usage of imperative
visit SAP Helpconstructs
Portal Compilation Compilation
Execution Execution
Find a dominant step – SQL statement CREATE PROCEDURE HELLO(IN P NVARCHAR(8))
AS BEGIN
......

SELECT ...... ;
to execute? END;
(= anti-patterns of SQLScript code) CALL HELLO(''); SELECT ...... ;
▪ Processing in SQL engine
– Long compilation of passed SQL statements
– Long execution of passed SQL statements
Execution Execution
Find a dominant step – SQL statement

to execute?
(= anti-patterns of SQLScript code )
▪ Processing in SQL engine
– Long compilation of passed SQL statements
– Long execution of passed SQL statements
The first step is to find the dominant SQL statement!

Key takeaways
The anti-pattern of SQLScript code should be

checked for performance issues caused by
imperative programming constructs.
The actual running SQL statements generated by

the SQLScript optimizer must be checked first for
performance issues caused by SQL statements.

Thank you.
open@sap.com
Follow all of SAP

warranty.

openSAP Hanasql2 Week 1 All Slides

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

openSAP Hanasql2 Week 1 All Slides

Uploaded by

Copyright:

Available Formats

Week 1: Understanding SAP HANA SQLScript Optimizer

Unit 1: Course Introduction

Week 3 Investigating SQLScript Performance Caused by SQL

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Unit 1: Course introduction

Unit 2: SAP HANA SQLScript optimizer

Unit 3: SAP HANA SQLScript optimization rules – Part 1

Unit 4: SAP HANA SQLScript optimization rules – Part 2

Unit 5: SQLScript general analysis strategy

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Unit 1: SQLScript supportability

Unit 2: SQLScript supportability – SQL Trace

Unit 3: SQLScript supportability – Plan Profiler

Unit 4: SQLScript supportability – M_ACTIVE_PROCEDURES

Unit 5: SQLScript supportability – EXPLAIN PLAN FOR CALL

Unit 6: SQLScript supportability – Plan Visualizer

Unit 1: INLINE feature

Unit 2: Case study 1 – Using the INLINE feature

Unit 3: BIND_AS_PARAMETER and BIND_AS_VALUE functions

Unit 4: Case study 2 – Using BIND_AS_VALUE

Unit 5: Using SQL hint in SQLScript

Unit 6: Pinning SQL hint for SQLScript

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

A programming language of SAP HANA CREATE PROCEDURE HELLO(IN P NVARCHAR(8))

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

A programming language of SAP HANA CREATE PROCEDURE HELLO(IN P NVARCHAR(8))

CALL statement END;

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

A programming language of SAP HANA CREATE PROCEDURE HELLO(IN P NVARCHAR(8))

CALL statement END;

SQLScript procedure HELLO has imperative

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

A programming language of SAP HANA CREATE PROCEDURE HELLO(IN P NVARCHAR(8))

CALL statement END;

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

When a user executes a SQLScript procedure, END IF;

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

When a user executes a SQLScript procedure, END IF;

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

When a user executes a SQLScript procedure, END IF;

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

When a user executes a SQLScript procedure, END IF;

The SQLScript execution plan is cached in SQL Compilation

Once cached, the cached execution plan is

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

The SQLScript engine executes imperative END IF;

The SQLScript engine passes declarative SQL

The SQLScript engine executes imperative END IF;

The SQLScript engine passes declarative SQL

The SQLScript engine executes imperative END IF;

The SQLScript engine passes declarative SQL

The SQLScript engine has three phases –

The SQLScript engine deals with imperative

The SQLScript engine passes declarative SQL

The SQLScript optimizer reshapes SQL

The SQLScript execution plan is cached in the

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

Control flow Procedure

Evaluate the SQL expression and folding constant.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3