Archives of the TeradataForum
Message Posted: Thu, 17 May 2012 @ 22:09:48 GMT
I can only thik of two reasons for a query being delayed in Teradata:
1) TASM throttle rules
2) Blocks - the query requires a lock which conflicts with a lock that has already been granted
If I understand you correctly, production holds data from start of 2010 to the current date and Certification is from start of 2010 to October.
Assuming that the number of rows is constant for each month and that "last October" means the end of October:
- Production holds data for 16 1/2 months of data
- Certification holds 10 months of data
If the two systems are of equal/comparable performance capabilities (sorry, I can't remember if you described the two systems) then I'd not be surprised if a query on Production takes 1.6 times the length of time for the same query on Certification.
Measuring the 'start' time with Pmon: If you're looking at the session screen in Pmon then I think that there is a delay in this information being available and that could very well be 30 seconds or more. What have you got set for the Session Collection rate ?
Ward Analytics Ltd - Information in motion (www.ward-analytics.com)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|