Intrepreting DBQL DelayTime in Teradata 13.10 - comment by sm4073

Hi Carrie,
As always I  value your postings and articles and views. Based on the conclusion above, I wrote some a simple scripts and found incorrect restults. Did a deep dive into the query and found that  the  inside DBC.DBQLogTbl  the column data type doesn't match and as such my report bit away from the actual expected results. Your thoughts on this please. There is no major impact because of this but would like to know the  reason behind this. 
DelayTime FLOAT FORMAT '----,---,---,---,--9.999',   
WDDelayTime INTEGER FORMAT '--,---,---,--9',
 
Ref:
If your query is only delayed by a WD throttle: 

• WDDelayTime = Time actually delayed
• DelayTime = The same time as in WDDelayTime    (/* When I compare the results does not match because of the decimal values*/ )

 If your query is only delayed by a system throttle:

• WDDelayTime will be NULL
• DelayTime = Time actually in the delay queue

If your query is delayed by both:

• WDDelayTime = WD throttle delay time
• DelayTime = Wallclock time delayed by both, does not identify system throttle contribution
•