Archives of the TeradataForum
Message Posted: Fri, 03 Dec 1999 @ 21:47:06 GMT
It sounds like what you are looking for is an understanding of the step that each SQL statement is currently in. Teradata doesn't provide that capability yet (I think it is coming.) Therefore, you really need to infer what is happening from other information like:
Are the queries clocking CPU and IO? Compare that with previous runs of this job.
Are there any warning messages in the job output such as 2631 ABORT due to deadlock?
Are these queries blocking each other?
Is the system at CPU 100% utilization?
Are other queries experiencing similar performance degradation? Does each update involve significant row redistribution? If so, check to see if the system is flow controlling". See the Performance Optimization manual (look for the puma m command).
Is there a query running on the system that is skewing badly? Try running a query against the updated table to see if some updates have been applied. (Using Locking for Access).
These are some of the things that I would examine first.
Hope this helps.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|