Then there is no way to stop the results from coming back if you opt to get all results. This will be a big problem is hundreds of millions of rows are returned.
Finally, even if I do stop the result at 2000 rows, the SQL history shows 2000 rows, rather than the actual row count (like I get in SQL Assistant). I could use the row count button, but the count is not captured for future reference.
We had to change the result set processing to NOT get the row count during this flow. The problem was that when calling the JDBC driver to reposition to the last row (which is how you get the row count) it could take a very long time and was not interruptable, giving the appearance that things were hung. The menu option to get the row count on the table (right click, Teradata>Row Count) should return the row count for the table. Is there an exception that occurs?
The menu option is working as expected. It returns the row count for a table.
What seems to not be working is when I opt to get back all of the rows (beyone the set limit), I cannot stop the retrieval like I can in SQL Assistant.
Since this seems to be an effect from using JDBC (slow response time to get to the last row), it sounds like the process will not be changed. Will there be any chance that ODBC will be added as a connection option?
Without this, I assume I will have to build select count(*) wrappers around my SQL. Doable but inconvenient. IMO the new tool is missing valuable functionality that was available in the old tool.
Bill, Since this is a Java based tool, there are no plans to include ODBC. We struggled with taking out the functionality of getting the row count but the affect of the long delay for large result sets was causing more distress from users. We hope there will be a better alternative from the JDBC driver in the near future.
OK, this is a big problem for me as a developer. I'd rather wait for the last row and know what I'm getting, plus have that total show up in my SQL history.
Also, any chance for this to be addressed?: there is no way to stop the results from coming back if you opt to get all results. This will be a big problem is hundreds of millions of rows are returned.
Is this a generic JDBC restriction?
@dnoeth, Yes, this is standard behaviour of JDBC protocol. We are working with the JDBC Driver team for a non-standard solution.
@bmcclernan, The row count was previously obtained after the query had completed and returned a result set. Stopping or canceling at that point ('Yes' response to the question) would stop the retrieval of rows from the result set to be displayed in the result set viewer. But trying to cancel once you replied 'No' (keep going), you could not cancel. We have also fixed this issue in our next release so that you can cancel once it starts retrieving from the result set to be displayed in the result set viewer.
Also, the final row count in the SQL History will reflect the actual number of rows that were retrieved. With the fix, if you cancel during the display to the result set viewer, the row count will reflect the number of rows actually retrieved before it stopped.
That's great news Francine! I'll make sure we look for the new release.
TO follow up, what release number will have the changes you mention? We are on Version: 14.10.01.201310271220 now. thanks!
Bill, Our latest version is 15.10.00.03, which will have this change for canceling result sets.
I use Teradata Studio Version 15.10.01 and it seems not working.
Wolfgang, The fix for 'the actual row count to be displayed in the pop up window' is available in our upcoming 15.12 release (scheduled for mid September).