Quantcast
Channel: Teradata Developer Exchange - Blog activity for carrie's blog
Viewing all articles
Browse latest Browse all 1058

Intrepreting DBQL DelayTime in Teradata 13.10 - comment by carrie

$
0
0

Haritha,
 
Basically,  you can take the difference between StartTime and FirstStepTime and assume that it represents parsing time.  But if there delay time due to a throttle, then that difference will also include delay time.   You have said that DelayTime is NULL.   So you are fine with this approach then.  But sometimes DelayTime is reported as zero instead of NULL, and that may look as if no delaying has taken place, but whether or not that is the case depends on what software release you are on.
 
 In 13.10, DelayTime in DBQLogTbl uses an integer data type, so any delaytime less than 1 second is reported as zero (not NULL).   Starting in 14.0 DelayTime has a data type of float format 9.999 so it will report very small delay times, to 3 decimal places.
 
 So if you are on 13.10 or earlier software and you see zero instead of NULL, there could be some small level of delay time that you are interpreting as parsing engine time.
 
Thanks, -Carrie
 


Viewing all articles
Browse latest Browse all 1058

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>