Exporting data execute again

Toad for Oracle - Beta
1

Hi, i am facing issue from 25.2 and still in 25.3 that exporting data from grid runs the query again instead of just getting down to the end of result set and export the data as it used to be.

already the query maybe took 2 minutes so we need just to export data without execute teh query again.

Thanks

2

here's what's happening:

  1. The query is tied to a grid, which means it is in bi-directional mode, which means we have to keep rows in memory as you scroll past them as well as do some processing to keep the grid in sync.
  2. You have not scrolled to the end of the dataset in the grid, so the number of rows to be retrieved is not known by Toad, so Toad doesn't know if it has enough memory to hold all or the rows.
  3. To prevent the chance of running out of memory while exporting your dataset, Toad runs the query in a uni-directional mode. This allows Toad to free up memory from fetched rows after they are exported. Additionally, this query is not attached to a grid, which means we can scroll faster through it.

To override this behavior, and make Toad NOT re-run the query (but export more slowly, with the chance of running out of memory if there are too many rows), check this box:

image
image450×710 19.2 KB

3

Thanks, now clear,

but for long queries that took maybe 30 minutes but have small records count then re-execute this will be annoying , also to get all records which will let results delayed , i don’t if something in between can be managed.

thanks , it is clear for me now.

4

Yes, I know waiting that long is not ideal, but it's better than Toad crashing and then you run out of memory.

If you CTRL+END on the grid to scroll to the end before exporting, then Toad will check the box when the window opens. Toad leaves it unchecked when you haven't made it to the end of the data.

If you forget (or don't want to) CTRL+END, just remember to check the box manually.

1 Like