Query execution timer and status indicator (Red Stop Sign) show the query is still running even after full data is returned. (4378691)

Query execution timer and status indicator (Red Stop Sign) show the query is still running even after full data is returned.

There are a few scenarios for this issue. See below for details of each including resolutions:

1. When Editor’s fetch limit setting matches the number of retrieved rows. Example: The fetch limit in Toad is set to 1000 rows. A query is executed with FETCH FIRST 1000 ROWS ONLY or any query that returns exactly 1000 rows. Toad loads all 1000 rows but does not reset the Execute button. It remains in a running state (red stop sign). Cause: Toad does not recognize that the execution is complete. The Execute button stays red as if the query is still running making users think Toad is still processing data when it is actually finished.
   
   
2. When “Select *” with a lower fetch limit setting is executed and user scrolls through data set. Example: A “SELECT * FROM TABLE” query is executed. The fetch limit in Editor is set lower than the total number of rows (e.g., Fetch 50). When query is executed with a lower fetch limit, and the fetch limit is set lower than the total number of rows (e.g., Fetch 50 rows) then only 50 rows are initially loaded. However, as the user scrolls in the results grid, Toad fetches more rows dynamically (in this case 50 by 50 will be loaded in the results when scrolling).  The Execute button remains in a running state (red) until all rows are fetched. Cause: The Execute button should remain red until all rows are fetched, since Toad is still retrieving data as the user scrolls.
   
   
3. When “Select *”  with a lower fetch limit is executed and user scrolls through the data until all rows are fetched. Example: A “SELECT * FROM TABLE” query is executed with a low fetch limit (e.g., Fetch 50). The user scrolls in the results grid until all rows are fully retrieved (e.g., "Record 215 of 215"). Even though all rows have been fetched, the Execute button remains in a running state (red), and Background Processes still shows the query as active. 

   This occurs even after manually loading all data by scrolling, meaning the button never resets, even when there are no more records left to fetch." Add at the end of Cause section - "This happens because Toad does not validate whether additional data actually exists when using scroll-based fetching. Instead, it assumes more data might be available even when the record count confirms that all rows are loaded.

   Cause: Toad does not recognize query completion and leaves the Execute button in a running state. Background Processes incorrectly indicates that the query is still active, misleading the user.

Case #1:
Resolution: Waiting for fix in the future release of Toad. Change log # ID IMTDS-3172

Workaround: Manually stop execution or close SQL Editor.

Case #2:

This is expected behavior and Toad is designed to work with dynamic fetching.

Case #3:

Resolution: Issue is currently under investigation for potential defect

Workaround: 1) Manually stop execution or close SQL Editor. 2) Increase the fetch limit to exceed the expected number of rows. For example, if the dataset contains 215 rows, setting the fetch limit to 500 will ensure all data is loaded at once, preventing the Execute button from getting stuck in a running state.

The Editor fetch settings can be controlled from Tools | Options | Database | General window