Archives of the TeradataForum
Message Posted: Fri, 22 Mar 2013 @ 10:03:53 GMT
Yes the network is a possibility. Another one is if a user is not at their desk and the application is waiting for a response. The following example demonstrates this.
- you use SQL Assistant to run a query which is going to return 5000 rows
- in your copy of SQLA you've got the option that limits the number of rows displayed in an answerset to 2000
- you execute your query and then do something else (lunch / meeting / coffee break / urgent report for the boss)
- the query completes in the DBMS and starts sending dat aback to the application.
- SQLA stops after receiving 2000 rows an asks you whether you want the rest
- until you answer that question, the query has not completed on the DBMS and your session is still in "response" state - *** providing that *** the answer set is large enough that it hasn't all been sent back (for instance, an answer set of say 20 rows will not cause this issue even if your SQLA setting was 10)
Ward Analytics Ltd - Information in motion (www.ward-analytics.com)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 24 Jul 2020|