• May 18, 2014
• in PLSQL, performance
• 4 min read

PL/SQL performance freak series - function/procedure parameters overhead

When writing a PL/SQL code, I usually use following strategy:

• If the code that I'm calling is returning a calculated value, it should be a function.
• If the code that I'm calling is doing some DB operations and is not returning a value, it should be a procedure.

There are however some situations, when I tend to break the rule, and this is due to performance.