 |
 |
Archives of the TeradataForum
Message Posted: Thu, 02 Mar 2006 @ 15:35:44 GMT
| Subj: | | Re: Table and join sequences.. |
| |
| From: | | Victor Sokovin |
| | Any such rules necessary for teradata? If there are a series of equi-joins spawning a few intermediate spool files in the process, how do I
arrange the join sequence such that the query would consume the least amount of resources ? | |
There are no such rules for Teradata on recent releases. The idea is that the optimizer might always rewrite the query as it feels appropriate.
In Teradata, there are no equivalents of Oracle hints. Try explain plans for your SQL statements and you'll see what the optimizer has done to
them.
Of course, exceptions exist, and if you are curious about them, try the archives of this Forum. But they are just that, exceptions. No
guarantee they will work for you on your current release or any future release.
So, not all Oracle experience can be recycled on Teradata but the most essential "best SQL practices" should still apply. Just allow yourself
some time to experiment.
Regards,
Victor
| |
