|
Archives of the TeradataForumMessage Posted: Fri, 08 Nov 2003 @ 00:53:41 GMT
"...which causes all derived tables to go to memory rather than spool." Not so. What it does is cause derived tables to be handled as if they were views. This often saves a retrieve step and it makes possible alternate plans the optimizer would not have considered if it spooled all derived tables. The advice to try setting internal 44 to TRUE is very good, though. The query is full of derived tables and spooling them as was always done prior to V2R5 might just allow the query to sneak by the memory limits of the parser.
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||