 |
 |
Archives of the TeradataForum
Message Posted: Thu, 02 Dec 2004 @ 15:21:31 GMT
Subj: | | Re: ("1=1") condition in the explain plan |
|
From: | | Meade, Cornelius |
I think the topic/issue some responders may have had in mind (including myself) when forming their responses may not have been quiet on
point....there is a difference between a result set that represents a Cartesian product (usually not very useful from a business perspective) and
the optimizer choosing to do a product join as some interim step which is really more to the heart of the question posed....That said however, I
have still often found it that a product join at any point in the query plan of a transaction that is already suspect, is usually worth closer
scrutiny to determine why that execution plan is being chosen.....
Cornelius Meade III
EDS - Consulting Services/BI/CRM
| |