Why there is the difference in Oracle PL/SQL response time within SQL Developer vs. SQL Plus?

The easiest experiment to make is changing the "SQL Array Fetch Size" in SQL Developer, which defaults to 50. If you see results from bumping it to 500, there's the answer.

The easiest experiment to make is changing the "SQL Array Fetch Size" in SQL Developer, which defaults to 50. If you see results from bumping it to 500, there's the answer. Interestingly, the default for the equivalent SQL*Plus parameter is only 15, but as APC said, SQL*Plus has the advantage of being native.

If changing "SQL Array Fetch Size" does not do anything, the next thing to look at is JDBC settings, which SQL Developer uses and SQL*Plus does not.

In addition to the good answers before mine... SQL*PLus sends the data straight back to the screen as soon as the first rows are returned whereas SQL Developer has to find the size of the resultset to return in advance of displaying records. This might explain why there is a delay for SQL Developer especially if the resultset is large or takes a long time to fully return (e.g. If the execution path is complicated).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.