Archives of the TeradataForum
Message Posted: Fri, 28 Jun 2002 @ 23:55:17 GMT
please report this to the GSC. Please encapsulate your query within a TSET export so that the GSC can check to see if the PLAN has changed bewteen 4.1.0 and 4.1.2.
Typically if it using more spool the optimizer has chosen a different path for some reason and we should figure out the reason.
Maybe it is out of date statitics.
Maybe you added more records to one of tables and crossed a boundary where the optimizer chooses a merge join vs a hash join vs cartesian product.
Maybe a DR added to 4.1.2 changed the boundary value and therefore without adding any more records your query is now on the other side of that boundary.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|