PLSQL_COMPILER_FLAGS and PLSQL_CODE_TYPE

Question

Why is the sql developer using plsql_compiler_flags parameter instead of plsql_code_type parameter for the debugger since the former has been deprecated?

Answer 1

Hi Ranit,
Changing to NATIVE compilation only affects PLSQL code, it wont improve performance for SQL.
You can usually speed up PL/SQL units by compiling them into native code (processor-dependent system code), which is stored in the SYSTEM tablespace.You can natively compile any PL/SQL unit of any type, including those that Oracle Database supplies. Natively compiled program units work in all server environments, including shared server configuration (formerly called "multithreaded server") and Oracle Real Application Clusters (Oracle RAC). On most platforms, PL/SQL native compilation requires no special set-up or maintenance. On some platforms, the DBA might want to do some optional configuration.
Without native compilation, the PL/SQL statements in a PL/SQL unit are compiled into an intermediate form, system code, which is stored in the catalog and interpreted at run time.
With PL/SQL native compilation, the PL/SQL statements in a PL/SQL unit are compiled into native code and stored in the catalog. The native code need not be interpreted at run time, so it runs faster
Because native compilation applies only to PL/SQL statements, a PL/SQL unit that uses only SQL statements might not run faster when natively compiled, but it does run at least as fast as the corresponding interpreted code. The compiled code and the interpreted code make the same library calls, so their action is the same.
Hope it clears your doubts.