Tuesday, July 4, 2017

PLSQL Performance Tuning – Implicit VS Explicit Cursors

In this post, I tried to understand the difference what Implicit and explicit cursors can make on PLSQL performance. Which is better?

Here is the small demonstration to show “Implicit Cursors” are definitely better than Explicit cursors. As much as possible, it’s better to use Implicit Cursors.


The time consumed clearly shows that “Implicit Cursor” is a winner from Performance perspective. Here, the time difference is because of the number of lines of source code. As PLSQL is interpreted code, this number of lines makes a difference.   


Hope it helps!!

Tuesday, July 4, 2017 by Team search · 0

PLSQL Performance Tuning – NOT NULL Constraint

In this post, I tried to explain the importance of constraint “NOT NULL” from performance perspective.

From SQL Perspective:

  • It adds semantic meaning to your data model. You KNOW that the column will always contain a value.
  • It removes ambiguity.
  • The more information you give the database, the better the quality of the plans. Not null impacts the optimizer, query rewrite, even the queries you must type in to get the correct answer.
  • It improves Query Performance

 From PLSQL Perspective:  Its better to use “NOT NULL” has a slight edge towards performance. The below demonstration will explain the same.


  Hope it helps!!

by Team search · 0


The ideas, thoughts and concepts expressed here are my own. They, in no way reflect those of my employer or any other organization/client that I am associated. The articles presented doesn't imply to any particular organization or client and are meant only for knowledge Sharing purpose. The articles can't be reproduced or copied without the Owner's knowledge or permission.