 |
 |
Archives of the TeradataForum
Message Posted: Wed, 07 Sep 2005 @ 22:54:19 GMT
Subj: | | Re: Urban myth / Legend / Complete fabrication |
|
From: | | Anomy.Anom |
<-- Anonymously Posted: Wednesday, September 07, 2005 18:13 -->
The order of the tables shouldn't matter for the optimizer, in this case. The plan should be the same. There is already an incident/DR for
this. NCR GSC should be able to give you more information on this. If you are able to run the query in a separate session, could you try this
diagnostic before the query - 'diagnostic noinner on for session;' and confirm if you could get the same plan for different table order.
| |