I'm testing out a package procedure that uses a fairly complicated cursor. If I manually run the cursor's query in an SQL window, it takes 3 seconds to run. But when I'm using a test window, it's taking forever for it to pull the cursor (I have yet to find out exactly how long, I've let it run as long as 25 minutes and then killed the test session).
I encountered this same issue with another complicated cursor query recently and found that when the process was run from a shell script, the whole thing took less than two minutes. When it was run from a Test window it took about 18 minutes. So there's something inherently slow about the Test window's ability to handle complicated cursor queries.
Any idea why the Test process in PL/SQL Developer is so slow? Are there any settings I can adjust to address this?
I encountered this same issue with another complicated cursor query recently and found that when the process was run from a shell script, the whole thing took less than two minutes. When it was run from a Test window it took about 18 minutes. So there's something inherently slow about the Test window's ability to handle complicated cursor queries.
Any idea why the Test process in PL/SQL Developer is so slow? Are there any settings I can adjust to address this?
