Query Results output very slow compared to TOAD

[HintonBR]

I have been using PL/SQL Dev for years now. Recently I moved to a new company that uses TOAD. I was going to begin the process of convincing them that PL/SQL Dev was the way to go, but ran into a major issue that I had never noticed before.

I run a query in TOAD that returns say 60000 records and it returns the data into the Grid in less than 10 seconds, but PL/SQL Dev takes minutes to finish populating the grid with the data.

When I was doing this in PL/SQL Dev I thought the query was merely slow and so I looked at speed enhancements - eventually I turned to a co-worker who ran it in TOAD and it returned in no time flat. The problem clearly lies with PL/SQL Dev fetching the results and populating them in the grid. I find it hard to believe that their is truly this much of a difference. If there is obviously there is no way I am going to be able to convince people that PL/SQL Dev is the way to go.

Anybody have any explanations?

Bryan

 

[Marco Kalter]

Are all 60,000 records fetched in both tools?

 

[rbrooker]

from experience, toad will fetch a certain number, and as you scroll down the grid, it fetches more records to fill in the display.

a good test would be to
run the query in both tools
in PLSD, press the "fetch all records" button
in TOAD, press ctrl-end

this will cause both tools to fetch ALL records at once.

 

[William Robertson]

How often would you want 60,000 rows on your desktop anyway?

 

[HintonBR]

Yes 60000 rows were fetched in both tools - In both PLSD and TOAD I hit the button that takes me to the last row.

As for why I want 60000 rows I want to time the query - and when TOAD can do it in 4 seconds an PLSD takes 10 minutes I really start to get perplexed

 

[p_m]

I suspect that when you move to the last row Toad binds only the last page of data to the grid. PL/SQL Developer may be binding all 60,00 rows to the grid?

 

[rbrooker]

that could be true, you could keep the "page down" button pressed in toad and make it skip through each record, that might make it take 10 minutes...

seems plsd is more honest than toad...

 

[ScottMattes]

I would test using the Test Window and opening a cursor.

Or, select count(*) from ( put your query here ).

The ways describe above are mainly testing the tools used.

 

[William Robertson]

> As for why I want 60000 rows I want to time the query

And now you have. It seems TOAD may have a rendering optimisation that PL/SQL Developer does not. I'm sure that is worth the extra $800 to somebody

If AA address this in the next release and make PL/SQL Dev faster than TOAD at this type of task, so what?