 |
 |
Archives of the TeradataForum
Message Posted: Wed, 16 Feb 2011 @ 08:39:32 GMT
Subj: | | Re: Mysterious "no more spool" errors |
|
From: | | Barrineau, Claybourne |
To your first point, I've definitely seen cases where Teradata was slow to release spool and queued up queries executed sequentially failed as
a result (in my case, I've seen this with queued-up Microstrategy reports). Regarding your second point...I just don't trust DBQL spool
numbers...I've never been able to correlate these numbers to the numbers I see in PMON. Typically, DBQL underreports the spool I see in PMON.
Hope this helps,
Clay
| |