Archives of the TeradataForum
Message Posted: Mon, 05 May 2003 @ 21:25:39 GMT
<-- Anonymously Posted: Monday, May 05, 2003 17:18 -->
Hi, as I understand it in V2R5 the optimizer will treat derived tables more like views and will be able to choose where, within the explain plan, to materialize and use them versus how it's done now which is to materialize the derived table first.
Does anyone know how this will affect the use of derived tables to do things like force aggregation of large tables prior to joining out to reference tables? Forcing precedence by using derived tables is a very effective performance tool, which if lost, will be a big issue for many users in my opinion.
Any feedback would be appreciated.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|