Nitin Srivastava, Author at DWHPRO
Avatar
Nitin Srivastava

Author Archives: Nitin Srivastava

Nitin Srivastava holds engineering degree in Computer Science. He has 5+ years of experience in Teradata SQL Development and Query Optimization. He has worked for Telecom,Health Care, Banking Clients across the globe.

3

How to get SQL Query Stats in Teradata

Several parameters can help us in understanding SQL Query Performance in Teradata.
I consider AMPCPUTime, TotalIOCount, SpoolUsage as three main parameters to determine SQL Query performance.
Say, you are executing multiple queries in Teradata sequentially. You might think the query which took most time is weak, but this may not be true for all the cases. However, if you refer to above mentioned three parameters to decide worst query, you will be correct for most of the cases.
There are two tables in DBC which give us this required information: DBQLOGTBL and DBQLSQLTBL.
To get SQL Query Stats, you can use below mentioned query:

SEL
TB1.queryband,TB1.NumResultRows,TB1.NumSteps,TB1.TotalIOCount,
TB1.AMPCPUTime,TB1.ParserCPUTime,TB1.NumOfActiveAMPs,TB1.MaxCPUAmpNumber,
TB1.MinAmpIO,TB1.MAxAmPIO,TB1.MaxIOAmpNumber,TB1.SpoolUsage,
SUBSTR(TB2.SqlTextInfo,1,1000) AS SqlTextInfo
FROM
DBC.DBQLOGTBL TB1
INNER JOIN
DBC.DBQLSQLTBL TB2
ON
TB1.QueryID = TB2.QueryID
AND
TB1.ProcID = TB2.ProcID
AND
TB1.SessionID=12345;

You can add or remove columns per your requirement. However, the ones highlighted are important parameters for determining any Query Performance in Teradata.
If the AMPCPUTIME is high, you have to tune your query to make sure it perform well.

Three points to consider while running the query mentioned above:

a) You may not see results immediately after running your SQL queries. There is few minute delay when query information comes to DBQL tables.

b) The query mentioned above may take some time to give output. The reason behind it is the ‘NOT SO PROPER’ Index columns for these two tables. When we check the PRIMARY INDEX columns for both the tables, we observe that the PI is same. Both the tables have ProcID, CollectTimeStamp as PI, however, the value for CollectTimeStamp can be different for the same query in both the tables. Hence joining by the second column in not advisable. Therefore, you cannot leverage PI ultimately here hence the query may take some time for giving results.

c) To get the SessionID, just run SEL SESSION; command in the same session in which you are running your queries.

So now on, never say that query which took the maximum time is the worst. Fetch the Query DBQL stats and check the worst query yourself.

>