Archives of the TeradataForum
Message Posted: Fri, 14 Dec 2012 @ 09:46:24 GMT
The time spent in "response" is partially controlled by the program, in your case Cognos. The session will stay in RESPONSE state until all of the data has been sent by the dbms. What is Cognos doing with the data once it has retrieved it? SQLA is 'simply' displaying it in a grid - but I wouldn't have thought it should take as long as you say. Presumably Cognos is using an ODBC connection to the Teradata system, are there any settings in your DSN that will slow down data transfer - you might want to compare the "max response size" value between the DSN used for SQLA and Cognos.
Finding the "time in responding state" is not straight forward and prior to TD 13.10 you cannot do it reliably.
- TD 12 and earlier column LASTRESPTIME in DBQLOGTBL is not always reliable (nominally you should calculate LASTRESPTIME - FIRSTRESPTIME)
- TD 13.0 this column is removed completely, you cannot work out " time in responding state "
- TD 13.10 and higher: you need the DBSCONTROL General setting DBQLLogLastResp as TRUE (by default it is false). That causes a 'pseudo step' with a type of RESP to be written to the DBQLStepTbl. Calculate " time in responding state" as STEPSTOPTIME - STEPSTARTTIME.
Ward Analytics Ltd - Information in motion (www.ward-analytics.com)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|